Fixed price or time and materials: which one protects a founder?
Most agency articles on this end in the same place: an MVP should be billed by the hour, because the scope is going to move. The scope is going to move. That is exactly why the founder, who knows least about how long the work takes, should not be the one carrying the estimate.
For a first build, a fixed price per milestone protects a founder better than time and materials, provided the price is tied to a written scope and every change is quoted before it is built. Time and materials is the right model for work nobody can scope yet, and for ongoing work after launch. The mistake is using it to avoid scoping.
What each model actually means
Both models pay for the same work. What changes is who absorbs the gap between the estimate and reality, and every software estimate has one.
| Fixed price | Time and materials | |
|---|---|---|
| What you agree | A scope, a price and a date | A rate, and a rough estimate of hours |
| If the work takes longer | The supplier absorbs it | You pay for every extra hour |
| If you change your mind | The change is quoted, and you decide | It is simply more hours |
| What you know on day one | The total | The rate |
| How it fails | Padding, and corners cut near the end | A budget that runs out before the product is done |
Neither column is free of risk. The question is which risk you would rather manage, and which one you can actually see coming.
Where the standard advice goes wrong
The case for hourly billing on an MVP runs like this: you are still learning what the product is, requirements will change, and a fixed price locks you into a specification you will regret. All three statements are true. The conclusion does not follow from them.
An estimate is a prediction about how long software takes to build. The supplier has built dozens of similar things and the founder usually has built none. Time and materials hands the consequences of that prediction to the party least able to judge it. When the estimate turns out low, and it usually does, the founder finds out from an invoice, often after most of the budget has gone.
The real answer to "the scope will change" is not to stop pricing the scope. It is to lock the scope before you price it, and then to price each change as its own decision. That is slower on day one and much cheaper by week eight, because you see every change in money before you approve it rather than after it has been built.
Why a fixed price can hurt you too
A fixed price is only as good as the terms around it. Four ways it goes wrong, and each has a tell you can spot before you sign:
| Failure | What it looks like | The tell |
|---|---|---|
| Padding | The quote carries a large buffer for risk, so you pay for delays whether or not they happen | A number with no scope document behind it |
| Change-order theatre | Every clarification is reclassified as a change, and the total creeps anyway | A scope written in paragraphs rather than screens and user journeys |
| Fixed price, floating date | The money is capped but the calendar is not, so the project simply runs late for free | No milestone dates, or dates with no consequence attached |
| Corners cut at the end | The supplier is losing money on the last milestone, and testing is where it shows | One large payment at the end, or all of it up front |
The last two are why a fixed price should be paid per delivered milestone, with a date on each, rather than as one lump sum. Payment then follows working software, and a supplier who is behind feels it at the next invoice rather than at the end.
When time and materials is genuinely the right answer
There are real cases, and a supplier who insists on fixed price for all of them is either padding hard or not thinking:
Even then, it should come with guardrails: a weekly or monthly cap you approve in advance, a demo of working software every week so hours map to progress, and the code in your own repository from the first commit so you can stop at any point and keep what you paid for.
The shape most founders actually need
In practice the answer is not one model. It is three stages, each priced the way its uncertainty deserves:
| Stage | How it should be priced | What it is for |
|---|---|---|
| 1. Scoping | A small fixed fee | Turning an idea into screens, journeys and a costed plan. This is what makes stage two priceable |
| 2. The build | Fixed price, paid per milestone | The first version, against a scope you have signed off |
| 3. After launch | Monthly, and optional | Changes driven by real users, which nobody can scope in advance |
This is how Foundreco prices, so it is worth being specific. Scoping is the App Blueprint, $800 to $2,500 over one to two weeks. The build is a fixed price agreed before work starts, paid per delivered milestone, and it does not move unless you change the scope; any change is quoted before it is built. If a milestone lands late because of Foundreco, that invoice drops 20% automatically, and you can leave at any milestone with all of your code. After launch, 30 days of care are included, and a monthly maintenance retainer, from $600 a month, is there if you want it rather than required. The full numbers are on the pricing page and the contract terms are on the guarantees page.
Five questions to ask any supplier, whichever model they quote
These work for fixed price and hourly alike, and a good supplier answers each one in a sentence:
| Ask | A good answer |
|---|---|
| What exactly is the price tied to? | A written scope, screen by screen, that you sign |
| How is a change handled? | Quoted in money and days before anything is built |
| What happens if you are late? | A named consequence, in the contract, not an apology |
| When do I pay? | Per delivered milestone, never mostly up front |
| If I leave halfway, what do I keep? | Everything, because it is already in your repository |
The last three are clauses rather than questions, and they are covered in more detail in six clauses to look for in a software development contract. If you are comparing suppliers more broadly, how to choose an app development company carries the rest of the checklist.
So which should you pick?
| Your situation | Pick |
|---|---|
| You have an idea and a budget, and need a first version | Paid scoping, then fixed price per milestone |
| You already have a locked scope and designs | Fixed price per milestone, straight away |
| You are exploring whether something is technically possible | Time and materials, with a cap |
| The product is live and you are iterating on user feedback | A monthly arrangement, cancellable |
| A supplier will only quote hourly for a first build | Ask why. Usually it means nobody has scoped it, including them |
If you want a first number before talking to anyone, the instant estimate gives a range in three taps, and the free app proposal turns six answers into a scoped document with a cost and a phased plan.
Common questions about pricing models
Is a fixed price always more expensive than hourly?
Does a fixed price mean I cannot change anything?
What is a milestone-based contract?
Why would an agency prefer hourly billing?
Does Foundreco ever bill by the hour?
Get one number, in writing
Send your idea in three sentences and you get an honest verdict within 24 hours. If it is worth building, you get a scope, a fixed price and milestone dates before anything is built.