We get the same question from new prospects almost every week: “Why don’t you just quote a fixed price for the build?”It’s a fair question. The agency model that founders grew up with is mostly fixed-bid project work — pay an upfront sum, get a delivery, sign off. The retainer model sounds like an upsell.
We’ve done both shapes. After enough years on each side, we have an opinion: fixed-bid project work is great for the agency and bad for the client, and we’d rather not run a business shaped that way. This post is why.
The fixed-bid cliff
A fixed-bid project ends on launch day. The site goes live, the invoice goes out, and the agency moves on to the next client. From that day forward, the site sits there ageing.
Software ages faster than buildings. A site shipped today will, within twelve months, have:
- Browser updates that break a previously fine layout
- A dependency CVE you should patch this week
- An analytics integration that quietly stopped reporting
- A Google Search Console alert nobody looked at
- A copy block that’s now factually wrong
- An email template that fires from a deprecated API
On a fixed-bid project, every one of those is a new purchase decision. The client either pays an hourly change-order, ignores the issue until it bites, or finds a new agency. None of those outcomes is good.
Software ages faster than buildings. The day you stop looking after a site is the day it starts costing you.
— Working principle
The incentive shape
Pricing shapes incentives more than any contract clause. Here’s how it plays out under each model:
Fixed-bid project
The agency’s incentive is to scope tightly, deliver cheaply, and move on. Anything that doesn’t fit the spec is out-of-scope. Long-tail issues land on the client. Quality of the build matters less than quality of the sign-off — once it’s signed, the bug becomes the client’s problem.
Hourly contract
The agency’s incentive is to fill the timesheet. Slow work pays better than fast work. Refactoring is billable. So is every meeting. The client is paying for attention, not outcomes.
Monthly retainer
The agency’s incentive is to keep the relationship alive. That means: reduce friction, surface problems before the client asks, suggest improvements proactively, fix things quickly. The client doesn’t have to chase. The agency doesn’t have to upsell.
Of those three, the retainer is the only model where the agency and the client win when the same things happen. That alignment is the entire argument.
Why it feels expensive (and why it isn’t)
The most common pushback is some version of:“I’m paying every month forever — that’s more expensive than a one-time build.”
Run the numbers. A fixed-bid build at the level we ship typically lands £25–55k. Then the site needs maintenance, performance discipline, and ongoing optimisation work. Most teams try to skip the relationship for three to six months and then pay £8k–20k in emergency engagement when something breaks or a competitor ships ahead. Inside eighteen months they’ve typically spent more than a year of Acceleration retainer, in unpredictable chunks, with no compounding and no senior context retained between engagements.
Why three stages, not one number
A relationship that lasts a year doesn’t need the same shape every month. Foundation is for teams who want a senior steward of their digital surface — weekly monitoring, monthly strategic audit, maintenance hygiene, and one shipped improvement each quarter. The work is disciplined and predictable, not ambitious. That is exactly what it should be at this tier.
Acceleration is for teams ready to compound — SEO sprints, paid acquisition on one channel, monthly build sprints, bi-weekly strategy. The cadence shifts from quarterly to monthly because the questions you are asking shift from is the site healthy to which lever moves revenue next. It is the default tier for B2B operators building serious infrastructure over twelve months and beyond.
Scale is qualitatively different again. Reserved engineering capacity, weekly cadence, parallel custom builds running alongside the optimisation work, a named lead, NET 30 invoicing. The teams who land here know they need an embedded partner, not a vendor.
Above Scale sits Bespoke — dedicated pod, embedded into your cadence, Master Services Agreement, custom commitment shapes. Discussed individually because procurement-shaped engagements get scoped, not bought off a card.
What this means for you
If you’re evaluating us against fixed-bid agencies, compare lifetime cost, not the upfront number. Ask the fixed-bid agency what their post-launch maintenance looks like, and price it in. The honest version of their answer is “hourly, when you ask.” Ours is on the page.
If you want to see the price ladder broken down by stage, with the explicit upgrade triggers, it’s on /pricing. Or just tell us what you’re trying to do and we’ll suggest a shape.