First, establishing whose licence this runs on
On a white-labelled install the builder is often registered to the agency that built the site, not to the owner. While that holds, updates depend on somebody else's subscription and can stop without warning. The first month of care is partly administrative: finding out whose key is in use, and if it is not yours, getting you onto one that is. It is a dull piece of work and it is the difference between a site you control and one you rent from someone who has stopped answering.
Clearing a backlog without breaking a good site
A two-year update gap is applied in order on a staging copy, not all at once on the live site — core and PHP compatibility first, then plugins in dependency order, with the builder itself last so any layout change is attributable. Beaver rarely causes trouble here, which means when something does move, it is almost always another plugin and we can say which. Live is updated once staging is clean.
Monthly updates, checked on the pages that matter
After the backlog, updates are applied monthly on staging, with the templates and the highest-traffic pages checked visually before anything reaches production. On this builder the check is quick precisely because the output is stable, so the time goes where it is useful — the contact form still sending, the checkout still completing, the header still rendering at phone width.
Backups that include the licence state
A restore that brings back the files and database but not a working builder licence is a restore you find the limits of at the worst moment. Backups here capture the site as installed, keep enough history to go back past a problem noticed late, and get restored to a scratch environment periodically so the restore itself is proven rather than assumed.
Small changes, done in the builder your team already knows
Copy edits, new staff, a price change, a seasonal banner. These are made in the builder rather than in code wherever possible, so your team can still do the same job themselves next time. Where a change keeps recurring, we convert the piece into a saved module once, which turns a repeated forty-page edit into a single one. Plan hours cover this work.
Uptime and forms, because silence is the usual failure
The way these sites fail is quietly: a form stops delivering after a host changes its mail handling, or SSL lapses, and nothing announces it. Monitoring covers availability, certificate expiry and a periodic test submission through the site's own forms, because a contact form that silently stopped a month ago costs more than any outage on a site this size.
What the plans cost
Care starts at $159/mo a month covering monitoring, updates, backups and small changes. The development plan at $700/mo adds a standing allowance of build time for sites that change most months. Work beyond the included hours uses the same published rates as anywhere else — $750 and $1,400 for blocks, $165 hourly. Month to month, cancel whenever it stops being worth it.
