Software is never really finished. Operating systems update, browsers change, security issues are discovered, third-party services change their APIs, and your own team keeps finding small things they want improved. A software AMC (annual maintenance contract) is how many businesses in India handle this after launch. But AMCs vary widely: some are little more than a phone number, others are a genuine support service. This guide explains what a good AMC should cover, what is usually extra, and how to choose a partner you can rely on.
- A good AMC covers bug fixes, security updates, backups, monitoring and small changes.
- New features and third-party costs are usually outside the AMC.
- Keep your code, hosting and accounts in your own name.
Why you need ongoing support
Without someone responsible for your application, problems tend to build up quietly:
- Security updates for the framework, server or plugins are skipped.
- Backups stop working and nobody notices until they are needed.
- An SSL certificate or domain expires and the site goes down.
- A payment gateway, SMS or email provider changes something and a feature breaks.
- Small bugs pile up and staff build workarounds.
An AMC turns this into planned, predictable work rather than emergencies.
What a good AMC should cover
Bug fixes
Fixing defects in existing functionality: something that used to work, or should work as specified, but does not. This is the core of any AMC.
Security updates
Regular updates to the framework, libraries, server software and dependencies, plus prompt action when a serious vulnerability is announced.
Monitoring and uptime
Basic monitoring so that downtime, errors or full disks are noticed by the support team, ideally before your customers notice.
Backups and recovery
Scheduled backups of the database and files, stored separately from the main server, with periodic test restores. A backup that has never been restored is only a hope.
Hosting and certificate management
Renewing SSL certificates, keeping server resources healthy and coordinating with the hosting provider.
Small changes
Many AMCs include a fixed number of hours each month for minor changes such as a new report column, a text change or a field on a form. Make sure the hours and what counts as "small" are written down.
Support channel and response times
A clear way to raise issues (ticket, email or WhatsApp group) and agreed response times by severity.
Need someone to look after an existing application? Tell us what it runs on and we will propose a clear support plan.
What is usually not included
- New features or modules, which are normally quoted separately.
- Major redesigns or technology upgrades, such as moving to a new framework version that requires significant rework.
- Third-party costs: hosting, domains, SMS, email, payment gateway fees and licences, usually billed at actuals.
- Data entry or operations work that your team would normally do.
None of this is a problem as long as it is clear before you sign.
Understanding response times and severity
A sensible AMC defines a few severity levels, for example:
- Critical: the system is down or a core function such as billing or orders is not working.
- High: an important feature is broken but a workaround exists.
- Normal: a minor bug or a cosmetic issue.
- Request: a small change or improvement.
Each level should have a target response time and a target to fix or provide a workaround. Be realistic: faster guaranteed response, especially outside working hours, costs more. Match the commitment to how critical the software is for your business.
- Bug fixes in existing features
- Security updates
- Backups with test restores
- Monitoring and SSL renewals
- Agreed response times by severity
- New features (quoted separately)
How to choose an AMC partner
- Ask for a code and infrastructure review first, especially if they did not build the software. It shows how they work and tells both sides what condition things are in.
- Check their experience with your technology stack: language, framework, database and hosting.
- Ask how issues are tracked. A ticket history protects both sides and shows what was done.
- Ask who will actually work on your system and what happens when that person is on leave.
- Read the scope and exclusions carefully, not just the price.
- Check exit terms: on termination, you should receive all code, credentials and documentation.
Protect your ownership
Whoever supports your software, keep control of the essentials:
- The source code in a repository you own.
- The hosting, domain and cloud accounts in your company's name.
- Admin access to every third-party service the application uses.
- Up-to-date documentation of how to deploy and run the system.
This makes it straightforward to change partners if you ever need to.
Signs your current AMC is not working
- The same bugs come back after being "fixed".
- Nobody can tell you when the last backup was tested.
- Simple requests take weeks without explanation.
- You do not have access to your own code or server.
- Updates are never applied because "it might break something".
Software AMC and support from Job Vista
Job Vista's technology team supports web applications, ERP and business software for clients worldwide, including software built by other vendors after a review. We agree scope, severity levels and response times in writing, keep your code and accounts in your control, and give you a clear record of every issue. Learn more about our software AMC and support service.
