
Key takeaways
- A maintenance and support agreement defines what is kept working, how fast problems are handled and what is paid for separately.
- Core clauses: scope, severity levels with response and fix targets, support hours, exclusions, reporting, security updates and exit terms.
- Common pricing models are a monthly retainer, a bank of hours or pay as you go. Faster guaranteed response usually costs more.
- Agree ownership of code, hosting accounts and documentation, so you can change provider if you need to.
Why you need one
Software does not stay finished. Operating systems, browsers, libraries and third-party services change, new security issues appear and your own business evolves. Without an agreement, a problem after launch becomes a negotiation: who is responsible, how fast will they respond and what will it cost? A maintenance and support agreement answers those questions in advance, so a bad day is a routine day. It is also the practical meaning of a promise to stand behind our work after launch.
Clauses to include
- 1Scope: which applications, environments and integrations are covered, and what is not.
- 2Severity levels: define critical, high and normal issues in plain terms, such as the system being down, a major feature broken or a minor fault.
- 3Response and fix targets: how quickly each level is acknowledged and how quickly work starts. Targets are not the same as guaranteed fix times, so be clear which you mean.
- 4Support hours: business hours, extended hours or on-call cover for critical incidents, and how to report a problem.
- 5Preventive work: security updates, dependency upgrades, backups checks and monitoring.
- 6Changes and new features: how requests are quoted, approved and scheduled, separate from fixes.
- 7Reporting: a regular summary of issues, work done, hours used and risks.
- 8Ownership and access: who owns code, accounts and documentation, and who holds credentials.
- 9Exit: notice periods, handover support and what happens to data when the agreement ends.
Fix or change request?
| Kind of work | Examples | Usually |
|---|---|---|
| Bug fix | A feature no longer works as originally agreed | Covered by the agreement or warranty |
| Compatibility update | A new browser or operating system version breaks a screen | Covered, if listed in scope |
| Security patch | A library vulnerability needs updating | Covered, with agreed timing |
| Small improvement | A label, a report column or a minor layout change | Drawn from an hours bank or quoted |
| New feature | A new module or integration | Quoted and scheduled separately |
Pricing models
- Monthly retainer: a fixed fee for defined coverage and response targets. Predictable, and good for business-critical systems.
- Hours bank: you buy a block of hours to use for fixes and improvements. Flexible, but track usage and expiry.
- Pay as you go: you pay for time when you need help. Cheapest when problems are rare, but there may be no guaranteed response.
- Hybrid: a small retainer for monitoring and updates, plus an hours bank for changes.
Faster guaranteed response and wider hours cost more, because the supplier must keep people available. Match the level of cover to the real cost of downtime to your business. Our article on mobile app maintenance cost explains budgeting in more detail.
A worked example
A company with an ordering system chooses a monthly retainer that covers monitoring, security updates, bug fixes and a small hours bank. The agreement defines critical issues as the system being unavailable, with the fastest response target, and treats cosmetic requests as normal priority. When a payment provider changes a rule, the team updates the integration within the agreed window and notes it in the monthly report. This is an illustrative scenario, not a client story, but it shows the value of agreeing definitions before something breaks.
Questions to ask before you sign
- What exactly counts as a critical issue, and who decides?
- What are the response targets, and what happens if they are missed?
- Who monitors the system, and how will you know about a problem before I do?
- How do unused hours work: do they expire or roll over?
- Who holds hosting accounts and credentials?
- What help do I get if I want to move to another provider?
Next step
Decide where your system runs with cloud hosting for business apps, plan the build properly using the software project timeline guide, read our commitments on the trust and guarantees page, or contact us to discuss support for your system.
Frequently asked questions
What is the difference between a warranty and a maintenance agreement?
A warranty covers defects in delivered work for a period stated in the contract. A maintenance agreement continues after that, covering monitoring, updates, fixes and support, often with response targets.
What is a response time target?
It is how quickly the supplier acknowledges an issue and starts work, usually set by severity level. It is different from a guaranteed fix time, so ask which one is promised.
Can I change maintenance provider later?
Yes, if you own the code, hold your accounts and have documentation. Include exit and handover terms in the agreement so the transition is smooth.

