The site launched, everyone celebrated, the project was closed. Six months later the contact form has quietly stopped sending emails, the certificate has expired, and a plugin nobody updated has become a way in for attackers. Nobody noticed, because nobody was watching. Website maintenance exists to catch these things before customers and search engines do.
Here is what website support includes, how it differs from ongoing development, which pricing models exist, what to put in the contract, how to hand a project over to a new provider, and what drives the cost.
What website maintenance includes
The scope depends on the site: a landing page on a site builder and an online store syncing with an ERP need very different attention. But the core of a website maintenance plan is almost always the same.
- Platform and library updates. The CMS, framework, modules, dependencies, the language version on the server. Updates close vulnerabilities and keep things compatible. Put them off for years, and a single update turns into a small project with code rewrites.
- Security. The SSL certificate, access rights, former employees' passwords, admin panel protection, malware scans, and filtering bots and spam in forms.
- Backups. Regular backups of files and the database, stored separately from the main server, and, most importantly, a check that you can actually restore from them.
- Uptime and speed monitoring. A service pings the site every few minutes and alerts you if it's down, slow or throwing errors. Key pages and forms are worth monitoring separately, not just the homepage.
- Bug fixes. The layout broke in a new browser, the CRM sync stopped working, payments fail after the payment module was updated.
- Content. Publishing news, swapping banners, updating prices and documents, if the client's team doesn't have the time or a convenient admin panel.
- Small enhancements. A new form field, another catalog filter, a block on a service page.
- Analytics. Checking that Google Analytics conversions are being counted, events didn't get lost after changes, and reports reflect reality.
Website support vs. ongoing development
Support answers the question "how do we keep what works working?" Development answers "what should we add so the site delivers more?" The first is hygiene: updates, backups, monitoring, bugs. The second is product work: new sections, a customer portal, integrations, conversion improvements, reworked user flows based on analytics.
Mixing them up is risky either way. If the whole budget goes to enhancements, updates pile up, and one day the site breaks at the worst possible moment. If you only pay for support, the site stays stable but stops meeting business needs and goes stale.
Support keeps the site working; development makes it more useful. Both need a budget.
In practice, it helps to separate routine support from enhancements: a fixed monthly scope for support, and individual tasks with an estimate, priority and deadline for development. That way you know what you're paying for, and essential work doesn't get crowded out by new wish-list items.
Pricing models: hourly, retainer, dedicated team
Providers usually offer three models. None is better on its own: the choice depends on how often tasks come up and how much the site matters to revenue.
| Hourly | Retainer with a block of hours | Dedicated team | |
|---|---|---|---|
| How you pay | For hours actually spent | A fixed monthly fee for a block of hours | For the time of specialists assigned to the project |
| Response time | Not guaranteed | Set in the contract | Fastest, the team is already in context |
| Routine work | Only on request | Included in the retainer | Included |
| Best for | Simple sites with occasional tasks | Most business websites | Large stores and services in constant development |
Hourly billing
The simplest option: a task, an estimate, the work, an invoice. It fits when the site is small and changes are needed once every few months. The downside is that the provider isn't obliged to respond quickly, and between tasks nobody keeps an eye on updates and security.
Website maintenance retainer
A website maintenance retainer covers routine work (updates, backups, monitoring) plus a block of hours for small tasks. The contract sets the response time. Agree on what happens to unused hours (do they expire or roll over?) and at what rate overage is billed.
Dedicated team
Developers, a designer, a QA engineer or a project manager are assigned to the project part-time or full-time. At this point it's less support and more continuous product development. It's justified when the site is the main sales channel or is itself the product, and the task list never runs out.
SLA and response time: what to put in the contract
An SLA, or service level agreement, defines how quickly the provider starts working on a problem and what counts as a problem. Without one, "the site is down" and "please swap this image" end up in the same queue.
Bugs are usually split by priority. Critical: the site is down, orders or payments aren't going through. High: an important feature is broken, but there's a workaround. Normal: everything else. Each priority gets a response time and a resolution time, plus defined support hours: nights and weekends coverage is priced separately.
- Scope of routine work: what gets done every month without a separate request.
- Bug priorities with examples, and the response time for each.
- Support hours and how to reach the team outside them.
- The channel for requests (task tracker, email, chat) and who on the client side may submit them.
- The block of hours, what happens to unused hours, and the overage rate.
- How enhancements are approved: an estimate before work starts, not an invoice after.
- Backups: how often, where they're stored, for how many days, and who tests restoration.
- Reporting: what was done in the month and how many hours were used.
- Ownership of the code and the obligation to hand over access and the repository if the contract ends.
How to hand a website over to a new provider
Companies switch providers for all sorts of reasons: a freelancer left, an agency stopped responding, the workload grew. The handover goes smoothly if you prepare in advance, ideally from day one, by keeping all the access in your own hands.
- Collect the credentials. Domain registrar, DNS, hosting or cloud, server, the site's admin panel, database, email, Google Analytics and Search Console, payment provider, CRM and integrations. The domain and hosting must be registered to the company, not the provider.
- Get the repository. All the code with its change history in a version control system where the company has owner rights. An archive of files from the server is worse: it has no history and often hides what was edited by hand.
- Request documentation. How the site is built, how to deploy it, which external services are connected, where keys and settings are stored, how the ERP and CRM syncs work, and what scheduled jobs run on the server.
- Make a full backup. Files, database, configuration. Before any changes, with a restore test.
- Run an audit. The new provider reviews the code, versions, security and performance and lists the risks. It's an honest starting point that shows what you've inherited.
- Change passwords and keys. After the handover, the previous provider shouldn't retain access to the site or services.
When you need a redesign or rebuild, not support
Sometimes website support turns into endless patching. Here are the signs it no longer makes sense to keep investing in support:
- the platform or framework no longer gets updates, and every server update breaks something;
- a simple enhancement takes days because the code is tangled and any change ripples into other parts;
- the site is awkward on a phone and slow to load, and it can't be fixed piecemeal;
- the structure no longer reflects current services and products, and new sections are bolted on;
- the business has grown and needs a customer portal, integrations or a catalog, and the current architecture can't handle them.
If several of these apply, it's more honest to estimate a year of support costs and compare them with a new site. Patching often turns out to be more expensive.
How much website maintenance costs
Website maintenance prices vary not because providers are greedy, but because the same label covers very different amounts of work. The price depends on:
- Site complexity. A landing page, a corporate site, an online store and a web service with customer portals all need different levels of attention.
- Platform and code quality. Clean custom code with documentation is cheaper to maintain than an outdated CMS with dozens of plugins and someone else's patches.
- Integrations. Every connection to an ERP, CRM, payment or shipping provider is one more point that can break and needs watching.
- Response requirements. Response within a business day and 24/7 on-call coverage are services at very different prices.
- Volume of enhancements. How many hours a month go to new tasks on top of routine work.
- Infrastructure. Who is responsible for the server, monitoring, backups and their storage.
To compare proposals, ask for a breakdown of the monthly work, the number of hours in the block, the response time by priority and the rate for hours beyond the block. A single "support costs X a month" figure without a scope tells you nothing.
At Sphere, launch and growth is a dedicated stage of every project: after release we monitor the site, keep it updated and improve it based on analytics. See examples in our work.
FAQ
What does website maintenance include?
Typically platform and library updates, security and SSL, backups, uptime and speed monitoring, bug fixes, help with content, small enhancements and analytics checks. The exact scope is set in the contract.
How is website support different from ongoing development?
Support keeps what already works running: updates, backups, monitoring, bug fixes. Development adds something new: sections, features, integrations, conversion improvements. It's convenient to plan and pay for them separately.
Which pricing model should we choose?
Hourly billing suits small sites with occasional tasks. A retainer with a block of hours suits most business websites because it includes routine work and guaranteed response times. A dedicated team is needed when the site or service is under constant development.
Can we switch website support providers?
Yes. Collect all the credentials, get the repository with its history, documentation and a full backup, have the new provider run an audit, and change the passwords. It's easiest when the domain, hosting and repository are registered to the company from the start.
Do we need support if the website is running fine?
Yes. Without updates, vulnerabilities and incompatibilities pile up, and without monitoring and backups any failure is discovered late and costs more to fix. Regular support is cheaper than emergency recovery.




