Insights / Digital Foundation
Website maintenance: what needs care after launch?
Hosting, technical upkeep, content and improvement are four different jobs. Know which ones you’re paying for.
The new website is live. Everyone’s relieved. The project is done.
Except it isn’t. Launch is the starting line, not the finish.
From the day it goes live, a website starts to drift. Software needs updates. Staff come and go. Services and prices change. Buyers ask new questions. Nobody notices, because nothing is obviously broken, until something is.
“Maintenance” gets used for all of that, which is the problem. A business buying a maintenance plan often assumes everything is covered. A provider selling one often means something much narrower. Both can be acting in good faith and still be surprised.
The question isn’t whether your website needs maintenance. It’s which parts of its care you’re paying for, and who looks after the rest.
Four kinds of care
Keep it hosted and protected.
Hosting, backups, certificates, monitoring and threat blocking. Nobody can make a website completely secure. Good care reduces the risk and shortens the recovery when something goes wrong. Hyperweb hosting, for example, includes nightly backups, core updates, plugin management and threat blocking. Here’s how we look after the foundation.
Keep it working.
Technical maintenance means updating the platform and its add-ons, then checking that forms, booking tools, payments and CRM connections still work. The testing matters as much as the update. An update nobody checked is how a contact form stops sending for a month.
Keep it accurate.
Team, services, prices, hours, locations, policies, case studies. Your provider can make the changes, but only you know when they’re needed. Someone inside the business should own a regular review.
Keep it improving.
New pages, clearer answers, better proof, fixes where enquiries drop off, search and AI visibility. This is strategic work, not maintenance, and it deserves its own budget and plan.
Most disappointment with maintenance comes from expecting the fourth job from a plan built for the first two.
Compare support models by responsibility
Price is easy to compare. Responsibility is what matters. The three common models all work for the right business, as long as everyone knows who does what.
| Model | Suits | Watch for |
|---|---|---|
| Pay as you go | Simple sites with occasional changes | Nobody is watching between requests. Updates and testing may only happen when you ask. |
| Monthly retainer | Regular changes or more complex sites | What the hours cover, who sets priorities, and what happens to unused time. |
| Managed plan | Owners who want hosting and technical care handled | Exactly what’s included, what’s billed separately, and what recovery looks like. |
Whichever model you choose, ask the same questions:
- Who applies updates, how often, and are they tested first?
- Is there a staging copy for testing changes?
- Where are backups kept, and how quickly can you restore one?
- What happens if an update breaks a form or an integration?
- Who do we call when the site is down, and when will they answer?
- Whose name are the accounts in?
That last one matters more than it sounds. Here’s how to check who controls your accounts.
Give it an owner inside the business
Even with the best provider, some of this can’t be handed off. Someone at your business has to know when a service changes, when a team member leaves, when a price goes up, and when buyers keep asking the same question the site doesn’t answer.
Say you run a 20-person engineering firm. Your provider keeps the site hosted, updated and backed up. But two project managers left in the spring, a service line was renamed, and the careers page still lists a role you filled months ago. None of that is a technical fault, and none of it will be caught by a maintenance plan.
Pick one person. Give them a short review every quarter: team, services, contact details, forms, proof. Have them send changes to your provider in one list, not as they remember them. It’s a small job that keeps a big one from building up.
What’s usually outside scope
Good providers are clear about this up front. Typically outside a maintenance plan:
- New pages, features or a redesign
- Writing or rewriting content
- Search, AI visibility and marketing work
- Fixing problems inside third-party software
- Repairing changes made outside the agreed process
None of that is a reason to avoid a plan. It’s a reason to write down what the plan covers, including recovery: what your provider will do if the site goes down, and how fast. Get it in writing rather than assuming. When something does break, here’s what to check before changing anything.
A website isn’t finished at launch.
Know what’s covered.
Know who does the rest.
Write it down.