A maintenance plan keeps the software current: updates, backups, uptime checks. A fractional retainer buys ownership of the outcome, including the failures that never produce an error message. They are different products, not the same product at two prices.
The most useful question I get asked is some version of this: “I already pay someone every month, so why is anything still broken?”
It is a fair question, and the answer is almost always that the thing being paid for and the thing being expected are two different products. A website maintenance plan keeps the software current: updates applied, backups taken, uptime watched. A retainer makes one person answerable for the outcome: the system works, and it changes when the business changes. They are not the same product at two prices, and nearly every complaint I hear about a maintenance plan comes from paying for the first while expecting the second.
Both are legitimate. They answer different questions, and the useful thing is to know which question you are asking.
You find out which one you bought on a bad week
On a good week the two products look identical. Nothing needed doing, and both invoices match last month’s.
On a bad week the difference is plain. A plan answers “were the updates applied?” A retainer answers “why did enquiries stop arriving on Thursday?”, and then tells you it is fixed. The first is a checklist. The second is an outcome, and only the second protects revenue.
Buying the wrong one is expensive in a quiet way. You are not overpaying. You are underinsured: paying real money every month for a service that was never designed to catch the thing that eventually costs you.
Side by side, the difference is in what each product is built to notice.
| What you are comparing | Maintenance plan | Retainer |
|---|---|---|
| What it protects | The software | The outcome |
| Who does the work | Mostly automated, reviewed in bulk across many sites | One named senior engineer |
| What counts as a problem | The site is down, or an update failed | Anything between your customer and the result |
| Changes and improvements | Quoted separately, or not offered | Included within an agreed scope, worked in priority order |
| Who notices a silent failure | Nobody, until you do | The monitoring, then the engineer |
| What arrives each month | A report that the updates ran | A note on what changed, what it showed and what comes next |
| Right when | The site is simple and stable | The systems carry revenue |
A good maintenance plan earns its fee
I want to be fair to the plan, because a good one is a real product and worth its price. It applies core, theme and plugin updates. It takes backups and, if it is any good, now and then proves that one actually restores, which is rarer than it should be. It watches uptime and tells you when the site stops answering. It applies security patches inside a stated window.
That work is necessary. Skipping it is how sites end up compromised, usually through a plugin nobody updated, or one that came from somewhere it should not have (how to check for nulled plugins). The market price reflects a service that is mostly automated and reviewed across many sites at once, which is why it can sell for €90 a month and still make sense for the provider.
What it buys you is the absence of one specific disaster: the site that fell over because nobody updated anything for two years.
BespokeForge sells a plan of its own, and sells it as exactly that. Upkeep is the routine for a system built or rebuilt here: updates with a check afterwards that the pages still render, security monitoring and patching, offsite backups with a restore that has been tested, certificate and domain expiry watched, and a short note every month, including the months when nothing needed doing. The monitoring is automated, and a person approves every change. It leaves out the server, content changes, new pages and features, performance and search work, and same-day incident response, because each of those needs a judgement call. It also sits outside the limit of three clients I take on at a time, because a system on the routine is built to need almost none of the attention that limit protects.
If what you need is the second product, Upkeep is the wrong purchase, and I will tell you so.
A plan watches whether the site answers, not whether it works
The gap is everything that breaks without breaking. A plan watches whether the site responds. It does not watch whether the contact form still delivers.
Uptime was 100% and the enquiries had stopped
A forms plugin started dropping submissions after an update, without a sound. Every page loaded perfectly. Uptime was a clean 100%. The dashboard was green from top to bottom, and the enquiries had simply stopped arriving. Nothing in a maintenance plan is built to catch that, because by every measure a plan tracks, the site was healthy.
I keep meeting the same shape in different clothes. Scheduled jobs that had never once run, because WordPress fires its scheduled tasks from page loads and a quiet site never triggers one. A caching layer reporting a successful purge while it went on serving stale pages, because the routine it called had stopped existing. An image in the newest, smallest format making phones slower than the older format it replaced, because decoding it cost more than downloading it saved. I measured that one over ten runs. It took me the better part of a week to pin down, and I was looking for it. Speed problems of that kind are common enough to have their own guide: why your website is slow.
None of those produced an error message. None appeared on an uptime dashboard. Each one cost money for as long as it ran.
That is the line between the two products in one sentence. A maintenance plan can tell you the site is up. It cannot tell you the site is working, and only the second is about your revenue.
A retainer month is quiet work, written down at the end
Retainers have a reputation problem, earned by every agency that ever invoiced monthly for work nobody could point to. So here is what a month on a retainer with me contains, in the order it happens. Nothing glamorous appears below, which is rather the point. A retainer covers the whole system, from the servers and the site to the customer data and the automations that move it (the four disciplines), and the Operate page lists what each of the three retainers, Maintain, Partner and Embedded, includes.
Monitoring runs underneath everything
Uptime checks, performance baselines, security signals and backup verification run all month. Most months this layer produces nothing but quiet confirmation. In the month it produces an alert instead, you hear about the problem from me, with a diagnosis attached, rather than from a customer or a blank screen. It is the part of the retainer you cannot see and would miss most.
A maintenance pass stops the slow rot
Every month carries a maintenance pass. Security updates go on, dependencies come current, and from time to time a backup is restored somewhere safe to prove it still works. The pass also catches the small degradations that every live system collects: a database that has grown sluggish, a plugin update that needs reading before it can be trusted, a disk creeping towards full. Each one is trivial on its own. Together they are the difference between a system that lasts and one that quietly rots.
On a retainer the pass covers the server under the site as well as the site itself, which Upkeep does not.
Small change is part of the month, not a quote
Most of what a growing business needs is not repair. It is change: a form that should send enquiries somewhere else, a slow page made fast, a report that finally answers the question the business keeps asking. Under a plan each of those is a quote and a wait, and the small ones never happen at all (the pattern is one of the signs you have outgrown your web vendor). On a retainer they are a queue, worked in priority order. Maintain covers changes within the agreed scope. Partner adds automations built and kept running, and a view on what to build next. Embedded is the whole technical function. New pages, new features and rebuilds are a different thing: on any retainer, they are scoped and quoted before they start.
This is also where the part people underestimate shows up. When I have run a platform for a year, I do not need a discovery phase to change it. I know which part is fragile, which decision was deliberate, and which clever thing from two years ago everything now quietly depends on. Work that costs an outsider a week of orientation costs me an afternoon. You are not buying hours. You are buying the permanent absence of ramp-up.
When something breaks, the person who runs it answers
Systems fail. What the retainer decides is what a failure costs you. The monitoring usually gets there before you do, and the person who answers is the person who runs the system every month, which shortens every diagnosis. Every retainer handles incidents inside a written response window. When two things go wrong at once, Partner and Embedded come first, and the limit of three clients keeps that rare.
Upkeep handles a break differently, and says so in advance: the site is restored from the last tested backup, as part of the routine and without a response window; the note explains what happened, and any fix beyond that is quoted before it starts.
The month closes with a note in plain language
Every month ends with a note: what was monitored and what it showed, what was updated, what was built, what I recommend next, and anything that needs a decision from you. If the month was quiet, the note says it was quiet and why that is good news. You should never have to wonder what a retainer did for you. The answer arrives in writing.
The market leaves a wide gap between a care plan and an agency
The price bands explain most of the confusion, because the two products sit far apart and most businesses sit between them.
- Care plans in 2026 run from roughly €35 to €90 a month for the basics, €90 to €230 for a small-business plan, and €230 to €650 where ecommerce or higher assurance is involved.
- Growth retainers sit apart from both, starting around €800 and rising.
- Agency retainers run from roughly €1,500 to €4,000 a month for a single discipline, and €4,000 to €19,500 for full service. Both bands have risen more than 30% since 2023.
Most established businesses sit in the space between the top of the care-plan bands and an agency that covers more than one discipline. They are too complex for a checklist and too small to fund an agency’s overhead, and their problems tend to fall between disciplines rather than inside one. That space is where the market sells a retainer with one senior engineer, under the name fractional engineering. The name matters less than whether the person behind it actually holds your system.
Prices vary across Europe, and these are bands rather than quotes. The full table, with what each band realistically covers, is in how much website maintenance should cost. BespokeForge’s own prices are fixed and public on the pricing page.
For a simple site, the plan is the right purchase
This happens often, and I would rather say so plainly than pretend the answer is always the more expensive one.
A maintenance plan is the correct purchase when the site is simple, the content rarely changes, nothing commercially important depends on an integration, and a day of downtime would be irritating rather than expensive. A brochure site for an established local business is exactly this. I have talked people out of a retainer for that reason. Retainer money spent on a site like that is waste, and anyone telling you otherwise is selling. For some simple sites the better saving is a lighter platform with less to update, which is its own question: when a website should not be WordPress.
The plan stops being the right answer at a specific point: when something on the system carries revenue, and nobody’s job is that it keeps working.
A retainer is a fixed fee, not a bank of hours
No retainer here is sold as a quantity of hours, because a quantity of hours is a thing you can lose at the end of the month. The fee is fixed each month instead. Anything genuinely outside the retainer is quoted before it happens, rather than absorbed quietly and resented later.
The rest of the terms are short.
- It starts from a system I know. Every retainer starts from a system BespokeForge built or audited. Either it was built here and the same person runs it, or a system that already works well enough is adopted as it stands and, from a fixed date, one person is answerable for it.
- Three months, then month to month. A retainer runs for a minimum of three months, the time it takes to reach a steady state. After that it rolls monthly, with thirty days notice either way. There is no annual lock-in, because the only honest reason to keep paying is that leaving someone who already understands your systems does not make sense.
- The accounts are yours. You hold the domain, the DNS and the repository in your own accounts from the first week, and the server too unless you choose to host with BespokeForge, so leaving is designed for rather than negotiated at the end.
- Three clients at a time. BespokeForge is one engineer, with no account managers and no juniors. Each retainer takes one of three client places, because a fourth client would take attention from the other three. Upkeep takes none.
Your last three reports already show which one you bought
Before you change anything, ask your current provider for the last three monthly reports, and read them for what they mention rather than what the contract promises.
A report from a plan lists the updates applied, an uptime percentage and the backups taken. Those are real facts, and every one of them is about the software.
A report from someone who owns the outcome says what the monitoring showed and whether it mattered, what changed in the system and why, what was built, what comes next, and what needs a decision from you. Those are about your business’s systems as they are being run.
If the three reports only ever contain the first kind, you now know exactly what you are buying, and exactly what you are not. If there are no reports to ask for, you have your answer sooner. And if the provider has stopped replying altogether, that is a different and more urgent problem, covered in what to do when your developer stops replying.
Then put one question to yourself. If the contact form stopped delivering tomorrow, how long would it take for someone to notice? If the honest answer is “within a day, and it would be obvious”, the plan is fine, and you can keep your money. If the honest answer is “when someone rang to ask why nobody had called them back”, you do not have a maintenance problem. You have an ownership problem, and no amount of update-applying fixes it. Who should hold a system once it is live is the subject of who owns your systems after launch.
If the reports leave you unsure, the audit settles it. It starts with a free 25-minute call, which confirms whether the problem is one BespokeForge can solve and which of the two routes applies. The audit itself is paid, ends in a written document you keep whatever you decide, and its fee is credited in full against a build or a retainer that follows. The contact page sets out what it covers.