← All posts

27 July 2026 · 5 min read

Web design retainers UK: from one-off builds to recurring

Web design retainers UK: how freelancers turn one-off website builds into monthly maintenance income, what to include, and how to price it fairly.

Web design retainers UK freelancers rely on tend to come from the same source: a client they already built a site for. A plumber in Halifax who paid a fixed price for a five-page site last spring does not want to think about hosting renewals, plugin updates or a broken contact form ever again. He just wants it to keep working. That gap between what a one-off build delivers and what a small business actually needs, ongoing, is where a retainer sits, and it is far easier to sell to someone who already trusts you than to a stranger.

Why a one-off build isn't the end of the job

A website is never really finished. WordPress core and plugins need updating or a site becomes a security risk. Hosting and domains renew every year, sometimes at prices the client never notices creeping up. Content goes stale: opening hours change, a menu gets a new dish, a testimonial needs adding after a good review comes in. None of this is dramatic work, but almost no small business owner wants to do it themselves, and most don't know it needs doing at all until something breaks. A retainer is simply you agreeing to be the person who notices before they do.

What to actually include

The strongest retainers are specific rather than vague. “Ongoing support” means nothing to a client and invites scope creep for you. A clearer version covers a fixed list: hosting, an SSL certificate, core and plugin updates, a monthly backup, an agreed number of small content changes (say, thirty minutes or two changes a month), and a fast response time if the site goes down. Anything beyond that list, such as a new page or a redesign of a section, gets quoted separately. Writing the list down in the agreement, even a short one, saves the awkward conversation later about what “support” was supposed to mean.

Some freelancers add light monitoring to that list: keeping an eye on page speed, checking the contact form still submits, confirming the booking link still points at the right place. Given how often these exact faults go unnoticed by the business itself, as covered in dead booking links and broken forms cost you work, a monthly check like this is a genuinely useful thing to be paid for, not padding.

Pricing a retainer without underselling it

Retainer pricing in the UK varies a lot by what is included and the size of the site, so there is no single honest figure to quote here. What matters more than a target number is the logic: price the retainer against the time it actually takes you plus the value of being on call, not against what feels comfortable to ask a client who is used to a one-off invoice. A retainer that only covers your literal minutes, with nothing for availability and responsiveness, will feel underpriced within a few months once the first out-of-hours emergency turns up. The same discipline that applies to one-off pricing, set out in how much to charge for a website as a UK freelancer, applies here too: work out your real cost of doing the job properly before naming a number.

It is worth billing retainers monthly by standing order or card rather than invoicing on request. A retainer that has to be chased every month behaves like ad hoc work with extra admin, and clients pay a fixed line item more reliably than an irregular invoice they have to remember to authorise.

Pitching the switch to an existing client

The easiest moment to introduce a retainer is a few weeks after launch, once the client has had time to notice the site working without them having to think about it. Framing it as protection rather than upsell tends to land better: not “would you like to pay me monthly” but “here's what I'll keep an eye on so the site doesn't quietly stop working the way the old one did.” Mentioning a specific, plausible failure mode helps make it concrete: an expired SSL certificate showing visitors a security warning, or a plugin update that breaks the booking form overnight with nobody noticing for a week. You are not inventing risk, you are naming the ordinary risk that every unmaintained website carries.

Some clients will decline, and that is a reasonable outcome too. Not every five-page site for a sole trader needs an ongoing arrangement, and pushing one on a client who genuinely doesn't need it costs you goodwill for very little revenue. The pitch works best on clients with a booking system, a contact form doing real work, or content that changes often enough to need a hand.

Where retainers change the shape of the business

A handful of one-off builds a year is unpredictable income. A base of even ten or fifteen retainer clients, each paying a modest monthly fee, gives a freelancer a floor to plan around, and it changes how each new build gets priced too, since a build that has a retainer attached from day one is worth more to you than one that ends the relationship at handover. It also compounds: every new build is a chance to add another retainer client, and every retainer client is someone who is far more likely to refer you than a client you finished with a year ago and never spoke to again.

None of this requires a large agency to run. A simple spreadsheet of who is on retainer, what is included, and when each renewal or update is due is enough at small scale. Patchscout is built for finding the next client rather than managing existing retainers, but the same audit it runs when searching a trade and town, checking speed, mobile behaviour, SSL and site builder, is a reasonable model for what to check on your own retainer clients each month. The three free searches on Patchscout are enough to see how the audit works before deciding whether it is useful for your own client list.