AMC and Support Contracts Explained: What You Are Actually Paying For
A plain-language breakdown of Annual Maintenance Contracts for business software — what should be included, response-time SLAs, what counts as a bug fix versus a paid change request, and renewal pricing traps.
What an AMC is actually supposed to cover
An Annual Maintenance Contract (AMC) for business software is meant to cover ongoing support after the initial purchase or build — bug fixes, security patches, minor updates, and a defined level of help-desk support for issues that arise during normal use. It is not, in a well-structured contract, meant to cover entirely new features or a significant scope change, which is reasonably billed separately as a change request. The confusion and disputes that arise around AMCs almost always come from this line not being clearly defined at the start — what exactly counts as a covered bug fix versus a chargeable enhancement — leaving it open to interpretation exactly when a business is least equipped to negotiate, in the middle of needing something fixed urgently.
Response-time SLAs: the number that actually matters
The single most important line in any AMC is the response-time SLA — not a vague promise of 'quick support,' but a specific, contractually defined time: for a critical issue like billing being completely down, what is the guaranteed response time, and what is the guaranteed resolution time or next-update interval if the issue takes longer to resolve? For a minor cosmetic issue, what is the reasonable, separately defined response window? A four-hour response commitment for a critical outage, in writing, with a defined remedy if missed (credit, escalation), is worth meaningfully more than an unwritten reputation for being responsive — get the number in the contract, not just in the sales conversation.
Bug fix versus change request: get the definition in writing
A recurring source of AMC disputes is disagreement over whether a specific issue is a covered bug fix (the software not doing what it was originally built to do) or a chargeable change request (a genuinely new requirement not in the original scope). This line will always have some genuinely ambiguous cases, but a good AMC defines the distinction as clearly as possible upfront — for instance, 'any deviation from the documented original functionality is a covered bug fix; any request for functionality not present in the original agreed scope is a change request, quoted separately' — rather than leaving it to be argued case by case with no defined principle to fall back on.
What a reasonable AMC typically costs, and why it varies
AMC pricing for business software commonly runs somewhere between roughly ten and twenty percent of the original software or license cost annually, though this varies meaningfully by the complexity of the system, the response-time SLA committed to, and how much of the support is proactive (regular health checks, preventive patching) versus purely reactive (only responding when something breaks). A very low AMC quote relative to this range is worth questioning specifically — ask what response-time SLA it actually includes, since an unusually cheap AMC sometimes means a correspondingly slow or minimal support commitment behind it, not simply better value.
Renewal pricing: the trap that appears in year two
A software or AMC quote that looks reasonable in year one sometimes increases substantially at renewal, once a business is genuinely dependent on the system and switching would be disruptive — a well-known pattern across many software categories, not specific to any one vendor type. Before signing an initial contract, ask explicitly what renewal pricing will look like, and try to get either a capped increase percentage or a fixed multi-year price written into the agreement, rather than discovering the renewal number only when the invoice arrives a year in, at which point your negotiating leverage is much weaker than it was before signing.
Questions to ask before signing any AMC
Ask for the specific response-time SLA for both critical and minor issues, in writing, with a defined remedy if missed. Ask for a clear, written definition of what counts as a covered bug fix versus a chargeable change request. Ask what is included versus explicitly excluded — security patches, minor version upgrades, data backup verification. Ask what renewal pricing will look like, and try to cap it in writing now. And ask for at least one reference from an existing AMC customer who can speak specifically to how a real support issue was actually handled, not just whether they are generally satisfied.
Relevant Services & Industries
Technical Consultancy
CTO-as-a-service and technical audits that give founders and leadership teams clarity before they commit budget.
Custom Software Development
Purpose-built software engineered around your exact workflow — not a template stretched to fit your business.
ERP Solutions
Enterprise ERP that unifies finance, sales, and HR on one platform — replacing disconnected spreadsheets with real-time visibility.
Common Questions
Keep Reading
Custom Software vs Off-the-Shelf: A Real Decision Framework
A grounded framework for the custom-vs-SaaS decision — total cost over 3-5 years, the customization ceiling of off-the-shelf tools, data ownership, and integration needs — without vendor bias in either direction.
ReadSoftware for Government Contractors: Managing e-Tenders and Compliance Without the Audit-Day Scramble
A practical look at what government contractors actually need from software — e-Tender and GEM tracking, compliance documentation, and building an audit trail that holds up under scrutiny.
ReadData Migration Checklist: Switching Business Software Without Losing Data
A practical, sequenced checklist for migrating data when switching business software — data cleaning before migration, a parallel-run period, validation testing, and a real rollback plan.
ReadReady to talk through your specific setup?
Book a free strategy call — a solution architect, not a salesperson, will walk through what actually fits your business.