Software AMC & Maintenance Cost Guide for India (2026)

Software AMC (Annual Maintenance Contract) in India typically costs 15–25% of the original development cost per year in 2026. A ₹10 lakh business application should budget ₹1.5–2.5 lakh annually for maintenance — covering bug fixes, security patches, dependency updates, backups, and small enhancements. Simple websites run ₹15,000–60,000/year; complex ERPs and platforms with integrations run 20–30% of build cost.

Maintenance is the least glamorous line in a software budget and the one that decides whether your ₹10 lakh system is still serving you in year five or quietly rotting. This guide from NexaEx explains what AMC should include, what it costs across system types, and how to structure a contract that doesn't punish you later.

What does a software AMC actually cover?

A well-drafted AMC has four layers. Insist on seeing all four in writing:

1. Corrective maintenance — bug fixes with defined severity levels and response times. A payment failure at 11 am on GST filing day is not the same as a typo on the About page; the contract should say so, with hours attached.
2. Preventive maintenance — dependency and framework updates, security patches, SSL renewals, database optimisation, backup verification. This is the layer cheap AMCs silently skip, and it's the one that prevents the 2 am disaster.
3. Adaptive maintenance — keeping up when the world changes: a payment gateway deprecates an API version, WhatsApp changes template rules, Android 17 breaks a permission your app used, GST returns add a field. None of this is your vendor's "fault", but somebody must do the work.
4. Minor enhancements — small changes bundled into the AMC, usually capped in hours per month (e.g., 8–10 hours). New modules are separate projects; a new column on a report should not be.

If a contract only promises "bug fixing support", you're buying layer 1 and will pay list price for everything else.

Software AMC cost table (India, 2026)

Percentages beat absolutes: 15–20% of build cost for standard systems, 20–30% where integrations and compliance churn are heavy. Under 10% is a red flag — the vendor either won't answer the phone or is planning to bill every ticket separately.

Why is maintenance so expensive when the software "already works"?

Because software sits on moving ground. In any given year, your stack will face: two-to-four framework security releases, at least one breaking change from a payment/SMS/WhatsApp provider, an OS or browser update that alters behaviour, certificate renewals, and organic data growth that turns a fast query slow. In 2026 add AI-layer drift: models get deprecated (the model your chatbot launched on will likely retire within 18–24 months), pricing changes, and prompts that worked degrade as usage patterns shift — we covered those recurring AI costs in the AI chatbot cost guide.

None of this is visible to users until it fails. AMC is the difference between these changes being absorbed quietly and being discovered as outages.

There's also compliance. The DPDP Act 2023 makes data breach notification and reasonable security safeguards a legal obligation for Indian businesses handling personal data — unpatched software is the most common breach vector. For NBFC systems, RBI's IT outsourcing and cybersecurity norms expect documented patch management and audit trails; our LoanKard clients treat AMC as a compliance artefact, not just a support plan.

AMC pricing models: retainer vs hourly vs per-ticket

• Fixed annual retainer (recommended for most SMBs): predictable cost, defined SLA, monthly hour bank for small changes. Typical: ₹12,000–50,000/month for SMB systems.
• Hourly/on-demand: ₹800–2,500/hour for Indian agencies in 2026 (metro agencies at the top of that band). Fine for stable, simple systems; risky for anything customer-facing because there's no response-time guarantee when things break.
• Per-ticket: looks cheap, creates perverse incentives — the vendor earns more when your software breaks more, and preventive work never happens.
• Dedicated support engineer: ₹40,000–90,000/month for a fractional or full-time named resource; sensible past ₹25–30 lakh of deployed software.

Hybrid structures work well: a modest retainer covering monitoring, patches, and priority response, with enhancement work quoted separately against a pre-agreed hourly rate.

What should an AMC's SLA actually say?

Numbers, not adjectives. A usable SLA for an SMB business application:

