Choosing an IT AMC Provider: 12 Questions to Ask

An Annual Maintenance Contract looks similar across providers on paper, and very different in practice. The differences show up on the worst day of the year, not during the sales process.

These are the questions worth asking before you sign.

On the contract itself

1. What is explicitly excluded? Every AMC excludes something. The exclusions matter more than the inclusions, because they are where the unexpected invoice comes from.

2. Is this comprehensive or break-fix? Comprehensive includes preventive maintenance and parts; break-fix means you call when it fails. They are not comparable on price alone.

3. What are the response and resolution times, and are they contractual? “Prompt response” is not a commitment. Look for a defined severity matrix with times attached.

On security

4. Who on your team will have administrative access to our systems? Get names and roles. Vague answers about “the team” mean nobody is accountable.

5. How do you manage remote access to our environment? Standing VPN access is a standing risk. Look for per-session approval and logging.

6. What happens to our credentials when the contract ends? They should be rotated, not simply retained.

7. Have you had a security incident that affected a client? Ask directly. The quality of the answer tells you more than the answer itself.

On operations

8. What is your out-of-hours coverage, and is it staffed or on-call? These are different arrangements and the contract usually does not say.

9. How is escalation handled when the first engineer cannot resolve it? Ask for the escalation path in writing, with names.

10. How do you report on what you have done? A monthly report of tickets closed is not useful. Look for trends, recurring incidents and preventative work.

On the commercial relationship

11. Is there a minimum term and what does early exit cost? Multi-year discounts are fine if you understand the exit cost.

12. Who owns documentation and configurations if we leave? If the answer is ambiguous, assume you will have to rebuild everything from scratch.

Red flags worth taking seriously

• No written SLA, only promises in a proposal.
• Reluctance to name the engineers who will hold admin access.
• Pricing far below the field with no explanation of how the scope differs.
• No documented handover process at exit.
• Security questions answered with assurances rather than specifics.

What good looks like

A competent AMC provider will answer these without hesitation and will push back on some of them – particularly around access, where a good provider will want tighter controls than you might propose. A provider uncomfortable with question 4 or question 12 is telling you something.

What an AMC should never cost you

An AMC is not insurance against everything. Understanding what it genuinely covers prevents the argument that happens at the worst possible moment – when a system is down and both sides believe the contract said something different.

Hardware failure outside warranty. Most AMCs cover labour on covered devices, not replacement parts for equipment the manufacturer no longer supports.

Third-party application support. Your AMC provider supports the infrastructure. The ERP vendor supports the ERP. When the ERP fails on the infrastructure, both will initially point at the other.

Projects disguised as support. A new server rollout is a project. If the contract has no project rates, expect an uncomfortable conversation.

Security incidents. Very few AMCs include incident response. A ransomware event is not a support ticket, and treating it as one wastes the most valuable hours.

What to put in writing

• A device list. Named assets with makes, models and support status. An AMC that covers the category but not your specific equipment is worth little.
• A severity matrix. What counts as critical, and what response time attaches to each level.
• Named escalation contacts with phone numbers, not a generic support address.
• An exclusions schedule. Explicit, in the contract, agreed before signature.
• An exit clause. Documentation and configuration handover on termination.

How to compare two AMC quotes fairly

Quotes are rarely like for like. Before comparing price, check whether both cover the same device list, the same hours, the same response times and the same exclusions. A cheaper quote covering half the devices is not cheaper.

The most useful comparison exercise is to take your worst realistic scenario – a core switch failure on a Monday morning – and ask each provider to walk through exactly what happens, who responds, and how quickly.

Frequently asked questions

How much does an IT AMC cost in India?

Pricing varies widely with scope, device count and response commitments. The more useful question is what happens to the invoice when something outside scope fails – a cheap contract with a narrow scope can cost more over a year than a comprehensive one.

Should we use a local provider or a national one?

Local providers typically respond faster on-site; national providers usually have deeper bench strength. Ask about both response time and escalation depth before deciding.

Can we move from break-fix to AMC later?

Yes, and it is usually worth doing. Break-fix arrangements tend to reward reacting to failures rather than preventing them.

Next step

See how our outsourcing and contracting engagements work, or talk to us on +91 97315 99227.