Compare website maintenance plans by included work, response coverage, restore testing and ownership. Separate onboarding from the monthly budget.
Inventory & baseline
Maintain & monitor
Report & improve
A maintenance price is meaningful only when you know what happens when something fails. Hosting, scheduled updates, content changes and incident response are different responsibilities. Start with an inventory of the application, infrastructure and vendors, then define the monthly service boundary. A small brochure site and a revenue-generating application need different support models even when they use the same framework.
Start with the scope, not a headline price
| Option | What you are paying for | What changes the estimate |
|---|---|---|
| Preventive maintenance | Scheduled dependency review, updates and routine application checks. | The number of applications, release process and regression coverage determine the effort. |
| Maintenance plus changes | Preventive work with an agreed allowance for small improvements. | Clarify task size, prioritisation, approval and whether unused time carries forward. |
| Operational support | Monitoring, incident triage and agreed communication and escalation. | Coverage hours and response expectations differ from a promise to resolve every issue immediately. |
Costs to include before you compare quotes
- Onboarding may require fixing deployment access, unsupported dependencies or missing backups. Price this separately from recurring maintenance.
- A successful backup job does not prove recovery. Agree restore checks, acceptable data loss and the people allowed to approve recovery.
- Cloud, domain, email and monitoring subscriptions may be paid directly to vendors. List them so the monthly service fee is not mistaken for the total operating cost.
Where to simplify — and where to keep the work
Reduce an open-ended feature allowance before removing visibility or recovery work. A bounded queue with clear priorities is easier to manage than unlimited requests. For a business that can tolerate next-business-day response, do not buy around-the-clock coverage by default; for a critical system, do not assume a low-cost update plan includes it.
Turn the scope into a budget
Ask for hours by work package: discovery, design, implementation, testing and release. Multiply each package by its agreed rate, then add external services and an explicit allowance for unresolved risks. Compare quotes against the same acceptance criteria, currency and tax treatment. Calendar weeks are not person-weeks: two engineers working together change the effort and coordination cost. For ongoing work, choose a monthly period. Keep one-off setup separate from recurring fees, and ask who approves changes before additional work starts.
A brief that gets you a useful estimate
- Provide repositories, hosting ownership, supported environments and known incidents.
- Define coverage timezone, response targets, escalation contacts and excluded work.
- Agree a monthly report: changes shipped, incidents, restore checks and remaining risks.
Check your own budget assumptions
Labour budget
Hours × rate × (1 + contingency / 100)
Planning arithmetic using your inputs, not a quote or a market price. Excludes tax, hosting, licences and other third-party costs. Use one currency throughout; changing it does not convert amounts.
Frequently asked questions
Does a maintenance retainer include redesigns and new features?
Only if the scope says so. Separate recurring preventive tasks from a development allowance and from separately quoted projects. Define how requests are estimated and approved; otherwise an apparently simple monthly price hides an unbounded backlog.
What is the difference between response and resolution time?
Response is acknowledgement and initial action; resolution is restoration or a fix. Define severity, coverage hours and escalation rather than assuming both share a deadline.
Should a maintenance plan include restore testing?
Specify it explicitly, including frequency, environment and evidence. A successful backup job alone does not establish that the application can be recovered.
Why can onboarding cost extra?
Access recovery, dependency updates, monitoring gaps and undocumented infrastructure may need initial work before routine maintenance is predictable.
What happens to unused monthly hours?
The agreement should state whether they expire, roll over or fund preventive work. Also define approval and pricing for work beyond the allowance.
Bring the scope. We will help make it buildable.
Share the user journey, integrations and launch constraints. We can clarify the scope and prepare an estimate with assumptions and exclusions.
Further reading
Website development cost: how to compare scope and quotes
Plan website development costs around templates, content, integrations and launch checks. Compare quotes and calculate your own labour budget.
SaaS development cost: budget beyond the dashboard
Plan SaaS development costs around tenancy, permissions, billing and operations. Compare launch scopes and identify recurring cost drivers.