Insights
Fixed price vs time and materials for a first release
The pricing model is a decision about who carries the risk of what nobody knows yet. Choosing it before the scope exists moves that risk around without reducing it.
What is the difference?
In a fixed-price contract the vendor commits to a defined result for a defined sum. Scope is the thing that is fixed, so changes go through a written change request. In time and materials you pay for the time spent, and scope can move every week. The buyer carries the risk of the total.
| Fixed price | Time and materials | |
|---|---|---|
| What is fixed | Scope and total | Rate; scope moves |
| Who carries cost risk | The vendor | The buyer |
| Needs before signing | Written scope and acceptance criteria | A priority order and a review interval |
| How change is handled | Written change request | Re-prioritised backlog |
| Fits | A defined first release after discovery | Unknown scope, or work after launch |
When is a fixed price honest?
A fixed price is honest when three things are written down: the workflow the release replaces, the systems it integrates with, and the test that says it is done. That is what discovery produces. Before that, a vendor quoting a fixed price is either padding the number to cover what it does not know or planning to recover the difference through change requests.
Reorigin scopes a written proposal for a defined release after discovery. The planning bands on the service pages, such as $2,000–$40,000 for a custom software MVP, tell you the order of magnitude before that conversation. They are not quotes.
When does time and materials fit better?
Some work cannot be fixed without lying about it: research into whether a model is accurate enough, modernising a codebase nobody has opened yet, or a product that keeps changing after launch. For continued product engineering after the first release, a retained partnership is the usual shape, and it is scoped separately from the release.
Time and materials is not the same as staff augmentation. You can pay for time and still have the vendor own architecture and quality. Reorigin does not sell unnamed hours under either model.
What do both models need?
Both need a first release small enough to reach production, a named owner on each side, and a rule for change. In a fixed-price release the rule is a change request. In a retained engagement it is a priority order reviewed at a set interval. Without that rule the pricing model does not protect anyone.
The sequence from inquiry to proposal is on how we work. The bands are explained in what a custom software MVP costs in Turkey.
Sources and further reading
- Principles behind the Agile Manifesto — the case for welcoming changing requirements, which a pricing model has to allow for.
FAQ
Is fixed price or time and materials better for an MVP?
Fixed price fits an MVP whose workflow, integrations, and acceptance criteria are written down after discovery. Time and materials fits work whose scope is still unknown or continues after launch.
Does Reorigin work fixed-price?
For a defined release Reorigin scopes a written proposal after discovery. When the product continues after launch, a retained partnership is the usual shape and is scoped separately.
Why not get a fixed price before discovery?
Because the scope is not known yet. A price before the workflow, integrations, and first release are named is a guess, and the difference returns later as padding or change requests.
Is time and materials the same as staff augmentation?
No. Time and materials is a pricing model. Staff augmentation is renting people you manage yourself. Reorigin does not sell unnamed hours under either model.