COBOX
Fixed Price vs Time and Material vs Retainer: How to Choose a Software Contract
When a founder asks for a quote, the answer often comes back as a single number. What is rarely explained is that the number comes with a hidden choice about who carries the risk if the work turns out harder, longer or different from what anyone expected. The pricing model is really a risk-sharing agreement.
Fixed price
You agree a scope and a price. The provider carries the cost risk within that scope. It is attractive because the budget looks certain, and it can work well for small, well-understood work.
What to watch: a fixed price is only as good as the scope document. Software requirements always shift as people see working screens, so changes become "change requests" priced separately, and the final cost can drift far above the first number. Providers also protect themselves by padding estimates or by limiting what is included. A very low fixed quote for a vague brief is a warning sign: something will be cut later.
Time and material
You pay for the effort actually spent, usually at hourly or daily rates, often with a monthly cap or a budget estimate. You keep flexibility: priorities can change weekly, and you pay for learning as you go.
What to watch: you carry the cost risk, so you need visibility. Ask for weekly timesheets or burn-down reports, a demo every sprint, and a clear estimate range at the start. It rewards a customer who can make decisions quickly and punishes one who cannot.
Retainer
You pay a regular monthly fee for a defined amount of capacity, for example a certain number of hours or a small team, used for ongoing improvements, support and maintenance. It suits live products, where the work is a steady stream of fixes and enhancements rather than a single project. Compare it against the realistic costs in what software maintenance costs after launch.
What to watch: what happens to unused hours, how emergencies are handled, and the response times in writing.
A hybrid that often works best
Many sensible engagements combine models. A common pattern is a small fixed-price discovery phase that produces a scope, a prototype and an estimate, followed by time-and-material or milestone-based delivery, followed by a retainer after launch. You pay a known amount to reduce uncertainty, then commit to build once the big unknowns are visible. See what a product discovery workshop includes.
Choosing quickly
| Situation | Usually fits |
|---|---|
| Small, well-defined build with stable requirements | Fixed price |
| Early product with unknowns and likely pivots | Time and material, after a fixed discovery |
| Live product needing steady care | Retainer |
| You have your own technical lead | Time and material (augmentation) |
Clauses that matter more than the pricing model
- Acceptance criteria. How will you decide a deliverable is finished? Tie payments to demonstrable milestones, not to dates.
- Change process. A short, written way to estimate and approve changes keeps arguments small.
- Intellectual property and access. Code, designs and accounts should belong to you, with repositories and hosting in your name. Read who owns your software.
- Warranty period. A defined window after launch in which defects are fixed at no charge.
- Exit and handover. You should be able to leave with your code, documentation and credentials.
- Confidentiality and data protection. Especially if the work touches customer data.
Questions to ask any provider
- What exactly is included, and what is out of scope?
- How are estimates produced, and by whom?
- What does a change request cost and how fast is it handled?
- How will I see progress every week?
The questions to ask before hiring a software development company cover the wider checklist. This article is general information, not legal advice; have a lawyer review the contract before you sign.
Turn your idea into a plan
Want a realistic estimate and a sensible commercial model? Start with a Business Blueprint covering customers, revenue model, MVP scope, technology and roadmap. Paste something like this into the Blueprint tool:
I want to build [product description] for [type of customer]. My budget range is [range] and my timeline is [timeline]. Suggest the MVP scope, the phases and which contract model fits each phase.
Or talk to us first, and read about the Business Blueprint.