A care plan is worth paying for if it covers hosting, SSL, backups you can actually restore, software and security updates, uptime monitoring, and a real person who answers. Mine start at $65 a month for that, $145 for a busier site, and $275 for ecommerce. It should be month to month, and leaving should not be a fight.
It is a rip-off when it is mostly hosting with a markup, when "unlimited support" turns out to have limits nobody wrote down, when the backups have never been tested, or when cancelling means you lose access to your own website. Those four patterns cover nearly every bad plan I have seen.
What you are actually paying for
The confusing part is that a care plan looks like it is for hosting, and hosting is the cheapest thing in it. You can buy hosting for a few dollars a month. Nobody is charging you $65 for server space.
What you are paying for is that somebody is responsible. Software your site depends on gets updated. Certificates expire. Plugins develop security holes. Hosts have bad days. A site nobody maintains does not fail loudly on a Tuesday afternoon while you are watching. It fails quietly, usually in the checkout or the contact form, and you find out weeks later from a customer who gave up and went somewhere else.
So the real question is not "what does the plan include", it is "when something breaks at 9pm, whose problem is it".
The four things that make a plan worth it
Backups you can actually restore. Every host says they do backups. Far fewer have ever restored one. An untested backup is a belief, not a safeguard. Ask when the last restore test was, and if the answer is vague, treat the backups as decorative.
Updates and security patching, done deliberately. Not auto-updating everything and hoping. Updates break things, particularly on WordPress where a plugin update can take out a form or a layout. Somebody should be applying them and checking the site afterward.
Monitoring that a human sees. Uptime monitoring only helps if the alert reaches someone who acts on it. A dashboard nobody looks at is not monitoring.
A direct line. The single biggest practical difference between a good plan and a bad one is how long it takes to reach someone who can actually fix the thing, rather than someone who will log a ticket about it.
The rip-off patterns
"Unlimited support" with undisclosed limits. There is no such thing as unlimited, and every provider knows it. The honest version states the limit. My plans include a defined amount of edit time and say so; work beyond it is quoted at $85 an hour before I begin, so nothing arrives as a surprise. The dishonest version says unlimited, then quietly rations you, and you find the real limit by irritating someone.
Marked up third party costs. Domains, platform subscriptions, plugin licenses, and payment processing should stay in your own accounts and be billed to you directly. When they run through a provider with a margin on top, you are paying a recurring fee forever for a bill they forward. Ask directly whether anything is marked up.
Hostage hosting. This is the worst one. If cancelling means losing access to your own site, you were never a client, you were a tenant. You should be able to leave with your code, your content, your domain, and your data. Mine are month to month with no contract, and if you go I help you move and hand over everything. That is not generosity, it is the minimum.
Edit time that rolls over and then does not. Watch how included time is described. Mine does not roll over month to month and the plan says that plainly, because a plan that implies you are banking hours and then does not honour them is a complaint waiting to happen.
A plan that is really a redesign fund. New pages, redesigns, and new features are project work, not plan work. A plan that blurs the line either costs too much for maintenance or quietly refuses the work when you ask.
What a plan should not cover, and why that is fine
It is reasonable for a plan to exclude new pages, redesigns, and new features. Those are projects with scope, and pretending otherwise leads to either a very expensive plan or a lot of arguing.
It is reasonable for third party licenses, domains, and processing fees to be billed to you.
It is reasonable that recovery from changes made by other people with access is billed hourly. If somebody else edits the site and breaks it, that is a repair job, not maintenance.
What is not reasonable is any of that being discovered after the fact. All of it should be written down before you sign.
Do you actually need one?
Honestly, not always, and I will say so.
If your site is a handful of static pages, rarely changes, is not built on something that needs constant patching, and you are comfortable knowing that if it goes down you will call someone and pay hourly, you can skip it. That is a legitimate choice and I would rather you make it knowingly than be talked into a subscription.
You probably do need one if the site takes payments, if it runs on WordPress with a stack of plugins, if leads come through a form you would not notice breaking, or if nobody in your business would spot an outage for two days.
The questions to ask before you sign
- What exactly is included, in writing, and what is explicitly excluded?
- How much edit time, and what happens when I use it up?
- When did you last restore a backup, and how long does it take?
- Who do I contact when it breaks, and what is a realistic response time?
- Is anything marked up?
- If I leave, what do I take with me and who helps me move it?
If the answers to those six are clear and written down, the price is probably fair whatever it is. If they are vague, the price does not matter.
All three of my plans and everything they include and exclude are on the pricing page, and the hosting and maintenance page goes through it in more detail.