BLOG
BlogGuides

Add functional checks to a website care plan

Care plans sell updates, backups and uptime. A nightly test that the form, booking or checkout still works is the check clients notice and understand.

What a care plan usually covers#

A WordPress care plan, in the words of one hosting company's guide, should include updates, backups, uptime monitoring, security checks, performance reviews and monthly reporting. Those protect the site from going down or being hacked. None of them checks that the site still does its job: that the form sends, the booking books, the cart checks out.

That gap is exactly where clients get hurt, because a site that is up and broken looks fine to every monitor. It is also the easiest value to explain: "every night we check that your booking form works, and here is last night's run."

What to add#

For each client, pick the one to three journeys that make them money:

  • the contact or quote form, all the way to the confirmation email,
  • the booking flow, ending in a confirmation,
  • the cart and checkout, as far as is safe on production,
  • the member sign-in, for membership sites.

Write each as a plain-language test, put it in the client's project, and add a nightly schedule. Point the schedule at a time after your update window, so the night's updates are what it checks.

Reporting it#

Clients renew what they can see. One maintenance writer puts it bluntly: the retainer is renewed by the report, not by the work. Add a line to the monthly report:

Booking form: checked every night this month, 30 of 30 passed. Last run: [link].

The link is a share link to the latest run, with its replay and video. When a check fails, you hear first, by email or Slack, with what broke and where, and you fix it before the client calls.

Pricing it#

Every scheduled run counts toward your plan. One test nightly is about 30 runs a month per client. Plan and usage shows the runs by project, so you can see what each client's checks cost and price the care plan tier accordingly. See what a browser test suite costs.

Be clear about what it is#

It is a functional check, not a security scan, uptime monitor or backup. Keep those, and sell this alongside them.

This post is part of Find the bug before your client does.

Filed underWebReleases and regressionsClient sitesSharing and alerts