Short answer: fixed price is the right model for a first, defined build — it forces clarity and caps your risk. A flat monthly retainer is the right model for everything after launch, because software never stops changing and paying per change is the most expensive way to change. Most businesses that get burned use the right model at the wrong stage.
What fixed price actually buys you
A fixed quote, in writing, before work starts — we offer exactly this for defined builds, and for a first engagement it's often right. You know your exposure, the provider carries the estimation risk, and everyone is forced to think before building. Its weakness appears the day reality diverges from the specification, which is always. Then every new idea becomes a change request.
The change-request treadmill
In the traditional model, each post-contract idea is scoped, quoted — commonly $10,000–$30,000 for anything substantial — negotiated and signed off before anyone writes code. Three costs hide in that loop:
- Delay: weeks of scope negotiation for days of engineering. The business waits while paperwork moves.
- Distortion: pricing per change punishes learning. Discovering a better approach mid-build becomes a commercial fight instead of good news.
- Deferral: maintenance and small improvements never justify their own change request, so they queue until they're an emergency — and emergencies bill differently.
The pattern's endgame is familiar: software that's expensive to touch, so nobody touches it, so it decays, so it's eventually "cheaper to rebuild" — with the same model, starting the loop again.
What a retainer changes
A flat monthly fee covering design, development, maintenance and releases turns software from a series of purchases into an operating capability. Priorities shift sprint to sprint as the business changes — no new quote, no penalty for a better idea. Maintenance happens continuously instead of queueing for an emergency. And the incentive flips: a retained team profits from your software being healthy and cheap to change, not from change being expensive.
The commitments are what make it real rather than a blank cheque. Ours are published: two-week sprints with a demo at the end of each, a production release every month — twelve a year, guaranteed — response SLAs in writing, and every line of code in your repository from day one, so you can leave at any time and keep everything. A retainer without published commitments and visible code ownership is just a subscription to hope.
How to choose
- First build, well-defined: fixed price, quoted in writing. Cap the risk, prove the relationship.
- Live software your business depends on: retainer. It will need continuous change; pay a flat rate for it, not a toll per idea.
- Either way: insist on day-one repository access under your own account. The commercial model matters less than whether you can walk away whole.