Keeping the site current, a stated content and development scope, and an unambiguous answer to who owns the hosting, the domain and the accounts.
Maintenance and improvement work are separate, and both are quoted.
Website support usually bundles two unrelated commitments. One is keeping the thing safe and working. The other is having someone available to change it. They cost different amounts and they fail in different ways.
Maintenance is the unglamorous half: dependency and platform updates, certificate and domain renewals, uptime and form monitoring, broken links, and the checks that catch a silent failure before a customer does. It is largely predictable and it is the part that protects the asset.
Improvement is the other half: an agreed content and development scope each month, applied to a queue you prioritise. It is what stops a site going stale, and it is the part businesses most often skip and then regret in the second year.
A plan states both. What we will not do is describe a maintenance-only plan in language that implies development time is included, because that ambiguity is the source of nearly every unhappy support relationship.
Three categories, with the line drawn before it matters.
| Category | What it covers | Where it stops |
|---|---|---|
| Maintenance | Dependency and platform updates, monitoring, certificates, backups, broken links and form checks | Anything that changes what the site says or does |
| Content scope | Page and copy updates, new pages on existing templates, images and metadata | A new template, a new content type or a new integration |
| Development scope | Component changes, new sections, performance work, analytics and small features | A redesign, a restructure or a platform move |
| Project work | Quoted separately with its own scope and acceptance criteria | It is never drawn from the monthly scope without agreeing it first |
Where a request sits near a boundary, it is scoped before it starts, so taking it into the month or quoting it as a project stays your decision.
The half of the plan that is invisible until it is missing.
A share of every month goes on work nobody requests, because the failures it prevents are more expensive than the time it takes.
Form monitoring earns its place more often than anything else on this list. A marketing site whose form has quietly failed looks perfectly healthy from the outside.
The question that only becomes urgent when a relationship ends.
Hosting, domain, CMS, analytics and any third-party service are registered to you with your billing. We hold access rather than ownership, so leaving is an access change rather than a negotiation.
Source lives in a repository you control, with the deployment configuration in it. Nothing that matters is on a machine only we can reach.
How to publish, where things are configured and what depends on what. Not written once at handover and left to age, because that is the version nobody trusts.
Plans are month to month after any initial term. A support arrangement that requires a long exit is a commercial device rather than a service commitment.
Support should be worth renewing, not difficult to leave.
Published starting figures in GBP and USD, excluding VAT.
Quoted separately from any build
Per month
From £399From $525
Monitoring, routine technical care and platform updates, plus small edits to text and images already on the site. New pages and substantial feature development are quoted as project work.
Starting price
Per month
From £1,250From $1,650
A live improvement programme on one site. You set the priorities each month, we work the queue in order, and the month closes with what changed and what it did.
Starting price
Per month
From £3,000From $4,000
Continuous delivery across an agreed portfolio, with planning ahead of the work rather than a queue you have to keep feeding.
Starting price
Hosting, CMS licences, domains and third-party services are yours and are billed to you directly. They are not marked up and resold through a support plan.
Yes, after a review of the stack, the hosting and the dependencies. That review is worth doing properly, because taking on an unfamiliar site without one means the first month is spent discovering it at your expense.
No, and deliberately. Hosting is billed to you directly, on your account, at cost. Reselling hosting inside a support plan creates a dependency that is only ever convenient for the supplier.
The terms state it explicitly before you commit, including whether any part carries over. We will not imply that unused time accumulates indefinitely, because a plan priced honestly cannot work that way.
Yes. Some sites genuinely only need keeping current and monitored. That is a smaller plan and it is priced as one, rather than sold as something larger with the development time quietly rationed.
Where the hosting, the domain and the repository actually live is usually the most revealing question.
