A WordPress care plan should include, at minimum, six things: scheduled updates, off-site backups, security monitoring, uptime and performance checks, a bounded content-edit allowance, and a monthly report. Those are the non-negotiable line items. Everything beyond them — staging-tested updates, WooCommerce operations, tighter SLAs — is how you differentiate tiers and protect margin.
This is the practical checklist version. If you’re defining or auditing a care-plan offer for a delivery agency, work through each section below and decide explicitly what’s in scope, what’s billed separately, and what service level you’re committing to. The discipline of writing it down is what separates a profitable product from a slow margin leak.
Every credible care plan, regardless of price, includes these. Treat them as the floor, not the ceiling.
Most catastrophic care-plan failures trace back to one of these two categories being sloppy. Get them right and you have eliminated the majority of emergency calls.
The value of monitoring is that you find out before your client does. A care plan that only reacts when the client emails “the site is down” isn’t a care plan — it’s a help desk with a worse name. Include continuous coverage and a defined response.
The line items above are where the work lives. The boundaries below are where the profit lives. Most agencies lose money on care plans not because the tasks are hard, but because the scope is fuzzy.
For how these boundaries translate into actual tier pricing, the WPOS pricing structure is a useful reference point for what scoped, repeatable operations cost at fleet scale.
Ambiguity is what kills care-plan margin, and the cure is a matrix that states, line by line, what is included, what is billed, and what is excluded. Drop something like the following into your statement of work and revisit it whenever a client request makes you hesitate about whether it’s covered.
| Item | Status | Notes |
|---|---|---|
| Core, theme, plugin updates | Included | Defined cadence, staging-tested on higher tiers |
| Off-site backups and restores | Included | Routine restores included; data-loss recovery from client error may be billed |
| Security scanning and hardening | Included | Cleanup after a confirmed breach may be a separate incident charge |
| Minor content edits | Capped | Up to the tier allowance; overage billed at the hourly rate |
| New page builds and design work | Excluded | Quoted as a separate project |
| Custom development | Excluded | Scoped and billed independently |
| SEO and content campaigns | Excluded | Separate retainer |
The point of the matrix isn’t legal armor — it’s a shared reference that lets your delivery team say “that’s out of scope, here’s the quote” without inventing the answer on the spot. Consistency across the fleet is what makes the plan a product rather than a per-client negotiation.
The checklist above assumes a human performs each item on each site. That assumption is exactly what caps your margin once the fleet passes a few dozen sites. The agencies pulling ahead are folding an AI-native execution layer into their care plans so the repeatable work scales without proportional headcount.
Concretely, the application-layer items on this checklist — automated audits, ongoing content management, and store operations — can be executed today through a structured layer rather than by hand. WPOS is the only WordPress AI system that is both independent of any builder or host and operates through that structured execution layer rather than touching the raw site directly. Across the connected fleet that already translates to over 800 pages produced per month and more than 20,000 agent tool-executions per month. For the underlying model, see what WPOS is, and review the available connectors to understand how it plugs into an existing stack.
Keep the seam honest with clients. Application-layer operations — audits, content, store ops — are automated now. Infrastructure-layer autonomy such as self-healing and automatic rollbacks is on the roadmap, not in today’s product. Include the former in what you promise today; describe the latter as direction, not delivery.
Practically, that means rewriting your checklist in two columns: the items a human still has to own, and the items the execution layer can run on a schedule. As more of the routine work shifts to the second column, you can either widen what each tier includes at the same price, or hold the scope and let the freed-up time go toward higher-value work the client will pay a premium for. Either way, the checklist stops being a labor estimate and starts being a margin lever.
There’s no universal number, but most agencies cap entry tiers at 30 to 60 minutes of edits per month and mid tiers at one to two hours. The key is to express it as a hard cap and define what counts, so a “quick edit” request can’t quietly turn into an unpaid redesign. If a client routinely exceeds the cap, that’s a signal to move them up a tier or onto a separate retainer.
It can, but bundling hosting changes the economics and your liability. Many agencies keep hosting as a separate line so the care plan stays portable across whatever host the client uses. If you do bundle it, be clear about what the care plan covers at the application layer versus what the host covers at the server layer, so accountability is never ambiguous during an incident.
At minimum: updates applied, backups taken, security scans run with any findings, uptime percentage, performance trend, and edits completed against the allowance. Keep it skimmable — a client should grasp the value in 30 seconds. The report is the single most important retention tool in the plan, because it makes invisible work visible at exactly the moment budgets get reviewed.
Want to build a care plan whose checklist scales without scaling headcount? Look at how WPOS structures its plans for agencies running maintenance across a fleet, or sign up for the WPOS beta to test the execution layer against your own sites.
Part of our guide: WordPress Maintenance Plans at Scale: Agency Guide.
1,000 free credits. Just describe what you need.
See It In Action