Most hosts already do a version of WordPress care for free: the ticket about a broken plugin update, the white-screen after a PHP bump, the “my site is slow” thread that eats an hour. A care plan turns that unpaid labor into a product with a price, a scope, and a team behind it. Here is how we have seen it work across the 1,000+ agencies and hosts that partner with Seahawk.
What a care plan actually covers
Write the scope down before you pick a price. A credible host-level care plan includes:
- Core, plugin, and theme updates on a schedule, with a visual check after each run and rollback if something breaks.
- Uptime and performance monitoring with alerting that goes to a human, not just a dashboard.
- Security hygiene: malware scanning, login hardening, removal of abandoned plugins, cleanup when something does get in.
- Backups you have actually restored, with a documented restore time.
- A small monthly task allowance (30 to 60 minutes) for the “can you change this banner” requests that otherwise become tickets.
Leave custom development, redesigns, and SEO out. Those are pro services with their own pricing, and mixing them into a care plan is the fastest way to blow your margin.
Three ways to package it
| Model | How it works | Best for | Watch out for |
|---|---|---|---|
| Bundled | Care is included in a “Managed WordPress” tier at a higher plan price | Hosts repositioning upmarket; simple to explain | Fulfillment cost on every customer, including ones who never need it |
| Add-on | Optional monthly line item on any plan | Hosts with a large existing base; easy to test | Needs active selling; attach rates stall without in-panel prompts |
| Tiered | Basic / Plus / Pro care, differentiated by task minutes, response time, and reporting | Hosts with agency and SMB customers on the same platform | More SKUs to support; keep it to three |
Most hosts start with the add-on model to learn attach rates, then fold a basic tier into their top plan once they know the cost per site.
Pricing and margins
Work backwards from the cost of fulfillment per site per month, not from what competitors charge. Your inputs:
- Automated work (updates, monitoring, backups) is nearly flat per site once tooling is in place.
- Human work is the variable: visual QA after updates, incident response, and the task allowance. Estimate minutes per site per month from your current ticket data, then add 20 percent.
- Support overhead: every care customer will contact you more, because they now feel entitled to. That is a feature, but budget for it.
A healthy target is 60 to 70 percent gross margin on the add-on price. If your human minutes push margin below 50 percent, the fix is usually tooling or a fulfillment partner, not a price increase.
Fulfillment: build, buy, or partner
You have three options for the human layer.
Build it in-house. Works if you already have WordPress engineers on staff and fewer than a few hundred care sites. Beyond that, scheduling update windows, QA, and incident response across the fleet becomes a full operations function.
Buy tooling only. A fleet platform handles the automated layer: scheduled updates, visual regression, monitoring, and reporting across thousands of sites from one console. WP Maintain was built for exactly this, with MainMonitor for uptime and performance, MainRank for search visibility tracking, and MainChat for customer-facing support inside the panel. Your team still handles escalations.
Partner for fulfillment. The human layer (QA, fixes, task requests, incident cleanup) is delivered white-label by a WordPress team under your brand. This is how most hosts scale past the first thousand sites without hiring a WordPress department. Seahawk has maintained thousands of WordPress sites this way, and acquired WP Services to productize the service catalog behind it.
Whichever you choose, define SLAs you can meet on a bad day, not a good one.
The support handoff
The place care plans fail is the seam between hosting support and WordPress support. Fix it with three rules:
- One intake, clear routing. Tier 1 keeps handling server, DNS, email, and billing. Anything inside wp-admin routes to the care queue with a tag, not a re-ticket. Customers should never be told “that’s a WordPress issue, not a hosting issue.”
- Shared context. The care team needs read access to the hosting account (PHP version, resource limits, recent restarts) and the hosting team needs the care history (last update run, open tasks). A platform like WP Maintain surfaces both in one view.
- A written escalation path for the ambiguous ones: site down after a plugin update, slow site caused by a theme query plus an under-sized plan. Decide in advance who owns it and who communicates.
Launching it
- Start with your top 10 percent of WordPress customers by plan value. They have the most to lose and already trust you.
- Offer the first month free to existing customers; attach rates rise sharply once the customer has seen one update report.
- Put the offer inside the control panel next to the WordPress install, not only on the marketing site.
- Send a monthly report. Customers who get a report renew; customers who hear nothing cancel the “thing they are not using.”
Next step
If you want the fleet tooling and an optional white-label team behind your care plan, WP Maintain is the platform Seahawk runs for web hosts and agencies: scheduled patching, MainMonitor, MainRank, MainChat, and a fulfillment team that has maintained thousands of WordPress sites. Talk to us about running a pilot on a slice of your fleet.