Website care plans get cancelled for one reason above all others: the client can't see what they're paying for. The work is real, it's just invisible. Nothing broke, so what exactly was the money for? Here's how to build one that survives that question.
Why the invisible-work problem is fatal
A good care plan is mostly prevention. Updates applied, backups verified, certificates renewed, a vulnerability patched before anyone noticed. Every one of those is a thing that didn't happen — and you cannot invoice a non-event unless you've made it visible first.
The plans that get cancelled are the ones where the client's entire experience is a monthly charge and silence.
What actually belongs in one
The maintenance floor
Core and plugin updates on a defined schedule, tested rather than blindly applied. Off-site backups with a restore that has genuinely been tested — an untested backup is a rumour. Uptime and certificate monitoring. Security patching.
The visible layer
A monthly summary in your branding: what was updated, what was caught, uptime for the period, anything worth knowing. This is the part that justifies the whole plan and it's the part most people leave out.
An allowance of real work
An hour or two of content changes included. This is what converts the plan from insurance into a service they use — and a client who emails you monthly is a client who doesn't forget you exist.
A named response time
Not "priority support" — an actual commitment you can meet. Vague promises get tested at the worst moment and remembered badly.
How to price it
Work out the real hours first. For a typical small business site, monthly maintenance is well under an hour once it's systematised — but the incidents are lumpy, so price for the average across a year rather than the quiet months.
Then decide what you're actually selling. If you price purely on the maintenance hours, you're selling a commodity and someone will always undercut you. If you price on the outcome — the site stays up, stays current, and someone answers the phone — you're selling the thing the client actually wants.
Two or three tiers works better than one. Most people don't want the cheapest option; they want to not pick the wrong one. A middle tier that's obviously the sensible choice does a lot of work.
Making the value visible every month
This is the whole game. The monthly summary should be boring, consistent and short. Uptime for the month. Updates applied. Anything caught before it became a problem. One line on what you'd suggest next.
Site was up all month. Applied eleven plugin updates and one core update, all tested. Renewed the SSL certificate three weeks before expiry. Contact form was getting spam, so we tightened the filter — submissions are clean now.
That takes two minutes to read and it makes the invoice self-evident. Send it whether or not anything dramatic happened — especially when nothing did, because a quiet month is the product working.
The bit that makes it scale
None of this survives being done by hand across twenty clients. The monitoring has to run itself, the reports have to assemble themselves, and your job should be the two sentences of judgement at the top. That's the difference between a care plan that's a nice side income and one that quietly becomes the most reliable part of the business.
White-label our monitoring and reporting inside your own care plan.
Partner pricing →