A WordPress maintenance contract is not a line that says “we look after the site”. It is the list of what is done, how often, and what stays out of scope when checkout breaks at 2 a.m.
What the contract must write down
- Updates to WordPress, plugins and the theme, with a copy before each lot.
- Backups that have been restored — a backup never tested does not count.
- A response time, in business hours, and after hours if there is one.
- The perimeter: one site, or a fleet. They are not priced the same.
- What is out: a redesign, a new shop, a host migration.
Why “unlimited” packages lie
Updating twenty sites on a Tuesday is not the same job as bringing WooCommerce back after a PHP bump. An honest contract splits routine from incident. wpmcp is built for that split: a dry run, a confirm token, a copy, a rollback — and a log of what was touched.
A fleet changes the paper
Past one site the question is not “who updates” but “which are late, and which break if we push”. A WordPress maintenance contract for an agency needs an inventory, not only a per-site checklist.
