The go-live celebration is over, the handover is done, and the integrator is finalising the final invoice. That is precisely when — with your teams exhausted and relieved — vendors choose to slide the maintenance contract across the table. Three pages buried in a purchase order annex, or worse, an amendment emailed over with a 48-hour turnaround request.
This contract will govern your day-to-day operations for the next five to ten years. Negotiation mistakes made here typically cost two to three times more over the life of the agreement than errors made when signing the original contract. This guide is aimed at CIOs and CFOs of mid-market companies — organisations with 50 to 500 users, an ERP that has been live for less than 24 months, and a clear goal of bringing this structural cost line under control.
TMA, AMO, and vendor support: three regimes that are constantly confused
Vendor support — what is (and is not) included in your licence
Vendor support is bundled into your SaaS subscription or your annual on-premise maintenance fee. It covers bugs identified by the vendor, regulatory updates (tax rule changes, statutory filings, payroll compliance), and access to new major versions according to the vendor’s lifecycle policy.
What vendor support does not cover: configuring your specific instance, adapting the system to your business processes, onboarding new employees, or anything related to your custom configuration. When your accountant calls support because an allocation rule stopped working after an update, the standard reply will be: “Please contact your implementation partner.”
TMA (Third-Party Application Maintenance) — delegating to your integrator
TMA is a contract with your integrator — or a specialist third party — to handle level-2 and level-3 support on your instance. They know your configuration, your custom developments, and your integrations with other systems. In practice, TMA covers:
- Resolution of functional and technical incidents outside the vendor’s bug scope
- Minor enhancements (new reports, workflow adjustments, configuration fixes)
- Non-regression testing during vendor updates
- Level-2 user support (escalation from your internal level-1 team)
The classic trap: confusing TMA with a disguised time-and-materials arrangement. A well-structured TMA contract defines a monthly hour bank, response times by severity level, and a formal ticket qualification process. A poorly drafted TMA is simply an open door to time-and-materials billing on every slightly complex incident.
AMO (Owner’s Project Management) — independent oversight
AMO is distinct from TMA. It is an independent party — typically a specialist ERP consultancy — that represents your interests with both the vendor and the integrator. Post go-live, AMO manages steering committees, qualifies enhancement requests, arbitrates scope disputes, and helps prepare renegotiations.
For a mid-market company with fewer than 150 users, permanent AMO is rarely cost-effective. However, engaging an AMO on a project basis — to draft or review your TMA contract, or to manage a major version upgrade — is an investment that pays back quickly.
The 8 clauses to negotiate in your ERP maintenance contract
1. Response times by severity level (P1 / P2 / P3)
This is the most important clause and the one most often handled carelessly. Without a contractual definition of severity levels and the associated response commitments, your provider unilaterally decides the priority of your ticket.
Market-standard levels in 2026:
- P1 — Critical: production down or data compromised. Acknowledgement time: under 1 hour. First diagnosis: under 4 hours. Resolution or workaround commitment: within 8 business hours.
- P2 — Blocking: major functionality unavailable, significant productivity impact but manual workaround possible. First diagnosis: within 8 business hours. Resolution: within 3 business days.
- P3 — Annoying: minor anomaly, limited impact, workaround available. Scheduled resolution in the next maintenance sprint (2 to 4 weeks depending on the delivery cadence).
Require a contractual definition of each level, not left to the provider’s discretion. And distinguish between acknowledgement time and resolution time: receiving an automated email within 15 minutes does not mean an engineer is working on your problem.
2. Coverage windows (business hours vs 24/7)
Standard market coverage is business hours, 8am–6pm, working days. If your operations extend beyond that — shift work, international sites, production on-call schedules — you need extended coverage.
Round-the-clock 24/7 coverage typically costs 30 to 60% more than standard coverage. Before accepting that surcharge across your entire scope, ask yourself: which P1 incidents could realistically occur outside business hours? For most mid-market companies, the answer is: month-end financial close and interfaces with logistics partners. Cover those specific perimeters rather than buying blanket 24/7 coverage.
Also verify how “business days” are defined: a provider based offshore may observe a different public holiday calendar. Require that the non-working day schedule be attached as an annex to the contract.
3. Service continuity guarantees (RTO / RPO)
For SaaS ERP, the vendor offers a platform availability SLA (typically 99.5% to 99.9% monthly). But that SLA covers infrastructure uptime, not data recovery after an incident.
Two metrics to require:
- RTO (Recovery Time Objective): maximum acceptable downtime. An RTO of 4 hours means the system must be operational within 4 hours of a major incident.
- RPO (Recovery Point Objective): maximum acceptable data loss window. An RPO of 1 hour means the most recent usable backup is no more than 1 hour old at the time of the incident.
For on-premise or dedicated-hosted ERP, these metrics must be contractualised with both the hosting provider AND the integrator who manages backups. The two responsibilities are often separate — and the first instinct in an incident is to pass the blame. Require a joint liability clause on RTO and RPO.
4. Version management and updates
This is the most underestimated workstream in ERP maintenance. A major vendor upgrade (moving from version N to version N+1) can require 20 to 80 person-days of testing, configuration corrections, and user validation. If that cost is not included in the TMA scope, it will be billed as time and materials.
What the contract must specify:
- Who decides the upgrade schedule? (you or the provider)
- Who performs non-regression testing? (the integrator, your internal team, or both?)
- In which environments? (at minimum: a staging environment before any production deployment)
- What is the minimum notice period before a major upgrade? (market standard: 30 calendar days)
- If a regression occurs after an upgrade, who bears the cost of the fix?
Most TMA contracts include minor updates (bug fixes, regulatory patches) but exclude major version upgrades. Negotiate a flat annual budget for major upgrades — even partial — rather than facing a surprise invoice every two years.
5. Knowledge transfer and mandatory documentation
When the integrator who deployed your ERP goes bust, is acquired, or loses the team that knew your configuration — which happens more often than you would expect — you end up with a system nobody truly understands.
The knowledge transfer clause must require:
- An up-to-date configuration document: all configuration choices documented, including the reasoning behind each choice (not just the “what” but the “why”)
- Handover scripts: startup, shutdown, backup, and recovery procedures
- Annual documentation update: not a document signed at go-live and never touched again
- At least two trained members of your internal team on first-level operations
This clause is often resisted by integrators because it reduces their lock-in leverage. That is precisely why it is non-negotiable.
6. Service KPIs (MTTR, availability, first-contact resolution rate)
A contract without performance indicators is a blank cheque. The KPIs you must track and contractualise:
- MTTR (Mean Time To Repair): average incident resolution time, by severity level. A target MTTR for P1 incidents should be under 4 business hours.
- Availability rate: percentage of time the system is operational within the contracted coverage window. SaaS standard: 99.5% monthly.
- First-level resolution rate (L1): proportion of incidents resolved by your internal team without escalation to TMA. A healthy L1 rate, after 12 months of production and adequate user training, sits between 60% and 75% of tickets.
- SLA compliance rate: percentage of incidents handled within contractual timeframes. If this falls below 90% over a quarter, a penalty should apply.
Require automated monthly reporting on these indicators, produced by the provider in a standard format (shared dashboard, or at minimum a CSV export). Do not accept a hand-written narrative report that naturally highlights what is going well.
7. Contract exit and reversibility
The reversibility clause is the one your integrator will most want to avoid. It is also the most important in the long run.
What a mid-market company concretely loses when it changes integrators without this clause:
- Source code for custom developments on your instance (typically stored in the integrator’s git repositories, not yours)
- Configuration documentation (if it exists)
- Interface and import/export scripts
- The institutional knowledge behind configuration choices — which is impossible to reconstruct without several weeks of auditing
The reversibility clause must provide for:
- Delivery of all deliverables (code, documentation, scripts) within 30 days of termination notice
- An open, standard format (not a proprietary format readable only with the provider’s tools)
- A transition period where the outgoing integrator assists the incoming one, for a minimum defined duration (standard: 2 to 3 months)
- A prohibition on billing this transition period at a punitive rate
Without this clause, changing integrators takes 9 to 18 months and costs two to four times more than a prepared transition.
8. Pricing (fixed fee vs time-and-materials, annual indexation)
Two models exist:
Monthly fixed fee: a defined hour bank, incidents covered without overruns if qualification is accurate. Predictable for your budget, but exposed to “disguised time-and-materials” risk if the scope boundary is vague.
Time and materials: billing at actual hours worked. Flexible, but uncapped and difficult to budget. Avoid for routine TMA; acceptable for one-off enhancement projects.
The recommended approach for mid-market: a monthly fixed fee with an optional time-and-materials bucket for out-of-scope work. The fixed fee covers incidents and small enhancements; time and materials is triggered by explicit purchase order above a defined threshold (for example, any request exceeding 4 hours).
On annual indexation: negotiate a cap — for example, no more than the applicable IT services labour index (such as CIPS, IMIS, or your national equivalent) plus 2 percentage points, applied only at the annual contract anniversary date.
Real ERP maintenance costs in 2026 — market benchmarks
The following ranges are order-of-magnitude estimates from the consulting market, not precise figures — they depend heavily on the vendor, configuration complexity, and the maturity of your internal team.
Vendor maintenance (included in the licence or as an option): for on-premise solutions, annual vendor maintenance typically represents 15 to 22% of the initial licence cost. For SaaS solutions, it is bundled into the subscription. This covers regulatory updates, bug fixes, and access to vendor support.
Integrator TMA (separate contract): TMA generally represents an additional 10 to 18% of the total initial project cost, depending on configuration complexity and the number of custom developments to maintain. A mid-market company that invested £250,000 in its ERP deployment can expect an annual TMA bill of between £25,000 and £45,000.
Benchmarks by vendor profile:
- SAP (Business One, S/4HANA Cloud Essential Edition): vendor support between 18% and 22% of licence value. Integrator TMA generally higher, as SAP skills are scarce and therefore expensive.
- Sage (Sage 200, Sage Intacct, Sage X3): vendor maintenance around 15 to 18%. TMA more accessible thanks to a broader partner network.
- Odoo (Enterprise): maintenance included in the annual subscription. External TMA variable by provider; the open-source model reduces lock-in but increases dependency on Python/JS developers.
- Microsoft Dynamics 365: monthly SaaS subscription covers vendor maintenance. TMA required for customisations and integrations; large partner market but uneven quality.
These ranges do not include major version upgrade costs (budget separately) or functional enhancements (outside standard TMA scope).
When to build an internal Centre of Excellence (CoE) rather than outsource
The threshold at which a CoE becomes cost-effective
An internal ERP Centre of Excellence — even one reduced to 2 or 3 people — becomes worthwhile when several conditions converge:
- More than 150 to 200 active users
- A broad functional footprint (finance, logistics, manufacturing, HR in the same ERP)
- A sustained pace of change (at least one functional enhancement request per month)
- Significant custom developments that require deep business knowledge
Below these thresholds, an internal CoE costs more than it saves. External TMA remains more efficient.
Roles to recruit internally vs keep in external TMA
Recruit internally:
- A functional lead per major domain (finance, logistics, manufacturing) — not necessarily technical, but a process expert who acts as the integrator’s main contact
- A functional ERP administrator capable of managing access rights, reference data, and simple configuration changes without raising a TMA ticket
Keep in external TMA:
- Deep technical skills (custom development, API integration, database administration)
- Specialist regulatory expertise (complex statutory update management)
- Vendor roadmap monitoring and major version upgrade management
An effective CoE does not replace TMA — it right-sizes it. With a solid internal lead, 40 to 50% of tickets that would have been escalated to TMA are resolved internally, reducing your monthly TMA volume accordingly.
Annual maintenance contract review checklist
Schedule an annual contract review, ideally 3 months before the anniversary date (leaving time to renegotiate if needed). Here are the 10 points to check:
- Major upgrade: is a major upgrade planned in the next 12 months? Is the budget already allocated or does it need to be renegotiated?
- Integrator team turnover: are the people who know your configuration still in place? Request the nominal list and succession plans.
- Indexation clauses: what will the rate be next year? Calculate the impact of the applicable index and negotiate before the anniversary date.
- Last year’s KPIs: average MTTR, SLA compliance rate, number of P1 incidents. If the indicators are deteriorating, raise it now — not during the next major outage.
- Up-to-date documentation: does the configuration document reflect the changes made over the last 12 months? Require an update if not.
- Time-and-materials volume: how many out-of-scope hours were billed this year? Systematic overruns mean either the fixed fee is undersized or the TMA scope is poorly defined.
- New users / new modules: have scope changes made the contract outdated? Adjust the fixed fee to reflect reality.
- Unresolved incidents: are there any tickets open for more than 90 days? Request a formalised resolution plan.
- User satisfaction: collect feedback from your internal leads. A provider that meets deadlines but consistently delivers workarounds rather than fixes is not solving the problem.
- Reversibility clause: if it was not in the original contract, renegotiate it now — before you need it.
To go deeper on ERP governance after go-live, read our post go-live ERP governance and Centre of Excellence guide and our article on reducing ERP licence costs after go-live. If you are still negotiating your initial contract, our guide on 15 clauses to secure before signing your ERP contract gives you the contractual foundations on which to build.
