Fixed price or retainer? How to choose for your first product
A simple framework based on how sure you are about what you’re building.
Founders often ask which engagement model is cheaper. The honest answer is that it depends on one thing: how confident you are about what you need.
Choose fixed price when…
- The scope is clear and unlikely to change much during the build
- You need a firm budget for investors or a grant application
- There is a hard deadline, such as a launch event or a regulatory date
Fixed price shifts the risk of estimates to us. In return, changes mid-project go through a change request so the scope stays honest.
Choose a retainer when…
- You’ve launched and are learning from real users every week
- Priorities change faster than a project plan can
- You want the same people on your product month after month
A retainer buys a dedicated team’s time. You decide every fortnight what that time goes on.
The most common pattern
- A two-week discovery sprint to define the MVP
- A fixed-price build to launch it
- A retainer to improve it based on what customers actually do
| Fixed price | Retainer | |
|---|---|---|
| Budget certainty | High | Monthly |
| Flexibility | Change requests | Fortnightly re-planning |
| Best for | MVPs and rebuilds | Live products |
| Risk on estimates | Studio | Shared |
A warning signIf a studio offers a fixed price before understanding your users, the price is a guess. Either it’s padded, or the scope will shrink later.
