· WPbyAI Research · WordPress Maintenance · 2 min read
WordPress Maintenance Plan vs AI Change Subscription
Ongoing AI editing capacity and managed WordPress operations solve different problems, carry different risks, and should not be sold as the same subscription.
An AI change subscription pays for bounded website modification capacity. A managed maintenance plan pays someone to take continuing responsibility for production health. They overlap, but they are not interchangeable.
Confusing the two creates unrealistic expectations: a customer assumes a low-cost editing plan includes emergency recovery, security response, backups, plugin updates, monitoring, and unlimited human work.
What an AI change subscription can reasonably cover
A controlled change plan may include a quota of standard jobs such as:
- editing approved text, images, links, or contact information;
- adjusting an existing section within the approved design system;
- adding a normal content page from an accepted pattern;
- updating navigation or an existing form field;
- producing a versioned preview and rerunning affected checks;
- exporting the resulting source and change record.
New payment flows, membership logic, database migrations, security incidents, major plugin changes, redesigns, and production outages require separate review.
What Managed Care would need to add
A real care plan may include scheduled backups, restoration tests, update previews, controlled plugin and core updates, uptime and security checks, recovery points, a monthly report, and an agreed response window.
That is an operational responsibility. It needs real evidence that backups restore, updates can be rolled back, access is controlled, alerts reach the right person, and the support workload fits the price.
WPbyAI’s current boundary
The private pilot does not publicly sell Managed Care. The current workflow aims to deliver C-verified, editable source and evidence. Continue is also marked as not yet on sale while automation cost, exception rates, and customer retention are measured.
This boundary protects both sides: customers can see what a price actually buys, and the service does not disguise an untested support promise as a software feature. Review the current pilot pricing and availability before submitting a project.