A fixed-price quote for a new app does not remove risk. It moves the risk into the change-request process, where it is harder to see and more expensive to argue about. For most funded startups, the better contract is a short fixed-price discovery phase followed by capped, time-boxed build phases.
That is an opinion, and plenty of buyers disagree. A fixed number is easy to take to a board, and it feels like the agency is carrying the danger. Here is why we do not think it works that way, and where fixed price is still the right call.
What a fixed price actually fixes
A fixed price fixes one thing: the number written on the quote, for the scope written on the quote. It does not fix what you will learn when real people use the product. That happens after the document is signed, and it is the part that decides whether the app works.
So the moment you see a real screen on a real iPhone and say, “this step should come before that one,” you have left the contract. Someone has to decide whether that is a change or a clarification, and the answer affects someone's margin.
Agencies know this when they price. Careful ones add a buffer for the unknowns, and you pay for that buffer whether or not the unknowns show up. Less careful ones price tight and recover the money through change orders. Either way, the number on the quote was never really the cost of your product.
Where the fight actually happens
Founders worry that time-and-materials means an open meter. The more common failure on a fixed price is quieter: a long argument over whether something was in scope.
Picture a quote that says “user login.” You assumed that meant the full sign-in experience, including what happens when a session expires. The team assumed the happy path. Neither of you is lying. The words were just written before anyone had touched the product.
We saw how fuzzy that boundary can get on SOAPNoteAI. The web product already used the OIDC authorization code flow, and getting that login working end to end on iOS took many iterations. A line item reading “authentication” would have looked simple on paper. Priced as a fixed fee, those iterations would have become a series of conversations about who owed whom, in the middle of a launch. We say that as a hypothetical: it is how the incentives would have pushed, not a description of how that engagement was contracted.
A fixed price is a bet on how well two parties imagined an unbuilt product in the same way.
The strongest case for fixed price
There is a real counter-argument, and it deserves a fair hearing. Fixed price gives you a ceiling. If your finance team needs one number, or you are working under a grant or a client contract that demands it, a ceiling is not a nice-to-have.
It also forces a discipline that time-and-materials does not. A team that has to stand behind a number will push you to write down what you want, cut what you do not need, and decide things early. Those habits are valuable.
We still hold our position, for one reason. The discipline is available without the trap. You can write the same detailed scope, apply the same cuts, and still keep the freedom to change your mind between phases. The ceiling is the only part of fixed price worth keeping, and a cap does that job too.
When fixed price is the right choice
We are not against it. Fixed price works well in a narrow set of situations:
- The scope is small and the screens are already designed and approved.
- The backend is stable and documented, so the app only has to consume it.
- The work is a port or an update to something that already exists and behaves the same way.
- You have a hard budget limit and are willing to trade features to stay inside it.
The backend point matters more than most founders expect. If you are unsure how solid your API is, read our note on why an existing API is the biggest variable in a mobile timeline. An unknown backend is exactly the kind of unknown a fixed price cannot absorb.
The contract shape we recommend instead
Most early products meet few of those four conditions, which is why we steer founders to a phased structure. It has four parts:
- A fixed-price discovery phase. A short, bounded piece of work that ends with a written scope, clickable designs, a list of technical risks, and an estimate range. You buy clarity for a known amount.
- Build phases of a few weeks each. Every phase has a written goal, an estimate, and a cap. The team stops and re-plans before reaching the cap rather than after passing it.
- A demo on a real device every week. Not a slide deck. If the work cannot be shown on a phone, you cannot judge whether the hours were well spent.
- A decision at every phase boundary. Continue, change direction, or stop. The contract should make stopping cheap, so the decision is real.
This keeps what founders like about fixed price, which is a known maximum for each commitment, and removes what they hate about time-and-materials, which is an open meter. It also turns scope changes from disputes into normal planning conversations.
What to ask any agency before you sign
Whichever model you pick, the contract only works if the agency behaves well inside it. These questions reveal that faster than a proposal does:
- How are scope changes priced, and who decides whether something is a change?
- What does a weekly progress report show, and can I see hours against the estimate?
- What happens to the budget if an integration turns out harder than expected?
- What does it cost me to stop after any phase?
- Who owns the code and the accounts from day one?
If you want a longer list built for the scoping stage, we wrote up the five questions we ask every founder before scoping a native iOS build. For help reading the numbers on the quotes you collect, start with what a $12k and an $80k build actually look like.
The trade-off we will not hide
The phased model asks more of you. You have to attend the weekly demo, make decisions quickly, and accept that the total cost of the full product is a range until discovery is done. If you want a single signed number and no involvement, a tightly scoped fixed price is the better fit, and we would rather tell you that than sell you the wrong shape.
The aim is the same either way: a contract where problems surface early, while they are still cheap to fix, instead of at the end, when they become arguments.
FAQ
Is fixed price or time and materials better for building a mobile app?
Neither wins by default. Fixed price suits a small, well-understood scope where requirements will not move. Time and materials suits products still being discovered. For most funded startups, the safer structure is fixed-price discovery, then short fixed-scope phases, each with its own budget cap and an explicit decision to continue.
Why do fixed-price app projects go over budget?
Usually the price does not go over; the scope arguments do. A fixed quote is written before anyone has used the product, so real feedback becomes a change request. Each one triggers a negotiation, and the team protects its margin instead of the product. Founders pay in delay and friction rather than a surprise invoice.
What is a capped time and materials contract?
A capped time and materials contract bills actual hours at agreed rates but sets a maximum for a defined phase. The team must stop and re-plan before reaching the cap. You keep flexibility on what gets built while limiting how much any single phase can cost, which makes budget conversations concrete and early.
How do I protect my budget on a time and materials app build?
Break the build into phases of a few weeks, each with a written goal, an estimate, and a cap. Ask for weekly demos on a real device and a burn report against the estimate. Review at every phase boundary whether to continue, change direction, or stop. Never approve an open-ended budget.
Comparing quotes and not sure which contract shape fits your product? Bring them to a free 30-min call and we will read them with you →

