Recurring changes are not unlimited support
Content and approved layout changes can follow a repeatable preview-and-approval flow. Plugin migrations, incidents, architecture changes, and production emergencies require a separate decision.
WordPress care plans
Choose a WordPress care plan by the work it actually covers—not by a vague promise to handle everything.
A useful maintenance plan separates recurring site changes, operational care, hosting, licenses, incident response, and major projects. WPbyAI currently offers a private-pilot path for scoped work while Managed Care remains a future product gate.
Current public status: Care plan applications are open for fit review, but Managed Care is not yet sold. Backup restore, update rollback, permissions, response scope, and real operating cost must pass before launch.
Your site remains a deliverable asset
A plan should not erase source ownership, version history, licenses, hosting choices, or the customer-controlled handoff path established at C verification.
Backups matter only when restore is tested
Operational care must name update, backup, restore, rollback, monitoring, exclusions, and escalation evidence rather than treating a green dashboard as proof.
What happens next
A visible path, with a stop at every meaningful decision.
- 01
Inventory the site
Record WordPress, PHP, editor, theme, plugin, hosting, license, source, backup, and ownership facts before choosing a plan.
- 02
Separate the work
Classify recurring AI change jobs, operational checks, incidents, major changes, premium licenses, hosting, and production access.
- 03
Verify the route
Start with a scoped pilot, staging preview, acceptance criteria, and a measured human-review boundary before any recurring promise.
- 04
Open care only after evidence
Managed Care stays closed until real update, backup, restore, rollback, permission, alert, and cost tests have passed.
Included in this route
- A plan-fit review based on the actual WordPress stack and requested work
- A written distinction between recurring changes, operational care, hosting, and separate projects
- Versioned preview and approval for accepted private-pilot changes
- An ownership, license, handoff, and known-limitations record
- A waitlist route for future Managed Care validation
Not assumed or promised
- A currently purchasable Managed Care subscription
- Unlimited human edits, unlimited revisions, or an unlimited project queue
- 24/7 emergency response, security incident response, or guaranteed response times
- Hosting, premium plugin licenses, SEO growth, or production access unless explicitly scoped later
- Automatic acceptance of every WordPress, plugin, theme, or server stack
Frequently asked questions
Scope first. Promises second.
What should a WordPress care plan include?
A credible plan separates recurring changes, updates, backups, tested restore, rollback, monitoring, hosting, licenses, incident response, response scope, and major projects. Each item needs a stated boundary.
Are care plans, maintenance plans, and maintenance packages the same?
The labels often overlap in search and sales language. What matters is the written scope: included work, capacity, exclusions, ownership, evidence, production permissions, and the conditions that trigger a separate project.
Can I buy WPbyAI Managed Care now?
No. Applications and fit reviews are open, but Managed Care remains closed until update, backup, restore, rollback, permission, alerting, and real-cost tests pass.
Does a future care plan automatically include hosting?
No. Hosting, domains, premium licenses, production access, SEO growth, and incident response remain separate unless an approved offer explicitly includes them.
Choose the right route
Different WordPress needs should not be forced into one vague plan.
WordPress Maintenance Services
Use this route for a defined change that should be previewed and verified now.
View this route →WordPress Website Management
See how ownership, requests, versions, plugins, and evidence can be managed over time.
View this route →Pilot Pricing
Review the current validation prices and the capabilities that remain closed.
View this route →Limited private pilot
Tell us what you expect a care plan to handle.
Describe the site, recurring requests, current provider, plugin stack, and main operational concern. We will classify fit without pretending Managed Care is already available.