Fixed-price software vs agency retainers

Fixed-price software vs agency retainers is how most UK founders actually buy delivery, even when the proposal talks about "partnership." One model sells a bounded outcome for a written number; the other sells ongoing capacity by the month. Pick for predictability and finish lines, not for which PDF looks friendlier.

Fixed-price software

Fixed-price software means you agree the outcome, the boundaries, and the number before serious build starts. At Eight Mile that runs survey first, then a fixed written price for the first release: the figure on the quote is the invoice. Work happens on your cloud accounts. You own the code, accounts, and data from day one, with warranty after launch rather than a vague "we'll keep tinkering."

It fits a SaaS MVP, customer portal, or ops platform you can name in one workflow. You want cost certainty, a finish line, and something you could hand to another team. Soft path sits on SaaS and software development.

One hard edge: fixed price with a wishlist is a fantasy. If the brief is "like X but nicer" with no must-haves, either shape it properly first or you will burn the trust the model depends on.

Agency retainers

An agency retainer buys continuous capacity: a team on a monthly meter, backlog never fully closed, discovery and delivery mixed together. It fits when you already trust the people, the product needs ongoing evolution, and "done" is the wrong word for the next twelve months.

It fails as a substitute for a scoped first release. I've watched retainers become a slow bleed: stand-ups every week, demos that never quite ship, and nobody able to say what last month's invoice bought. Open retainers optimise for motion. They do not automatically protect a date.

Quick Comparison

• Cost predictability. Fixed-price: written number before build. Retainer: monthly burn; total unknown.
• Scope. Fixed-price: bounded outcome for the release. Retainer: living backlog.
• Speed to first useful release. Fixed-price: strong when scope is ruthless. Retainer: depends on prioritisation habits.
• Change handling. Fixed-price: new release or priced change. Retainer: absorbed into the month, or quietly deferred.
• Ownership / IP. Fixed-price: should be yours from day one. Retainer: often fuzzy if hosted "for you."
• Exit cost. Fixed-price: leave with the repo if set up right. Retainer: process, knowledge, and sometimes the platform.
• After launch. Fixed-price: warranty or next fixed release. Retainer: continuous relationship by default.

When each fits

Choose fixed-price when you need a clear MVP or rebuild with a finish line and a number you can take to the board. Choose a retainer when continuous product work with a trusted team beats a series of priced releases, and you accept open-ended cost for that flexibility.

Wait on both if you cannot name the first useful outcome. Pricing models do not fix an empty brief. And beware the agency that quotes "fixed" then change-requests every clarification into extra fees: that is a retainer in a fixed-price costume.

Which one do you need?

If you are weighing fixed-price software vs agency retainers for a first SaaS or ops build, start fixed-price when certainty and ownership matter more than perpetual capacity. Keep retainers for after you have something live and a partner you trust.

Eight Mile is built for the survey, then a fixed written price, then your accounts path, not for classic open retainers as the default. That is a commercial choice, not a moral one.

Fixed price for a finish line; retainer for continuous capacity. Buy the one that matches how "done" should feel.

If a fixed-price first release is the better call, contact Eight Mile and describe what "live" means in a few sentences.