A lot of attention goes into getting a new website or system built. Rather less goes into what happens once it’s live. That’s understandable: the launch feels like the finish line. In practice, it’s where the real use begins, and where most of the questions and small problems turn up. Good website support is what gets you through that stage.
Support arrangements vary a lot between suppliers, and “support” can mean anything from a fully managed service to “email us if it breaks”. Neither is wrong, but you need to know which one you’re getting.
Here’s what good website support should cover and how to compare what’s on offer.
The launch period
The first few weeks after going live are when you’ll discover the things testing didn’t catch. A good supplier expects this and builds it in.
- A defined snagging period. A window after launch where genuine bugs are fixed at no extra cost. Ask how long it is and what counts as a bug.
- Quick response for serious issues. If something important stops working in the first week, you want someone on it fast.
- Training and handover. Your team should know how to do the everyday tasks themselves, with written guidance they can refer back to.
Ongoing technical care
Websites and systems need regular maintenance to stay secure and working. This is the part that’s easy to forget until something goes wrong.
- Software, plugin and security updates, applied and checked
- Regular backups, stored separately, with occasional test restores
- Monitoring, so someone knows if the site goes down before your customers tell you
- Renewals for domains, security certificates and licences
- Keeping integrations working when connected tools change
Software doesn’t stay still after launch. The platform changes, browsers change and the tools around it change. Support is what keeps it working through all of that.
Help with changes and improvements
Separate from fixing problems, you’ll want things changed: new pages, a tweak to a form, a new report, an extra step in a process. Clarify how this is handled.
- Is there an allowance? Some plans include a set amount of time each month for small changes.
- How is extra work charged? Hourly, per task, or quoted separately?
- What’s the turnaround? Small changes shouldn’t take weeks.
It’s worth understanding the difference between a fix (something built doesn’t work as agreed) and a change (you’d like it to work differently). Disagreements about which is which are one of the most common causes of friction, so it helps to agree definitions up front.
Questions to ask before you sign
- What exactly is included in the monthly fee, and what isn’t?
- How do we report a problem, and who responds?
- How quickly will you respond, and how quickly will you fix things, for urgent versus minor issues?
- What hours is support available? What happens at weekends?
- How are updates tested so they don’t break anything?
- Where are backups stored and how often are they taken?
- What happens if we want to end the arrangement? What do we get handed over?
Response time and fix time are different things. A promise to respond within an hour means someone acknowledges the problem, not that it’s solved within the hour. Both are worth knowing.
How much website support do you actually need?
This depends on how much the system matters day to day. A brochure website that rarely changes needs far less than an online shop or a system your staff use all day.
A useful way to think about it: if this stopped working on a Friday afternoon, how much would it cost you by Monday? If the answer is “not much”, light support is fine. If it’s “a lot”, pay for proper cover.
Be wary of the opposite extreme too. Going without any support to save a monthly fee often works fine for a while, until an update fails, a certificate expires or a form quietly stops sending enquiries. At that point you’re paying emergency rates to someone who’s never seen the system before, which is rarely the cheaper option.
What you should do on your side
Website support works best as a partnership. On your side:
- Nominate one person as the main contact.
- Report problems with specifics: what you did, what happened, on which device, with a screenshot.
- Keep a simple list of requested changes so priorities are clear.
- Review the arrangement once a year to check it still fits.
Our approach
For websites, our website maintenance and support plans cover updates, backups and changes. For software, apps and business systems, system and app support covers the ongoing care that keeps them running well.
