WordPress care plans: what to include and how to price them

What is a WordPress care plan?

A WordPress care plan is a recurring service, usually billed monthly, under which someone keeps a WordPress site updated, backed up, monitored and supported for a fixed fee. You will also see it called a maintenance plan, a website care plan, a site care package or a support retainer. The structure is the same.

What separates a care plan from ad-hoc fixes is that the scope is written down. A plan that does not say what is included, what is excluded, how fast you respond and how the work is reported is not a plan. It is an expectation waiting to be disappointed. Our free WordPress care plan template gives you that structure in three tiers.

Does every WordPress site need a care plan?

No. A personal site with a handful of plugins and nothing riding on it can be looked after by its owner. The test is how much the business depends on the site, not how cheaply updates can be clicked: a site that takes orders, books appointments or brings in leads needs someone accountable for it every month.

If you own the business and would rather keep that work in house than pay a retainer, the same routine can be run with software. See WordPress management for business owners. The rest of this guide is written for the people who sell care plans: freelancers, agencies and website care businesses.

Why sell WordPress care plans?

Stable revenue is the obvious reason. Project income is lumpy and care plan income is not, and a base of recurring revenue changes how a business behaves: you can turn down bad projects, hire ahead of demand and survive a slow quarter. It is why so many people start a WordPress maintenance business alongside their build work, or instead of it.

The less obvious reasons matter as much:

• Retention. A client on a care plan hears from you every month. When they need a new project, you are already there.
• Fewer emergencies. Sites you maintain break less, and sites that break less generate fewer panicked phone calls on both sides.
• Business value. Recurring revenue with documented delivery is far easier to sell, or borrow against, than project income.

How should updates be handled under a care plan?

Updates are where a care plan earns or loses trust, because they are the work most likely to break a site. A professional process never pushes an update onto a live site and hopes:

1. Take a restore point first, so any change can be undone.
2. Test risky updates on a staging copy before they reach production.
3. Check the site afterwards: does it load, do the key pages look right, do forms and checkout still work?
4. Roll back automatically if a check fails, then tell someone.
5. Record what changed, so the monthly report writes itself.

Done by hand across a portfolio, this is the step that eats the week, and it is the strongest case for automation. WPCentrify runs safe updates with automatic rollback on every site you manage.

How much should you charge for a WordPress care plan?

Build the price rather than picking it. Work out your delivery cost per site, divide it by one minus your target margin, and that is your floor. Then check the floor against what the market supports and what the site is worth to the client. Observed prices run from about $29 a month for a basic plan to $400 for a priority plan, with managed retainers above that.

The arithmetic

Monthly delivery cost per site = (hours per site x your effective hourly cost) + (tooling spend / number of sites). Your floor = delivery cost / (1 - target margin).

For example, a site that takes 1.5 hours a month at an effective cost of $65 an hour, plus $13 of tooling, costs $110.50 to deliver. At a 60 percent target margin the floor is about $276. If you charge $95 for that site, the plan loses money and no efficiency elsewhere fixes it. The care plan calculator runs this with your own numbers, and the maintenance ROI calculator shows what manual delivery costs you now.

Three ways to set the price

• Cost-plus. Hours times rate, plus margin. Simple and defensible, but it anchors the price to your cost rather than the client's risk, so it underprices critical sites.
• Value-based. Priced against what downtime or a hack would cost the client. It captures more on revenue-critical sites and is harder to justify on a small brochure site.
• Tiered hybrid (recommended). Three published tiers with a cost-plus floor, revenue-critical sites priced against risk, a tracked support allowance and margin reviewed per account each quarter.

What margin to aim for

Aim for 55 to 75 percent gross margin once routine work is automated. Below 40 percent a plan cannot absorb a single bad month on that account. The full guide to pricing WordPress maintenance covers price rises, per-site versus per-client pricing and what to do about underpriced accounts.

What should a care plan exclude?

