Services · Support and care
Support that keeps it working and improving.
Launch is the start, not the finish. We host, maintain and keep improving what we build, so it stays fast, secure and useful as the business changes.
What's included
Looked after, not left alone.
A care plan covers the things that keep a site or system healthy, and the steady improvements that keep it earning its place.
Managed hosting
Sites we build run as static files on Cloudflare's edge network, served from whichever data centre is nearest the visitor. There is no origin server to fall over under load and nothing to patch at 2am.
Security & updates
Dependencies in the serverless functions are kept current, API keys rotated, and security headers reviewed. No plugin stack means the usual attack surface is not there to begin with.
Backups & monitoring
The site itself lives in version control, so every deploy is recoverable by design. Where there is a database behind a portal or a CRM, that gets backed up separately and checked.
Ongoing improvements
An allowance of development time each month for the things that come up: a new service page, a form that needs another field, a report nobody thought of at launch.
Priority support
You message the person who wrote the code, not a ticket queue. No re-explaining the build to whoever picks it up, because it is the same person every time.
Reporting
What changed, what it cost in hours, and what the site did that month. You should never have to ask what a retainer is actually buying you.
The honest version
Most of the maintenance list does not apply.
Traditional website care is largely a treadmill the platform creates for itself. A WordPress site needs its core, theme, plugins and PHP version updating, because any one of them going stale is a way in. Most of what a maintenance plan bills for is stopping that stack falling over.
By default we do not build on that stack. The public site is static HTML served from the edge, with no CMS, no plugin directory, no database and no server behind it. There is nothing to log into and nothing to exploit. We have written about why that removes most of the attack surface and how the two approaches compare.
So a plan with us is not insurance against your own website. It is time to keep improving it, plus the handful of things that genuinely do need watching:
- The serverless functions. Forms, chat, payment webhooks and any custom API each carry dependencies, and those move. They get updated and tested before anything ships.
- Keys and secrets. Email, payments and AI services all authenticate with keys. They get rotated, and access gets reviewed when someone leaves.
- Third parties. Payment providers and email services deprecate APIs on their schedule, not yours. Someone needs to be reading those notices.
- Your data. Enquiries, client records and invoices in a portal are the part that cannot be rebuilt from a git repository. That is what backups are actually for.
- The content. A page that was accurate at launch quietly stops being accurate. Prices change, services change, people leave.
Why it matters
Software needs looking after.
- Sites decay in ways nobody notices until a customer does. An image creeps in oversized, a form silently stops sending, a third-party script starts costing half a second. Speed is a feature, and it is one you lose gradually rather than all at once.
- The launch build is a hypothesis. What actually converts only becomes clear once real enquiries start arriving, and acting on that is where the return sits. A site that never changes after launch never gets better.
- One point of contact who already knows the build. No agency handover, no account manager relaying your request to a developer, no starting again because whoever built it has moved on.
Inherited builds
We will take on a site we did not build.
Most enquiries here are from businesses whose developer has gone quiet, or whose agency retainer stopped feeling like value. We can pick those up, but not blind.
We look first
A short review of what is actually running: the platform, the plugins, the hosting, where the domain and DNS sit, and who currently holds the keys. You get the findings whether or not you go ahead.
You get the truth about it
Sometimes the answer is that the site is fine and needs light touch care. Sometimes it is that you are paying to maintain something that should be replaced. We will say which, and it costs nothing to hear it.
Access on your side
Domain, hosting and analytics stay in accounts you own. If we ever part company you keep everything, with nothing to prise out of an agency. It is the same principle as owning your platform.
Scope
What a plan does not cover.
Worth being straight about, because vague retainers are how clients end up feeling short changed.
- A full redesign. Improvements are incremental. Rebuilding the site is a project, quoted separately, not something to smuggle through a monthly allowance.
- Unused time rolling up forever. Hours are there to be used. We will tell you when you are not using them rather than quietly banking the money.
- Third-party subscriptions. Your domain, and any paid services the site depends on, stay in your name and on your card. We manage them, we do not resell them.
- Writing all your content. We will write and edit as part of the allowance, but nobody knows your business like you do. The best pages come out of a conversation, not a brief.
Questions
Good to know.
What does a care plan include?
Managed hosting, security and updates, backups and monitoring, plus an allowance of ongoing improvements each month.
Do I have to be a build client to get support?
No. We can take on care for an existing site, after a short review to understand what we are looking after.
How quickly do you respond?
Care plans come with agreed response times, and you deal directly with the person who knows the build.
Is hosting included, or billed separately?
Included. Our stack runs on infrastructure that costs very little to serve, so hosting is not where we make our money and we do not mark it up as a line item. The value is in the maintenance and the improvements.
What if I want to leave?
You take everything. The domain, the DNS, the hosting account and the code are all in your name already, so there is nothing to hand over and no notice period holding your site hostage.
Can you support a WordPress site?
Yes, though we will be honest about it. We will keep it updated and secure, but a plugin-heavy site costs more to maintain and stays slower than a rebuild would be. If the maintenance bill is approaching what a new build costs, we will tell you.
What happens if something breaks out of hours?
For sites we build, the public site is static files at the edge, so the usual out-of-hours emergency, a server going down, does not really happen. Where something does fail it tends to be a form or an integration, and every deploy can be rolled back to the previous version in moments.
Want your site properly looked after?
Tell us what you are running and we will recommend the right level of care.