Launch is the first version,
not the last.
The site keeps its author: four senior days a month, a release every month, and a quarterly look at the architecture that issues a new version of the document.
£2,000 a monthfour days · rolling after three months · Studio at £4,000 for eight
Why the site should keep its author
The site keeps its author
The person who decided the structure, rode the prototypes and wrote the code is the person who changes it. No agency handoff to a maintenance team, no freelancer learning the codebase — the same hands, every month.
A release every month
Four senior days, planned together at the start of the month and shipped by the end of it: new sections, new content types, a landing page for a campaign, the things a live site teaches you it needs.
The architecture keeps its version
Every quarter, a look at the site against its architecture: what’s changed, what the numbers say, what the next floor should be. It issues a new version of the document — so the site is never the thing that was launched and left.
The rhythm
A month,
and a quarter.
A short call to set the month’s priorities. The days go where they matter; nothing gets started that won’t ship.
The work, on preview links as it goes. Fixes and small questions are answered as they come, not queued to the end.
Shipped, checked on devices, and written up in a line or two — what changed and why. The version number moves.
The site against its document: what’s changed, what the analytics say, what comes next. A new version of the architecture, issued.
Evolution
£2,000/mo4 senior days a month · rolling after 3 months
The site keeps its author. A monthly release, a quarterly architecture version, priority on everything you send.
Studio
£4,000/mo8 senior days a month · rolling after 3 months
For a business with a roadmap: the same rhythm at twice the pace, and a seat in your planning.
Every Repositioning includes its first ninety days of Evolution. After that, it’s a decision you make having seen what a monthly release does.
Questions
The things
people actually ask.
Is this only for sites you built?
Mostly, because that’s where the author is. A site I didn’t build can come in through an Architecture Review first — a week and a real document — after which I know it well enough to keep it properly.
What counts as a day?
A focused senior day of design or build, whichever the month needs. Four a month, planned together. Unused days roll over one month, so a quiet month isn’t a wasted one.
What’s the commitment?
Three months to start, then rolling monthly with thirty days’ notice. No lock-in beyond that; pause it if the business needs to.
How is it different from Design Partner?
Design Partner is for product teams and agencies: senior days inside their own process. Evolution is for the business that owns the site, and the quarterly architecture version is the difference.
Can it scale up?
Yes — Studio is eight days a month at £4,000, for a business with a roadmap rather than a wish list. Move between them at a month’s notice.
Isn’t a retainer just a subscription for fixes?
It shouldn’t be, and this one isn’t. Fixes happen, but the month is planned around what moves the site forward, and the quarter is planned around the architecture. The support hours after a launch cover the fixes; Evolution is for the next version.
Keep the site
moving.
If I built your site, a call is all it takes. If I didn’t, an Architecture Review first — a week and a real document — and then I know it well enough to keep it properly.