Your software breaks. Your team can't work. How fast does your vendor respond? That's where a Service Level Agreement (SLA) comes in—and it's the single most important contract clause most customers never read carefully. This guide walks you through what to demand, what's realistic, and how to spot weak SLA language before you're stuck waiting 72 hours for a critical fix.
What Is a Software Maintenance SLA?
An SLA is a legal commitment from your vendor about how they'll support you. It spells out response times (how fast they acknowledge your problem), resolution times (how fast they fix it), and uptime guarantees (how often your software actually works). Without one, you have no recourse if support ignores you or your system stays down for days.
The contract should be measurable and specific. "Fast support" is meaningless. "4-hour response time for Severity 1 incidents" is actionable.
Response Time vs. Resolution Time
These aren't the same, and vendors often blur the line.
Response time means someone from support acknowledges your ticket and asks clarifying questions. You might hear back in 1 hour, but the actual fix could take weeks. Resolution time means the problem is actually solved and your system works again.
Most vendors offer tiered response times based on severity:
- Severity 1 (critical, system down): 1–4 hour response; 4–24 hour resolution target
- Severity 2 (major feature broken): 4–8 hour response; 2–5 day resolution target
- Severity 3 (minor bug, workaround exists): 8–24 hour response; 5–15 day resolution target
- Severity 4 (cosmetic or enhancement request): 24–48 hour response; no fixed resolution time
Always ask: What counts as Severity 1? Does "system down for one user" trigger it, or only "system down for all users"? Vendors define this differently, and the definition matters.
Uptime Guarantees and Credits
Many vendors promise 99.5%, 99.9%, or even 99.99% uptime. The difference is tiny but expensive. 99.5% allows 3.6 hours of downtime per month; 99.9% allows 43 minutes.
Check what happens if they miss the guarantee. Most offer service credits—a partial refund of that month's fee. A typical range:
- 99.5% uptime missed → 10% credit
- 99.0% uptime missed → 25% credit
- Below 99% → 50% credit or cancellation option
Read the fine print: Do planned maintenance windows count as downtime? (Usually they don't, and vendors can schedule maintenance during your business hours if the SLA allows it.) What's the maximum credit per month? Some cap it at 30% even if you're down for days.
What to Look for in a Real SLA
1. Define Severity Clearly Demand specific examples. "Severity 1 means the application is completely inaccessible to all users" is clear. "Critical issues" is not.
2. Exclude Unreasonable Exclusions Many SLAs exempt issues caused by your code, your network, third-party integrations, or beta features. That's fair. But push back if they exclude "issues reported outside business hours" or "issues you didn't report fast enough." You shouldn't lose coverage because you discovered a bug at 6 p.m. Friday.
3. Request Escalation Paths A good SLA names an escalation manager you can contact if standard support isn't solving the problem. Without this, you're stuck in a queue.
4. Confirm Incident Communication Will they update you hourly during an outage? Daily? Insist on a minimum frequency, especially for Severity 1 incidents.
Typical Pricing Impact
SLA tiers directly affect cost. A basic plan with 24-hour response might run $500–$2,000/month. A premium SLA with 1-hour response and 99.99% uptime can cost 2–3× more. Compare vendors carefully—sometimes a cheaper base price with weak SLA is far more expensive than a higher-tier alternative.
How to Compare Vendors
When evaluating software maintenance providers, use these questions:
- What's the response and resolution time for your typical use case?
- Is the uptime guarantee tied to their infrastructure, or does it exclude third-party dependencies you depend on?
- What's the actual credit mechanism, and how often do they miss targets?
Mercoly lets you compare Software Maintenance & Support providers side-by-side, view their SLAs, and read customer reviews about real-world response times—cutting your evaluation time in half.
Frequently Asked Questions
Q: Can I negotiate SLA terms? Yes. Vendors often list standard SLAs online, but enterprise customers almost always negotiate tighter response times, higher uptime guarantees, or broader severity definitions in exchange for longer contracts or higher volume commitments.
Q: What if the vendor misses their SLA? You're entitled to the service credit outlined in the agreement. Document every incident with timestamps and push back if they refuse; repeated misses give you grounds to exit the contract early.
Q: Do all software maintenance plans include an SLA? No. Cheap, community-supported, or self-service options rarely come with formal SLAs. If uptime matters to your business, demand one in writing before signing.
Start comparing trusted vendors today on Mercoly to find the SLA that matches your needs and budget.