The excluded list does more work than the included list. State plainly that these are outside the plan and quoted separately:

• Content edits beyond the stated allowance
• New features, new pages and design changes
• Third-party integrations and their ongoing support
• SEO, advertising and marketing work
• Recovery from problems caused by client changes or third-party developers
• Migration to new hosting, unless stated
• Training beyond a stated allowance

Ambiguity always resolves in the client's favor and against your margin, not because clients are difficult but because everyone reads a vague scope generously in their own direction.

How do you sell care plans to existing clients?

Run a pre-sales audit instead of a pitch. Show the client the current state of their own site: known vulnerabilities, abandoned plugins, when the last backup ran, whether a restore has ever been tested and how Core Web Vitals look. A maintenance proposal template that leads with the audit does most of this for you.

It works because it is specific and true, and it moves the conversation from "would you like to buy maintenance?" to "here is the current risk, and here is what it costs to remove it." Most people say no to the first and yes to the second.

Lead with consequences rather than features. Offer Standard by default, not the cheapest tier. Price against what a problem would cost, not against your hours. And be willing to walk away from a client who wants the protection without paying for it.

Selling the plan is only the start; our guide on how to manage WordPress clients covers the onboarding, access, reporting and handover that follow.

What goes in a care plan agreement and SLA?

A care plan agreement does not need to be long. It needs to state:

• Scope, included and excluded, in plain language
• The support allowance and what happens when it is used up
• Response targets, and whether they are targets or commitments
• Any uptime commitment, and what happens if it is missed
• What data you hold and how it is protected
• The notice period, in both directions
• What happens at the end: data handover, access removal and a final backup

Only offer an SLA with a remedy attached if you can meet it and measure it. An uptime promise you cannot measure is worse than none, and a service credit you have not budgeted for is a liability. Uptime monitoring from three locations gives you the record to back a commitment.

How do you report on a care plan so clients renew?

Care plans rarely get canceled because the work was bad. They get canceled because the work was invisible: a month with no downtime, no hack and no broken form looks, from the outside, exactly like a month where nothing happened. The monthly report is the only regular evidence that anything is happening, so as far as the client is concerned it is the product.

• Send it on the same date every month. Predictability is most of the value.
• Lead with outcomes, not changelogs. Availability, problems prevented, work completed and hours used come first. Version-by-version detail goes underneath for anyone who wants it.
• Brand it as yours. A report carrying a vendor's logo invites the client to look up what that vendor costs.

Our WordPress maintenance report template shows a structure clients read, and white-label client reports can assemble it automatically from the work already done. Beyond the report, retention comes from being visibly useful: a quarterly conversation about the site rather than the plan, and flagging problems before the client notices them.

How do you know which care plans make money?

Most care plan businesses cannot say which accounts are profitable, which is how unprofitable ones survive for years. Track four numbers per client: recurring revenue, hours used (support conversations included), labor cost at your effective rate and gross margin.

Review them every quarter. A small number of accounts usually consume a large share of support, and they are rarely the ones paying the most. Once you can see it, you can raise the price, reduce the scope or end the relationship. All three beat not knowing. Care plan profitability tracking works this out per client from work already recorded.

What changes when you pass fifty sites?

Care plan operations break at predictable points. Around fifteen sites, doing the work by hand stops fitting into the week. Around fifty, the problem becomes coordination rather than labor: who is doing what, on which site, under which plan.

What has to be in place by then:

• Automated delivery of routine work, with verification, so labor grows with exceptions rather than with site count
• Role-based access, so work can be delegated without sharing admin passwords
• A documented policy per tier, so behavior is consistent whoever is on shift
• Tracked support allowances, so scope drift is visible before it becomes permanent
• Per-client economics, so growth does not quietly reduce margin

None of this is exotic. It is what stops being optional once the operation is bigger than one person's memory. The guide to managing multiple WordPress sites covers the workflow side in more depth.