SLA (Service Level Agreement)
An SLA (Service Level Agreement) is a written commitment from a provider that states how quickly problems will be answered and fixed, how much uptime is promised and what happens if those targets are missed.
An SLA is a promise with numbers in it. It is the document, or the part of a contract, that says how quickly a provider will answer a problem, how quickly it will be fixed and what the provider owes you when it is not. Without those numbers, "we will support you" means whatever the provider wants it to mean on the day.
What a useful SLA contains
- Scope: which systems and which kinds of problem are covered.
- Severity levels: for example, "nobody can bill" is critical, while "a report column is misaligned" is minor.
- Response and resolution times: response means a person acknowledges the problem; resolution means it is fixed or a workaround is in place.
- Hours: business hours or round the clock, and in which time zone.
- Uptime target and remedy: the figure promised, how it is measured and what happens if it is missed, such as a fee credit.
What a written SLA changes
An SLA turns an argument into a lookup. It also forces an honest conversation about cost, because quicker response and longer hours need more people and so a higher fee. Beware of dramatic penalties on a small contract; the provider simply prices the risk into the fee. A one-page SLA that both sides can keep is worth more than a ten-page one nobody reads. The uptime clause is explained under uptime.
An example: a transport operator in Namakkal
Take a lorry operator that dispatches trucks through a trip-sheet application, where drivers wait for their slips every morning. A sensible clause for this business might say that if nobody can issue a trip sheet, someone responds within thirty minutes between five in the morning and ten at night and a workaround is in place within four hours, while a faulty report can wait until the next working day. Those figures are illustrative; the structure is the point. Our page on software for logistics companies shows the systems involved.
Our approach to response times
At VS Tech Builders our plans carry defined support periods, and for larger systems a maintenance retainer is available as an option, which is where response times belong. If you want specific figures written into a retainer, tell us during scoping and we will agree numbers we can genuinely meet. Read about software maintenance and the cost of app maintenance in India before you decide how much cover you need.
Common questions
Does a small software project need an SLA?
A short one, yes. For a website or a small app, a half-page note covering who to contact, how fast you will hear back and what counts as urgent is enough. Elaborate service credits and multi-level escalation suit large contracts. What matters is that expectations are written down before the first problem occurs, so nobody argues about them during it.
What is the difference between response time and resolution time?
Response time is how long the provider takes to acknowledge your report and start work. Resolution time is how long it takes to fix the problem or provide a working alternative. A promise of a one-hour response says nothing about the repair, so insist that both figures are written down for each severity level.
Read more
Tell us what you need. Get a fixed quote.
Describe your business and the problem in a few lines. We reply within one business day with an honest recommendation, a scope and a fixed price.