
Quick answer
What is a software SLA and what should a business include in it?
A software SLA for business is a written agreement that says how fast your software provider will respond to and fix problems. It should define severity levels, response and resolution times, support hours in IST, uptime meaning, escalation contacts, backups, security duties, monthly reports, exit and handover steps, and what happens when targets are missed.
Key takeaways
- An SLA puts support promises in writing.
- Response time is not the same as fix time.
- Define severity levels with real examples.
- State support hours clearly in IST.
- Include backups, security and monthly reports.
- Plan exit and handover before you need it.
What is a software SLA for business?
A software SLA for business is the part of your contract that sets measurable support promises: how fast the provider replies, how fast it fixes issues and how it reports on this. It turns "we will support you" into clear numbers and steps.
An SLA is common for software maintenance, hosting, cloud services, IT support and outsourced development teams. It may be a separate document or a section inside the main contract or annual maintenance contract (AMC).
Without an SLA, every problem becomes a negotiation. You call, you wait and you are not sure when it will be fixed. With an SLA, both sides know what is expected. This is useful when you outsource IT work to a team in another city, since most of the contact happens online.
What is the difference between response time and resolution time?
Response time is how fast the provider confirms your issue and starts work. Resolution time is how fast the issue is actually fixed or a working workaround is in place.
Many SLAs only promise response time. A quick reply that says "we are looking into it" is good, but it does not fix your billing screen. A useful SLA has both.
| Term | What it means | What to check |
|---|---|---|
| Response time | Time from your report to the provider's first real reply | Is it an auto-reply or a person who has read the issue? |
| Resolution time | Time until the issue is fixed or a workaround is live | Does the clock pause while waiting for your reply? |
| Workaround | A temporary way to keep working while the full fix is made | Is there a deadline for the permanent fix? |
| Update frequency | How often the provider sends progress updates | Is it set for each severity level? |
How should severity levels be defined in an SLA?
Severity levels group issues by how much they hurt your business, and each level gets its own response and resolution targets. Define them with real examples from your own software.
Most SLAs use three or four levels, often named P1 to P4 or Critical to Low. The names matter less than the examples. Both sides should agree in advance what counts as critical.
| Level | Meaning | Example |
|---|---|---|
| P1 Critical | Software is down or a core task is blocked for everyone | No one can log in, or GST invoices cannot be created |
| P2 High | A key feature is broken but work can go on with difficulty | UPI payment status not updating, staff marking it by hand |
| P3 Medium | A feature has a problem that affects some users | A report shows wrong totals for one branch |
| P4 Low | Minor issue, question or small change request | A spelling error, or a request to add a new field |
The response and resolution targets for each level should be written in the SLA as hours or business days. Shorter targets for P1 usually need more support people on standby, which affects the cost.
What does uptime mean in a software SLA?
Uptime is the share of time the software or server is available and working, usually measured each month. It matters most for cloud software, websites and apps that your staff or customers use all day.
SLAs often write uptime as a percentage. For example, an SLA might promise "99.9% uptime per month". This is only an example of how such terms are written. The higher the number, the less downtime is allowed in a month, and the more the setup usually costs.
Questions to ask about uptime
- How is uptime measured, and by which tool?
- Is planned maintenance counted as downtime or not?
- When is planned maintenance done? Is it outside your business hours in IST?
- What about outages caused by the hosting or cloud provider?
Uptime depends a lot on hosting. If your software runs on a cloud platform, the cloud provider has its own SLA. Your software provider's SLA should explain how the two fit together. Our cloud solutions team can help you plan hosting that fits your uptime needs.
What support hours and escalation should the SLA include?
The SLA should state support hours in Indian Standard Time (IST), say whether weekends and holidays are covered, and list who to contact at each stage if an issue is not moving.
Support hours
Business hours support might be Monday to Friday during office time. Some businesses also need extended hours or 24x7 cover for critical issues, such as an online store or a factory running night shifts. Make sure the clock for response time only runs during the support hours you have agreed, and that this is written clearly.
List the national holidays and any regional holidays when support is limited. A business in one state and a provider in another may have different local holidays.
Escalation matrix
- 1
Level 1: support desk
First contact for all issues, logs the ticket and tries a first fix.
- 2
Level 2: senior developer or team lead
Takes over if the issue is not fixed within the agreed time.
- 3
Level 3: project or delivery manager
Steps in when a P1 or P2 issue is still open or keeps coming back.
- 4
Level 4: company leadership
Final contact for serious or repeated SLA breaches.
Each level should have a name and contact. Issues should be logged as tickets, even when first reported on WhatsApp or phone.
Need help with your project?
Talk to the SI Company India team. Free first call, simple advice, clear quote.
What should the SLA say about backups and security?
The SLA should say how often backups are taken, where they are kept, how long they are kept and how fast data can be restored. It should also list security duties such as access control, updates and how breaches are reported.
- Backup frequency, such as daily database backups
- Backup location, kept separate from the main server
- How long backups are kept
- Target time to restore data after a failure
- Regular test restores, not just backups
- Who has access to servers and code, and how access is removed
- How often security patches and updates are applied
- How quickly you will be told about a data breach or suspected breach
India has rules on reporting certain cyber incidents through CERT-In, and the Digital Personal Data Protection Act, 2023 covers personal data. Ask your legal adviser which rules apply to you, and make sure the SLA supports them.
What reports and reviews should the provider share?
Ask for a short monthly report that shows tickets raised, tickets closed, response and resolution times against targets, uptime and any open risks. Then review it together.
- Number of tickets by severity level
- How many met or missed the SLA targets
- Uptime for the month and any outages, with causes
- Backups taken and any test restores done
- Security updates applied
- Issues that keep coming back, with a plan to fix the root cause
Go through it on a short monthly call to raise concerns early. If you work with dedicated developers, this review also helps plan their time for the next month.
How should an SLA handle exit, handover and penalties?
The SLA should explain what happens if targets are missed, usually through service credits, and what the provider must hand over if the contract ends. Both protect you if the relationship does not work out.
Penalties and service credits
A service credit is a discount on a future bill when the provider misses an SLA target. For example, an SLA might reduce the monthly fee by a set share if uptime falls below the agreed level. Credits are usually capped. Repeated serious breaches may give you the right to end the contract. Keep the rules simple, so both sides can work them out from the monthly report.
Good signs in an SLA
- Clear severity levels with examples
- Both response and resolution targets
- Support hours stated in IST
- Named escalation contacts
- Exit and handover steps written down
Warning signs in an SLA
- Only vague words like "best effort" or "as soon as possible"
- No difference between bugs and new work
- No reports or way to measure targets
- No mention of backups or data return
- Code and server access kept only by the provider
Exit and handover
- Full source code and database handed over on exit
- All server, domain and cloud logins in your company name
- Technical notes on how to deploy and run the system
- A handover period to brief the new team
- Data deleted from the provider's systems after handover, if you ask
How do you set up a software SLA, step by step?
List your critical tasks, agree severity levels and targets with the provider, write them into the contract, and review results every month. Change the SLA as your business grows.
- List the tasks your business cannot stop, such as billing, orders or payroll.
- Decide the support hours you really need in IST.
- Agree severity levels with examples from your own software.
- Set response and resolution targets for each level.
- Add uptime, backups, security and reporting terms.
- Write the escalation matrix with names and contacts.
- Add service credits and exit and handover terms.
- Have your legal adviser review the final document.
- Review the SLA each year and update it as needs change.
If you are not sure what levels fit your business, our technology consulting team can help you plan them. SI Company India works with businesses across India fully online, so support, reviews and handover can all happen over calls, tickets and shared documents.
What affects the cost of a software support SLA?
Cost depends mainly on support hours, how fast the targets are, the size of the software and how many people must be on standby. We do not share fixed prices here. You get a clear quote after a free call.
- Business hours only, extended hours or 24x7 cover
- How short the P1 and P2 response and resolution targets are
- Size and age of the software, and the quality of its code
- Hosting and uptime needs
- Number of users, branches and outside integrations
- Monthly hours included for small changes
SI Company India is powered by Shivah Web Tech, with 11+ years of experience, a 25+ member in-house team and 500+ projects. Our team works Monday to Friday, 9:30 to 6:30 IST, with 24x7 emergency support for urgent issues. Learn about our software development work or contact us to talk about a support plan.
Frequently Asked Questions
What is an SLA in software support?
An SLA, or Service Level Agreement, is a written promise from a software provider about the level of support you will get. It covers how fast they respond, how fast they fix issues, support hours, uptime, backups and reports. It also says what happens when targets are missed. It makes support measurable instead of based on goodwill.
Does a small business need a software SLA?
Yes, if your work depends on the software every day. Even a short SLA of one or two pages helps. It should cover severity levels, response times, support hours and backups at the least. Without it, you have no clear way to know when an issue will be fixed or what to do if support is slow.
What is the difference between an AMC and an SLA?
An AMC, or annual maintenance contract, is the yearly agreement to maintain and support your software. An SLA is the set of measurable service promises, such as response times and uptime. An AMC can include an SLA as one section. An AMC without clear SLA terms often leads to confusion about how fast issues will be handled.
What does 99.9% uptime mean?
It means the software or server should be available for 99.9% of the time in the period measured, usually a month. That leaves a small amount of allowed downtime each month. The exact meaning depends on how the SLA counts planned maintenance and how uptime is measured, so always read those details carefully.
What is a good response time for critical software issues?
It depends on how much a critical issue hurts your business. A software outage that stops billing or orders needs a much faster response than a report error. Agree targets that match your real risk, and remember that shorter targets and longer support hours usually cost more because more people must be ready.
What are service credits in an SLA?
Service credits are discounts on a future bill when the provider misses an agreed target, such as uptime or resolution time. They are usually capped at a share of the monthly fee. Credits are not meant to cover all your losses. They encourage the provider to meet targets and give you a fair remedy.
Should the SLA cover new features and changes?
The SLA should say how change requests are handled, but they should be kept separate from bugs. Bugs are fixed under the support terms. New features are planned, quoted and scheduled. Some plans include a set number of hours each month for small changes, which helps avoid delays for minor updates.
Can software support work well if the provider is in another city?
Yes. Most software support is done online through tickets, calls, remote access and shared documents. What matters is clear SLA terms, a good ticket system, named contacts and regular reviews. Make sure support hours are stated in IST and that urgent issues have a fast contact route, such as a phone number.


