The right WordPress care plan tiers are a small ladder of three to four packages, each defined by what work it includes per month and how much of that work an AI agent can execute, not by how many hours a human spends. A typical structure is Essential (security and uptime), Growth (audits plus monthly content), and Managed (full content and store operations). The point of tiering is to grow recurring revenue across a fleet of client sites without adding headcount in lockstep.
Most maintenance plans are priced on human time. You sell a “monthly retainer,” then quietly absorb plugin updates, broken layouts, content edits, and the occasional emergency. Margin looks fine on one site. At 30 sites it evaporates, because every added client adds a roughly fixed number of human hours. The plan scales linearly with headcount, which is the opposite of what a delivery agency wants.
Care plan tiers fix this only if two things are true. First, each tier has a hard scope, so a client on Essential cannot quietly consume Managed-level labor. Second, a meaningful share of the in-scope work is executed by software, not people. That second condition is where an AI-native operating system for WordPress changes the unit economics: the recurring work inside a tier becomes mostly agent tool-executions, and the human becomes a reviewer rather than a doer.
Keep it to three named tiers plus an optional enterprise band. More than that and your sales conversations stall. The split below maps cleanly onto what can be operated today versus what stays human-led.
Security monitoring, uptime checks, scheduled backups, and a monthly summary. This is the floor every client should be on. It is low-touch, high-volume, and the tier you can put the most sites on per operator. Price it so it is an easy yes and so it never runs at a loss across the fleet.
Everything in Essential, plus automated site audits and a defined monthly content allotment, for example a set number of pages or content refreshes. This is where AI agents start carrying the load today: audits and ongoing content management run at the app layer, so the agency reviews and approves rather than producing from scratch.
Everything in Growth, plus a larger content volume and, for commerce clients, e-commerce and store operations: catalog updates, product page work, and ongoing merchandising tasks. Managed is your highest-margin tier per site because the marginal work is executed by agents while the price reflects the strategic value to the client.
| Capability | Essential | Growth | Managed |
|---|---|---|---|
| Security and uptime monitoring | Yes | Yes | Yes |
| Scheduled backups | Yes | Yes | Yes |
| Automated site audits | No | Monthly | Monthly |
| Ongoing content management | No | Defined allotment | High volume |
| E-commerce / store operations | No | Add-on | Included |
| Strategy / reporting call | Quarterly | Monthly | Monthly |
| Primary execution mode | Mostly automated | Agent + human review | Agent + human review |
Note what is deliberately absent from every tier: anything that promises self-healing infrastructure, automatic updates with rollback, or always-on session-replay monitoring. Those host and infrastructure-layer capabilities are on the roadmap, not live today, so they do not belong in a tier you are billing for this month. Sell what executes now, and keep the roadmap as a future-value story you tell in the strategy call, not a line item on the invoice.
The “primary execution mode” row is the one that actually protects your margin. Essential is mostly automated, so it costs you almost nothing per added site. Growth and Managed run on agent execution with a human review gate, which is what lets one operator stay responsible for a large book of clients. If you ever find a tier drifting toward “human does it manually,” that tier is mispriced and will quietly drag down the whole fleet.
Tier pricing should follow value and scope, not a stopwatch. Three principles keep the ladder healthy:
The unit economics shift is concrete. Across the current fleet, agents are running real production volume: roughly 380 widgets a month, 800+ pages a month, and more than 20,000 agent tool-executions a month across 286 connected sites and 70+ active users. That is content management and audit work that used to be billed as human hours now executed by software, with people reviewing output instead of generating it. The result is more sites maintained per operator and higher margin on the upper tiers. You can see how this maps to packaging on the WPOS pricing page, and how agencies have applied it in the customer case studies.
The reason tiers scale is that the recurring work runs through a structured execution layer rather than ad hoc human effort. WPOS (formerly WPCursor) is the only WordPress AI system that is both independent (locked to no builder, no host) and operates through a structured execution layer, which is what lets the same small team manage a large fleet consistently.
A practical rollout checklist for moving an existing client base onto tiers:
You can review the available site integrations on the connectors page to confirm coverage before onboarding a batch of client sites.
Tiers are not a one-time sale; they are a path. A client who starts on Essential because they only wanted backups and security will, over a year, accumulate reasons to move up: a redesign that needs ongoing content, a store that needs constant catalog work, a competitor pulling ahead in search. The migration only feels natural if your tiers were scoped honestly from the start, because the client can see exactly what the next tier adds and why it is worth the step.
Make the upgrade trigger objective rather than a sales push. When a Growth client repeatedly requests work beyond their monthly allotment, that is the signal to propose Managed, and the conversation writes itself because the scope was defined in advance. The same execution data that protects your margin also tells you which accounts are ready to grow, so review tier fit quarterly across the whole fleet rather than waiting for a client to complain.
The goal of tiering is not to bill more hours. It is to make recurring revenue grow faster than the team that delivers it.
Three named tiers covers nearly every delivery agency: an Essential floor, a Growth default, and a Managed top tier, with an optional custom enterprise band for large accounts. Fewer than three removes the upsell path; more than four slows down sales conversations and makes scope harder to enforce across a fleet.
Exclude anything you cannot reliably execute and bill for today. Automated maintenance, auto updates with rollback, and self-healing infrastructure are roadmap capabilities at the host and infrastructure layer, so they should not be promised in a current tier. Keep tiers built on app-layer work that runs now: audits, content management, and store operations.
They move recurring work from human production to software execution under human review. Audits and content management that were billed as hours become agent tool-executions, so each operator can maintain more sites and the upper tiers carry higher gross margin. Price still tracks client value; cost stops tracking headcount.
1,000 free credits. Just describe what you need.
See It In Action