Near-zero marginal cost, priced accordingly
The floor: monitoring and patching, nothing more.
- Uptime, SSL and domain expiry monitoring
- Security updates of the server and its dependencies
- Backups
- Critical incidents handled in support hours
CARE PLANS · QUARTERLY
Two plans, quarterly, not monthly
Custom builds need less maintenance because there are no plugins to update and nothing breaks on someone else's release schedule. Quarterly billing matches how often there is actually something to do, not how often a subscription renews.
WHAT IT COSTS
Watch, or Assurance. Platforms by agreement.
Two plans, not a tier ladder. Watch is priced low on purpose — it is the proof that this is not rent.
Watch, plus a dated report and a standing fix
The artifact clients in the US and the EU are actually paying for.
- Everything in Watch
- Critical incidents, 24/7
- A dated quarterly report: speed, links and redirects, security headers, accessibility
- Anything that regressed since the last report, fixed at our cost
Hosting, domain and third-party software are billed at cost, no markup, on either plan. Platforms and marketplaces are priced by agreement — operational complexity varies too much for a flat quarterly figure. All maintained sites are monitored from the same Command Centre, regardless of plan or size.
THE PRINCIPLE
Is this rent?
We say stop renting your website. Our own recurring charge has to pass the same test.
Ask one question of any recurring charge, including ours: if you stop paying, does anything stop working, and do you lose anything? With a rented platform the site goes down and the work stays behind. With us the site keeps running on your server, under your domain, on code that is already yours. You stop buying the work, not the right to exist.
HOW THIS STAYS HONEST
What a plan assumes, and what breaks it
The conditions behind both plans, not buried in an agreement you see after signing.
ConditionsWATCH · ASSURANCE
- 01Every build we run is monitored in our Command Centre, and every deployment is recorded.
This is how a regression gets caught and attributed, not a claim without a record behind it.
- 02Changes made outside our process are not fixed free.
A change made without our written agreement and review, if something goes wrong with it, is not covered: we either restore the last version we signed off, or review the change at an hourly rate.
- 03Stopping a plan does not stop the site.
It keeps running on your server, under your domain, on code that is already yours. Monitoring stops, and any future fix becomes hourly work instead of something already covered.
WHY LESS TO MAINTAIN
No plugin ecosystem means no monthly patch cycle
The framing behind the price, not just the number itself.
A plugin-based site generates its own maintenance workload: version conflicts, abandoned plugins, a theme update that breaks a layout nobody touched. A custom build has none of that surface area, so the ongoing work is genuinely smaller, and the price reflects it rather than being discounted from a larger one.
STRAIGHT ANSWERS
Questions about care plans
The ones that come up once a project is close to launch.
Watch is the proof that this is not rent: uptime, SSL and domain expiry monitoring, security updates of the server and its dependencies, backups, and critical incidents handled in support hours, all for
No. Care keeps what already exists running: monitored, patched, and responded to quickly if something goes wrong. New features or content changes are scoped and quoted separately, the same way the original build was, rather than folded into a flat fee that quietly expands to cover anything asked of it.
That is allowed, since you own the code. What it changes is the plan: a change made outside our process, without our written agreement and review, is not fixed free if something goes wrong with it. We either restore the last version we signed off, or review the change at an hourly rate.
The site keeps running, on your server, on code that is already yours. Nothing goes down and nothing is taken away. Monitoring stops, and any future fix becomes hourly work instead of something already covered.
Because the operational complexity varies far more than it does for a website. A marketplace handling payments and multiple vendors carries a different risk profile from a brochure site, so it is priced by agreement rather than a flat quarterly figure, scoped the same way the build itself was.
Building something new? Care is scoped once the build is.
There is no need to decide on a care plan before a project starts. We revisit it at handover, once you know what you actually built.
Care plans sit alongside managed hosting and monitoring as the three parts of what keeps a site running after launch.