In short
A simple managed website may need less than $100 per month in software and occasional support, while a professionally maintained custom site often costs $300–$2,000 monthly. Ecommerce, integrations, accounts, compliance, or active improvement can cost several thousand. Scope and response expectations matter more than the package name.
Planning ranges
Website maintenance can mean a $20 platform subscription or a team monitoring a revenue-critical application. These ranges are useful only when paired with scope:
| Website type | Typical monthly planning range | Common work |
|---|---|---|
| Simple hosted-builder site | $20–$150 | Platform, domain, small updates handled internally |
| Small CMS marketing site | $100–$500 | Hosting, backups, updates, monitoring, occasional fixes |
| Custom marketing or content site | $300–$2,000 | Managed infrastructure, dependency work, monitoring, support time |
| Ecommerce or integrated website | $1,000–$5,000+ | Transactions, integrations, releases, security and operational support |
| Web application | $2,000–$15,000+ | Product engineering, incidents, infrastructure, dependencies, ongoing changes |
These are planning ranges, not market rates for a defined service. Content, SEO, design improvements, new features, and around-the-clock support may be separate.
Separate five different costs
1. Infrastructure
Domain, DNS, hosting, CDN, database, storage, backups, email delivery, search, and monitoring. Some costs are fixed; others scale with traffic, storage, users, or transactions.
2. Software and licences
CMS plans, plugins, fonts, consent tools, analytics, security services, form platforms, and integration products. Record renewal dates and account ownership.
3. Preventive maintenance
Updates, dependency review, backup testing, access review, certificate checks, monitoring, performance regression checks, and removal of obsolete software.
4. Support and recovery
Diagnosing broken forms, failed deployments, expired integrations, editor problems, incidents, or unexpected browser behaviour. The response promise changes the price significantly.
5. Improvement
New content types, conversion work, SEO, accessibility improvements, design changes, integrations, and features. This is product development, not merely keeping the current system working.
A proposal that combines all five into “maintenance” is difficult to compare and easy to misunderstand.
What preventive maintenance should include
For a typical professionally managed website, agree on:
- uptime and error monitoring;
- automated backups and periodic restore tests;
- platform, plugin, and dependency updates;
- security advisories and access review;
- form and transaction checks;
- domain and certificate expiry ownership;
- analytics and consent verification;
- broken-link and redirect checks;
- performance regression monitoring;
- CMS support and documentation updates;
- a record of changes;
- a recovery and escalation path.
Not every check needs to run monthly. Frequency should follow consequence and rate of change.
What changes the cost
Technology and dependency surface
A hosted builder transfers platform maintenance to the vendor. A custom application gives more control while creating more code, infrastructure, and integrations to own.
Business consequence of downtime
A portfolio site and a booking platform require different monitoring and response. Faster guaranteed response needs capacity reserved before an incident occurs.
Change frequency
A stable marketing site may need occasional preventive work. A site with weekly releases, campaigns, catalogue changes, and experiments needs an ongoing delivery rhythm.
Integrations
CRM, payments, inventory, authentication, search, and marketing services change APIs, credentials, and limits. Each connection adds monitoring and failure states.
Security and governance
Accounts, personal data, payments, regulated content, multiple editors, or formal review requirements increase operational work.
Content and languages
Maintenance may include editorial help, translations, media optimisation, link review, or content expiry. Make those responsibilities explicit.
Retainer, time bank, or pay as needed?
Pay as needed
Fits a low-risk, stable site when response time can be flexible. The risk is finding qualified availability during an incident and losing context between requests.
Time bank
A set number of hours used for maintenance and small improvements. It provides access and budget control, but unused-time and rollover rules need clarity.
Retainer with service expectations
Fits important or frequently changing systems. The agreement can cover preventive tasks, monitoring, response windows, reporting, and reserved improvement capacity.
The best model follows the consequence of failure and expected change—not the agency's preferred billing structure.
Warranty is not maintenance
A warranty corrects defects in the agreed delivered work for a defined period. Maintenance keeps the system healthy as browsers, dependencies, services, content, and threats change. New functionality changes the agreed work.
Before launch, classify examples:
- a form never worked as accepted: warranty;
- an email provider changes its API six months later: maintenance;
- the business requests a second CRM route: improvement.
Clear categories prevent ordinary defect correction from consuming a maintenance allowance.
Questions to ask in a maintenance proposal
- Which systems and environments are included?
- What preventive tasks happen, and how often?
- What is monitored automatically?
- What counts as an incident?
- What response is promised by severity and time of day?
- Are fixes included or only diagnosis?
- How are third-party costs billed?
- What is excluded?
- Does unused time roll over?
- Who owns accounts, backups, code, and documentation?
- How can either side end and hand over the service?
Common questions
Does every website need monthly maintenance?
Every website needs ownership, but not every site needs monthly human work. Managed platforms handle much infrastructure; a stable small site may use monitoring and scheduled periodic review.
Is hosting included in website maintenance?
Sometimes. Ask for infrastructure, software licences, maintenance labour, support, and improvements as separate lines so recurring costs and responsibilities remain visible.
What is a reasonable maintenance budget?
Base it on the system and consequence of failure. A small CMS site may justify $100–$500 monthly; a custom or integrated site often needs $300–$2,000 or more, excluding active product development.
Can I maintain a website myself?
Yes, when the platform is managed and the team can own content, access, renewals, backups, and basic checks. Custom code and integrations usually require qualified technical support.
Does maintenance include SEO and content updates?
Only if the agreement says so. Technical upkeep may preserve crawlability and performance, while keyword research, content, internal-link work, and reporting are ongoing visibility services.
