“Maintenance plan” gets used loosely across the industry, which makes it hard to compare what you’re actually getting. Here’s what’s inside a well-scoped plan, and what usually isn’t.
Proactive Monitoring
Automated checks on uptime, performance, and error rates that alert a real person before a customer notices something's wrong — the core of what separates proactive plans from reactive break-fix support.
Security Patches and Dependency Updates
Regularly scheduled updates to frameworks, plugins, and libraries, prioritized by severity so security issues get addressed fast and routine updates happen on a predictable cycle.
A Defined Response Time for Issues
A real plan specifies how quickly you'll hear back and how fast critical issues get addressed — vague promises of "fast support" without numbers aren't a real SLA.
A Monthly Hours Allowance for Small Changes
Most plans include a set number of hours for minor updates and small features, which is often the most-used part of the plan in practice.
What's Usually Not Included
Major feature builds, redesigns, and large integrations are typically scoped and quoted separately from a maintenance retainer — worth clarifying upfront so there's no surprise later.
Frequently Asked Questions
What happens to unused monthly hours?
This varies by provider — we roll a portion forward to the next month rather than losing them outright, up to a reasonable cap.
Can a plan scale up or down as needs change?
Yes — plans should be reviewed periodically and adjusted based on actual usage and how the system’s risk profile has changed.