• Critical (system down, payments failing): response within 2–4 business hours, workaround within 24.
• High (feature broken, users blocked): response same business day, fix within 3 business days.
• Normal (cosmetic, minor bugs): next release cycle, within 2–4 weeks.
• Uptime: 99.5% monthly for standard business apps (≈3.6 hours downtime allowance); 99.9% costs meaningfully more in infrastructure.
• Backups: daily automated, weekly restore test — an untested backup is a hope, not a backup.
• Support hours defined (e.g., Mon–Sat 9:30–18:30 IST), with an emergency channel for critical issues.

Also insist on a monthly one-page report: tickets handled, patches applied, uptime, backup status. Vendors who won't report won't be doing the preventive work either.

What happens if you skip AMC?

We inherit two or three of these systems every year, so the pattern is familiar:

• Year 1: nothing visible happens. The gamble feels smart.
• Year 2: a gateway API version retires; checkout breaks on a festival weekend. Emergency fix at crisis rates: ₹40,000–1 lakh, plus lost sales.
• Year 3: the framework version is end-of-life; a known vulnerability is being scanned for. Upgrading three years of skipped versions costs ₹2–5 lakh — several times the skipped AMC.
• Year 4–5: the original vendor has moved on, no one has credentials or context, and "small change" quotes start at rebuild prices. This trajectory — and how switching costs compound — is exactly what our sibling post Hidden costs in software projects maps in detail.

Deferred maintenance isn't saved money; it's an unhedged liability with 30–50% annual interest.

In-house engineer vs vendor AMC: which is cheaper?

Past a certain software footprint, businesses consider hiring their own developer instead of paying AMC. The 2026 numbers: a capable full-stack developer in tier-2 Tamil Nadu costs ₹4.8–9 lakh/year (₹40,000–75,000/month); in Chennai or Bangalore, ₹8–15 lakh. Against a ₹2–3 lakh AMC, the vendor wins on cost until you have roughly ₹25–40 lakh of deployed software or a genuine stream of weekly change work.

The comparison isn't purely financial. One in-house engineer is a single point of failure — they take leave, they resign (average tenure in Indian IT is under 3 years), and no single person covers mobile, backend, DevOps, and security equally. A vendor AMC gives you a bench. The mature pattern we see at ₹30 lakh+ footprints: one in-house "product owner" who knows the business and handles small changes, backed by a vendor retainer for infrastructure, security, and anything deep. That hybrid usually beats either extreme.

Questions to ask before signing an AMC

• Which of the four maintenance layers are included, and where exactly does "enhancement" begin?
• What are the response times for critical issues on weekends, in hours?
• Who verifies backups, how often, and when was the last restore test?
• Are framework and dependency upgrades included, or quoted separately?
• If we exit, what's handed over and within how many days?
• Can we speak to two clients who've been on your AMC for 2+ years?

Ten minutes with this list tells you more than the SLA PDF will.

How to negotiate a fair AMC

• Get scope in writing: the four layers above, hour caps, exclusions, and what counts as an enhancement.
• Own everything: code repository, cloud account, domain, and database must be in your name. AMC should never be a hostage arrangement — if you can't fire the vendor, it isn't a contract, it's a lease on your own system.
• Ask for the runbook: deployment steps, credentials inventory, backup locations. A vendor confident in their AMC will hand it over; one who resists is selling lock-in.
• Review annually: as systems stabilise, AMC should drift down toward 12–15%; as you add modules, it steps up. Recalculate against current system value, not the original invoice, using something like our project cost calculator as a baseline.
• Check the team, not the brand: ask who specifically answers a Saturday-evening critical ticket. A named escalation path beats a glossy SLA document.

At NexaEx we run AMC for systems we built and systems we didn't — taking over an orphaned codebase starts with a 1–2 week audit (₹25,000–75,000) so we can quote maintenance honestly. Several of our case studies began exactly that way.

Talk to us

If you have running software with no maintenance contract — or an AMC you suspect covers less than you think — send us the details. We'll review the scope and tell you what's missing, without drama. Reach us at /contact or WhatsApp +91 97912 97741. We reply within 24 hours.