Sites that load fast and convert
Custom builds and integrations
Bounded, auditable, human-approved
Being found, staying fast, staying safe
Websites do not fail dramatically. They drift — a plugin update nobody applied, a contact form that quietly stopped sending three weeks ago, a certificate about to expire, a backup that has never once been restored to check it works.
A care plan is somebody holding the other end of that. Most of its value is in the incidents you never hear about, which makes it a genuinely difficult thing to sell and an obvious thing to keep once you have had one.
Move over the monitor ↓The case
Every one of these is silent. The site keeps loading, nothing looks wrong, and the damage is only visible if somebody is specifically checking.
A host changes its mail configuration, or a plugin update alters a setting. The form still shows a thank-you message. The enquiries simply stop arriving, and you assume business is quiet.
Caught by: a test submission on a schedule.
Backups run nightly and report success. Nobody has ever restored one. A meaningful share of untested backups turn out to be incomplete, corrupt or missing the database at the moment they are needed.
Caught by: restoring one, on purpose, on a schedule.
Disclosed publicly, patched upstream, unapplied on your site. Automated scanners find these within days, and the gap between disclosure and exploitation is often measured in hours.
Caught by: monitoring advisories, not just the update badge.
Your version stops receiving security fixes. Everything keeps working, so nothing prompts anyone, until a host forces an upgrade and something built for the old version breaks.
Caught by: tracking the calendar, not the symptoms.
An update changes a script, and payment fails on a specific browser or device. Traffic looks normal. Sales fall by a share nobody can attribute, and it can persist for weeks.
Caught by: automated checkout tests after every update.
An image library expires, an embedded map loses its key, a font licence lapses, a third-party script is discontinued. The page still loads with a hole in it.
Caught by: a person actually looking at the site.
Interactive
Drag the slider to however long it has been since anyone deliberately maintained your site. The figures are typical for a WordPress site running around twenty plugins — illustrative rather than a diagnosis of yours.
Notice that nothing on this list is dramatic at three months and most of it is serious by eighteen. That gradient is the whole problem: there is never a day when neglect announces itself, so there is never an obvious moment to act.
Interactive
Fourteen jobs that keep a site working. Mark each one honestly — us, your team, or genuinely nobody. The third column is the interesting one.
Almost every site we take over has five or six items in that column, and the owner is surprised by at least two of them. They are not neglected on purpose — they were simply never assigned to anyone, and nothing forces the question until something breaks.
Coverage
Monitoring is only useful if the alert reaches a person who can act. Ours go to us first, and to you when something needs a decision rather than a fix.
Platforms cared for
Monitoring & uptime
Backups & infrastructure
Where alerts land
The work
Most of it is routine and invisible. That is the intended state, not a sign nothing is happening.
Core, plugins, themes and dependencies updated on a staging copy, checked, then applied live — rather than clicked on a Friday afternoon and hoped over.
The part everyone means by "maintenance"
Files and database on a schedule, stored away from the server they came from, with a periodic restore into a scratch environment to prove they actually work.
An untested backup is a hope
Not just "does the homepage load". Whether the contact form sends, whether checkout completes, whether the response time has quietly doubled since last month.
Where most plans stop short
Advisories tracked for the specific components you run, access reviewed, unused accounts and abandoned plugins removed before they become the way in.
See Security & Hardening for the deeper work
A price update, a new team member, a changed opening time, a PDF swapped. Included up to an agreed amount of time so nobody has to raise a purchase order for ten minutes of work.
Often the most used part
What was updated, what broke, what we fixed, what needs a decision from you. One page, in plain language, not forty pages of automated charts.
Deliberately short
Shape
We do not publish a monthly figure, because a brochure site and a store taking orders overnight are not the same commitment. The shape below is what the levels differ on.
For sites where a few hours offline is inconvenient rather than expensive.
Response targetNext business day
For sites that generate enquiries or revenue, where a quiet failure costs real money.
Response targetSame business day
For sites where downtime is measured in lost orders and someone will be called at night.
Response targetAgreed, including out of hours
Honesty
This category contains a lot of low-effort recurring revenue, so it is worth being specific about where the line sits.
Plenty of plans are an automated update job and a generated PDF. If nobody stages the updates, tests a restore or checks that the form still sends, very little is actually being maintained.
Small changes are included. A new booking system is a project. We will always say which one something is before starting, not after.
Hosts fail, vendors break things, attacks happen. What a plan changes is how fast it is noticed, how contained it is, and whether a working backup exists.
If the site is built on something fragile, maintenance manages the symptoms. We will tell you plainly when you are paying to keep something alive that should be replaced.
We work with your host or arrange one, but a care plan is the attention rather than the server. Bundling the two makes it harder to leave, which is not the relationship we want.
Month to month, cancel with notice, and you keep every credential, backup and piece of documentation. A plan people stay in because leaving is painful is not a plan worth selling.
Questions
Because "works fine" is the state a site is in right up until it is not, and the failures described above are all invisible from the outside.
The honest answer is that if your site is a brochure that generates nothing and you can tolerate a week offline, you may genuinely not need this. If it produces enquiries or orders, the cost of one silent failure usually exceeds a year of the plan.
You can, and some clients do exactly that with a checklist we provide. The risk is that updating live without a staging copy or a tested restore path works ninety-nine times and is very expensive on the hundredth.
The updates are also the easy part. Backup verification, transaction monitoring and advisory tracking are the parts that rarely get done in-house.
Monitoring alerts us, usually before anyone at your company has noticed. We establish whether it is the host, an update or something external, and either fix it or escalate to whoever can.
You get told what happened and what we did, including when the answer is that we are waiting on a third party.
Frequently, and it usually starts with an assessment rather than a plan — there is no point maintaining something before knowing what state it is in.
Occasionally that assessment concludes the site needs work before a plan makes sense, and we will say so rather than quietly billing around the problem.
Text edits, image swaps, price and hours updates, adding a team member, publishing a post, changing a PDF. Roughly, anything measured in minutes.
New page templates, new functionality or design changes are projects, and get quoted separately. We will tell you which category something falls into before doing it.
The report, and the fact that it includes the boring months. If a report has nothing to say beyond "updates applied", that is what it should say.
You also keep access to everything — the backups, the logs, the staging environment. Nothing about the arrangement depends on you not being able to check.
Give notice and we hand over credentials, documentation, backups and anything else that is yours. Month to month, no exit fee.
We would ask why, because it is usually useful to know, but the offboarding does not depend on the answer.
Patching, advisory tracking and access review are part of a plan. Deeper hardening — a full audit, firewall configuration, penetration testing, incident response planning — is separate work.
Most sites need the first continuously and the second occasionally.
Call back
Leave a number and a good time. We will call you back to talk about what you are trying to build — no charge for the conversation.
Or call us directly +1 (647) 385-5532