A website support package should make owning a website easier, not add another contract you have to decode. The right plan gives you a clear route for updates, faults and everyday improvements, so the website can keep helping customers instead of quietly drifting out of date between expensive redesigns.
That sounds obvious, but support packages often bundle very different jobs under the same friendly label. One may mean automated backups and a monthly update. Another may include time to change an offer, repair a broken enquiry route, review a weak page and help the business decide what needs attention next. Neither is automatically wrong. The mistake is assuming they are interchangeable because both arrive as a monthly fee.
The useful question is not “what is the cheapest support package?” It is “what would happen if this important part of the website became wrong, unavailable or confusing?” Start there, and the scope becomes much easier to judge.
What is a website support package?
A website support package is an ongoing agreement for help with the website after it has launched. It can cover routine checks, technical care, content changes, troubleshooting, advice and planned improvements. Good support makes the business less dependent on the person who originally built the site and gives the owner a sensible way to keep it useful.
It is broader than simply having somewhere to host the website. Hosting makes a site available online. Support is the work that helps keep the information accurate, the important journeys working and the next change from becoming a stressful technical project. For many small businesses, that means there is someone accountable when a form stops sending, a price changes, a service needs a clearer explanation or customers keep missing the same piece of information.
The right level depends on how much the business relies on the site. A simple brochure site that rarely changes may need light-touch help. A site that earns regular enquiries, carries bookings, supports paid campaigns or has changing services needs a more active support relationship. The bigger the cost of a wrong page or a broken customer route, the less sense it makes to leave support vague.
What should a good package include?
There is no universal shopping list, but a credible package explains the foundations and the human help separately. The foundations are the checks that keep the site dependable: backups, sensible updates, monitoring and a recovery route. The support layer is how you ask for a change, what happens when something goes wrong, and whether the provider has time to improve the parts customers actually use.
The National Cyber Security Centre advises small organisations to identify the information they need to back up, keep backups separate and make them part of ordinary business practice. Its guidance on backing up business data is useful because a backup is only reassuring when it is recent, accessible and part of a real recovery plan. The same principle applies to a website: do not just ask whether backups exist; ask what happens if you actually need one.
| Part of the package | What good looks like | Question to ask |
|---|---|---|
| Routine care | Clear checks for updates, backups, security and the main website functions. | What is checked each month, and how do you know it worked? |
| Everyday changes | A plain description of the small edits included, such as changing a service, photo, price or opening hour. | What counts as a normal update, and what becomes a separate project? |
| Fault support | A clear way to report a problem and a sensible response for issues affecting customers. | What happens if a form, booking route or key page stops working? |
| Improvement work | Time to fix recurring friction, clarify weak content or prioritise the next useful change. | Does the plan only keep the site online, or can it make the site work harder? |
| Ownership | The business knows who controls its domain, hosting, website access and key accounts. | Can the business access the essentials if it changes provider? |
Maintenance and support solve different problems
Maintenance protects the health of the website. Support helps the business use it. The two overlap, and a sensible plan may cover both, but it helps to know which job you are buying. A backup, software update and security check can be essential, yet they will not correct an out-of-date service list, explain a new offer or fix a customer journey that is losing enquiries.
Think of maintenance as the safety net and support as the practical help that keeps the site aligned with the business. If the site is broadly right but needs protecting, a maintenance plan may be enough. If the business changes regularly or the website is an important sales tool, support should include a simple route for making those changes properly. Our guide to website maintenance costs in the UK explains the care side in more detail.
Decide what your business cannot afford to lose
The package should match the website's role in the business. Start with the actions that matter most: quote forms, phone links, online bookings, orders, customer logins, location details, price information or campaign landing pages. If one of those breaks, how quickly does it become a commercial problem? That is a more useful guide than the number of pages on the site.
A local trades business may need its call buttons, service areas and quote route checked more than it needs a monthly design brainstorm. A restaurant may need menu changes, bookings and opening hours kept accurate. An online shop may need much closer attention to checkout, stock, delivery and payment routes. A consultant may value help keeping offers, case studies and enquiry pages clear as the business grows.
This is why broad promises such as “unlimited support” should make you ask more questions, not fewer. Unlimited can mean the provider will accept any request, but it does not explain when work will happen, who will do it, how it is prioritised or where a larger project starts. A defined, well-explained allowance is often more useful than a grand promise with no visible boundary.
Ask how updates are made safely
Routine updates are sensible, but a good provider does not treat every update as harmless. Changes to the platform, plugins, forms or integrations can affect the customer-facing website. The National Cyber Security Centre notes that keeping software up to date helps prevent known vulnerabilities from being exploited. Its guidance on keeping software up to date is a helpful reminder that patching is part of basic protection, not an optional extra.
Ask for the practical sequence. Is there a backup before a significant update? Are the important journeys checked afterwards? Is there a recovery route if something unexpected changes? You do not need a lecture on the technology. You need confidence that an update is followed by a check of the things customers use: enquiry forms, booking routes, checkout pages, phone links and the key information that helps someone decide.
This also separates a maintenance task from real support. A provider who can say “the update is complete” has done one part of the job. A provider who checks the page, explains the result and fixes the customer impact has done the useful part.
Make small changes genuinely small
Businesses change constantly. A new service appears, a team member leaves, a seasonal offer ends, an address changes, a customer asks the same question for the tenth time, or a page needs better proof. These are ordinary changes, but they often become expensive or delayed when the support plan only covers technical upkeep.
Before you sign, describe a few changes you expect to make this year. For example: “We will need to update prices twice, add a testimonial each quarter, change a service page and replace some photos.” Ask whether those are included and how you request them. The answer tells you far more than a generic line saying “content support available”.
The same applies to improvements. Support is more valuable when it can respond to a real customer problem: a weak page, a confusing call to action, an enquiry route that does not work cleanly on mobile or a service that has no focused page. Those changes help protect the money already spent attracting visitors. They are not decorative extras.
How to compare two packages fairly
Put the quotes side by side and compare the work in plain language. Start with the guaranteed basics: backups, updates, checks, monitoring and a recovery process. Then compare the human side: included support time, ordinary content updates, expected response when a customer-facing fault appears and whether the provider will help improve a page rather than only restore it.
Next, check the exclusions. It is reasonable for a package to exclude a major redesign, a new booking system, professional photography, paid software or substantial new content. The important part is finding that out before the work begins. A good quote does not pretend a large project is a small edit. It makes the boundary clear and tells you how larger work will be scoped.
Finally, look for evidence that the provider can explain what they do. That may be a short monthly update, a list of completed work, a conversation about priorities or a clear record of support requests. You do not need a colourful dashboard for its own sake. You need to know whether the website is being cared for and what has improved.
Red flags to avoid
Be cautious of a package that offers complete peace of mind but cannot name its routine checks, support limits or process for a serious problem. A reassuring label is not a service level. The same is true of a plan that offers unlimited edits but will not explain what counts as an edit or how long ordinary requests take.
Another warning sign is unclear ownership. Your provider can manage the accounts, but your business should know where the domain, website access, hosting account and important customer-facing tools live. That does not mean you must run them yourself. It means you should not be locked out of the things your business depends on.
Also watch for support that treats every request as an interruption. The point of a package is to make routine website work straightforward. If you are reluctant to correct a wrong phone number, update a service or report a broken enquiry route because it feels like starting a new project, the support model is not doing its job.
Use this website support checklist
- List the customer actions your website cannot afford to lose, such as calls, enquiries, bookings or checkout.
- Ask which routine checks, updates and backups happen and how the provider confirms they worked.
- Define everyday edits in plain language before agreeing a monthly allowance.
- Check how an urgent fault is reported, acknowledged and dealt with.
- Confirm who owns the domain, hosting, website access and key business accounts.
- Separate routine support from bigger redesigns, new features and paid third-party tools.
How 118 118 Sites helps
118 118 Sites is designed for owners who want the website work handled in plain English. The support is not limited to keeping a site online. It includes the practical changes, fixes and ongoing improvements that help the site stay accurate, easy to trust and ready for the next customer.
See the detail on our website support services and website maintenance services pages, then compare the full plan on Pricing. If you are unsure what needs attention first, start with the free site audit and use the results to decide whether the priority is care, support or a bigger website change.
Frequently asked questions
What should a website support package include?
A useful package should make the routine work clear: how you ask for help, what counts as a small update, how faults are handled, whether backups and updates are checked, and what happens when the work falls outside the monthly plan. The right detail depends on the site, but the boundaries should never be a mystery.
Is website support the same as website maintenance?
Not quite. Maintenance is usually about keeping the site secure, available and technically healthy. Support is the human help around the site: updating pages, fixing customer-facing issues, answering practical questions and making agreed improvements. Some plans combine both, but it is worth checking which parts are actually included.
Do small businesses need website support?
A small business needs support when its website matters to enquiries, bookings, sales or trust and nobody in the business has the time or confidence to keep it accurate. A simple site may only need occasional help, while a business that changes offers, runs campaigns or relies on online enquiries may need a more responsive plan.
How do I compare website support packages?
Compare the work rather than the package name. Put each offer against the same questions: what routine checks happen, what changes are included, how urgent problems are treated, who owns the accounts, what evidence of work you receive, and what will cost extra. That shows whether two similar prices are actually buying the same level of help.
