Software Maintenance and Support: Choosing the Right Model

Warranty, AMC, retained hours or managed service? The right choice depends on what happens after your build team leaves.
The riskiest point in a custom software project may not be launch day. It can be month seven.
The warranty has ended. The delivery team has moved to another project. Nothing appears broken yet, but nobody clearly owns the system.
That is when alerts can go unread, credentials expire, backups remain untested and documentation slowly falls behind the code. Pasted text
Software Maintenance Is More Than Bug Fixing
Software maintenance services keep a working system working.
The source article separates ongoing work into several categories, including corrective maintenance for discovered problems, adaptive maintenance for changes in the surrounding environment, and work that improves or extends the system. Pasted text
For a practical support contract, four areas should be clearly separated:
Warranty — defects against the agreed scope during a fixed post-launch period.
Corrective maintenance — faults discovered after warranty.
Adaptive maintenance — updates required because browsers, operating systems, SDKs, payment gateways, certificates or dependencies change.
New features — functionality that was not part of the original handover.
Putting everything under one vague “support” budget is where disagreements begin. Pasted text
Warranty vs AMC vs Retained Hours vs Managed Service
There is no single support model that fits every application.
Warranty only can work for simple, stable internal systems where downtime has limited business impact.
AMC suits established business systems that need predictable corrective and adaptive maintenance.
Retained hours work well when the application is still evolving and you want a committed block of engineering capacity.
Managed service with SLA is designed for systems where downtime can interrupt critical business processes and monitoring, incident response and defined restoration targets matter. Pasted text
The simplest question is:
How much downtime can your business tolerate?
If four hours offline is inconvenient, an AMC may be sufficient.
If four hours stops invoicing, operations or field teams, you probably need contractual service levels rather than AMC-level expectations.
What a Useful SLA Looks Like
An SLA should be understandable by the person experiencing the business problem—not only by an engineer.
A practical structure might look like this:
S1 Critical: Core system or process completely unavailable.
First response: 30 minutes, 24×7
Restore/workaround: 4 hours
S2 High: Core process degraded or a department/site blocked.
First response: 2 hours within cover hours
Restore/workaround: 1 working day
S3 Medium: Secondary function unavailable but work can continue.
First response: 1 working day
Restore/workaround: 5 working days
S4 Low: Cosmetic issues, usability problems or minor requests.
First response: 3 working days
Resolution: next scheduled release Pasted text
And remember: response time is not resolution time.
A vendor acknowledging your S1 ticket quickly does not mean the service has been restored. Both targets should appear in the agreement. Pasted text
Knowledge Continuity Matters
Support quality often comes down to one question:
Who still understands the system six months after launch?
Good continuity requires current architecture documentation, integration details, environment information, scheduled-job documentation and practical incident runbooks.
There should also be a named engineer who knows the codebase and a backup who has actually worked with the system. Pasted text
Don't Forget the Exit
A good support agreement should explain what happens when the relationship ends.
That includes current documentation, runbooks, credential handover, knowledge-transfer time and a final backup that your organisation can restore independently.
These terms are much easier to negotiate when signing the agreement than when leaving it. Pasted text
The Bottom Line
Software support should not begin with the question, “What is the monthly maintenance price?”
Start with:
What needs to stay running? Who owns it? How quickly must it recover? And who still understands it when the original build team is gone?
Once those answers are clear, choosing between warranty, AMC, retained hours and managed service becomes much easier.

Read full blog