Your first iPhone app, built in 6 to 10 weeks and owned by you from day one.
Before any code, we work out who the app is for and what the first version has to do. Then one small team builds the iPhone app, the website and the backend.
- 30-minute call
- Fixed quote before any code
- NDA on request
Fixed quote
The price is agreed in writing before any code is written.
6 to 10 weeks
From the first meeting to a test version on your phone through Apple’s TestFlight.
Your accounts
The code, the domain and the App Store accounts are in your name before work starts.
A build every week
Each week you get a new version on your phone and a list of what changed.
Where is your app today?
Pick the one that fits. Your answer goes straight into the form, so you don’t have to explain it twice.
Most app budgets are lost on a first version that has to be thrown away.
First builds rarely fail because of the code. They fail because the plan was wrong, and then you pay for the app twice.
The deadline keeps moving
“Estimated 8 weeks. Actual: never completed after 26.”
The code has to be redone
“Every task they worked on had to be fixed by other people.”
You can’t get to your own code
The app exists, but it sits in the developer’s account instead of yours.
Nobody hears about the launch
The app is finished, but there’s no store page and no plan for after release.
The rest of this page explains how we avoid each of these.
Sometimes the honest answer is: don’t build the app yet.
If you haven’t talked to five people who would use it, talk to them first. If a no-code tool already does the job, keep using it. It’s time to build a real app when you hit one of these problems:
- Apple rejects it for being a website inside an app (App Review Guideline 4.2)
- It stops working without an internet connection
- Notifications don’t arrive
- The tool can’t do the one thing your users keep asking for
You own the code and every account. The contract says so.
Before the first line of code, the repository, the domain and the Apple and Google developer accounts are created in your company’s name. You add us as collaborators. If you decide to stop working with us, you remove our access and keep everything. The contract says this in plain words.
Every build is checked against Apple’s own review rules.
Apple publishes the App Review Guidelines it uses to approve or reject apps. We check each build against them before we submit it, and you get the checklist.
Minimum functionality
The app has to work like an app. A website wrapped in an app gets rejected.
Completeness
No placeholder text, no broken links and nothing marked “coming soon”.
Privacy
The app says what data it collects, why it needs it and how users can delete it.
The website side is measured with Google’s Core Web Vitals. You can run both checks yourself.
How the project runs, step by step
Expect about five hours of your time at the start, then about an hour a week.
- 01
Blueprint
Together we work out who the app is for, what they use today, the smallest useful first version, the screens, how it’s built and how it launches. It ends with a fixed quote, and the plan is yours to keep either way.
- 02
Design
You get the flows and screens as a prototype you can tap through on your phone.
- 03
Build
A new TestFlight build lands on your phone every week, with a plain list of what changed.
TestFlightBuild 7 · ready to testEvery week - 04
Launch
We handle App Review, release the app to users in stages and set up the store page.
- 05
After launch
We watch how people actually use the app, then ship the next release.
Is your app idea ready to build?
Answer five quick questions to find out. No email needed.
- Q1
- Q2
- Q3
- Q4
- Q5
Questions founders ask before hiring an app studio
How much does it cost to build an MVP app?
The price depends on how many screens the app has, how much backend it needs and what has to be in the first release. We agree a fixed price in writing before any code is written, and it only changes if the scope does.
Who owns the code?
You do, from the first commit. The repository, the developer accounts and the domain are all in your name.
Who will I work with?
A small senior team. The people who plan your app are the same people who build it.
What do I get if I stop after the Blueprint?
You keep all of it: the research, the scope, the screens and the technical plan. You can take it to any developer.
Do you build Android apps too?
Starting with iPhone is usually the faster way to learn what users want. If you need Android at launch, we plan for it in the Blueprint.
I already built my app with a no-code tool or a contractor. Can you help?
Yes. Bring it to the review. Sometimes the right answer is to keep what you have.
Will you sign an NDA?
Yes, before the first call if you like.
Book a free 30-minute review of your app idea.
Tell us what you’re building. Within one business day we’ll reply with a few questions and a time for the call. There’s no sales deck and no follow-up sequence.
We’ll sign an NDA if you ask.