You’ve found a new B2B data enrichment or prospecting tool. The demo was impressive, the pricing fits your budget, and the features check all the right boxes. You’re ready to sign.
But have you read the SLA?
This document — usually buried in the contract appendix — defines what a vendor is actually committing to. A poorly negotiated SLA means your cold email campaign stalls on a Monday morning, your leads go unenriched the night before a big pitch, or worse: you lose data with no legal recourse.
This guide explains exactly what an SLA is, what “99.9% uptime” really means in practice, and which clauses to verify before adding any B2B tool to your sales stack.
Enrich your leads without interruption, directly in Google Sheets
Derrick is a native B2B enrichment tool built for Google Sheets. Emails, phone numbers, LinkedIn data: enrich your prospects in a few clicks.
What Is an SLA? Definition and Why It Matters for Sales Teams
SLA stands for Service Level Agreement. It’s the contractual document in which a service provider — a SaaS vendor, cloud host, or telecom operator — formally commits to delivering a defined level of service quality. It sets the rules before the service goes live.
An SLA typically covers three dimensions:
- Availability: how long the service must be accessible, expressed as a percentage
- Responsiveness: how quickly the vendor responds to incidents
- Compensation: what you’re entitled to when those commitments aren’t met
For an SDR or Growth Marketer who relies daily on a data enrichment tool or email sequencing platform, the SLA isn’t a technical footnote. It’s the guarantee that your sales stack holds up when you need it most — during a high-volume outbound push, a product launch, or the final stretch before a quarter closes.
SLAs originated in the network services industry to measure transmission quality. They gradually became standard across the entire IT sector — from SaaS platforms to data centers — and are now a core component of every serious B2B cloud contract.
Key SLA Metrics: What Each Term Actually Means
Before comparing contracts, you need to speak the language. Here are the four indicators you’ll find in most SaaS SLAs.
1. Uptime Rate (Availability)
This is the most visible SLA metric. It expresses, as a percentage, the time a service is operational and accessible over a given period — typically a calendar month.
The standard formula:
Uptime (%) = (Total time − Unplanned downtime) / Total time × 100
99.9% sounds impressive. But translated into actual time, the difference between SLA tiers becomes significant.
2. Response Time Guarantee (RTG)
The RTG specifies the maximum time in which the vendor’s technical team commits to acknowledge your incident after you’ve reported it. This is not the resolution time — it’s a confirmation that someone is looking at it.
Example: a 4-hour business hours RTG means that if your ticket hasn’t been acknowledged after 4 hours, the vendor is in contractual breach.
3. Resolution Time Guarantee
The resolution commitment goes further: it defines the maximum time to fix the incident and restore the service. This is the metric that matters most to end users.
A robust SLA distinguishes between criticality levels (P1, P2, P3) with different resolution times depending on severity. A critical incident blocking the entire team gets a resolution target of a few hours; a minor UI bug may allow several business days.
4. SLA Credits (Service Penalties)
When commitments aren’t met, most SLAs provide service credits — typically applied as a discount on your next invoice or as a credit balance. Cash refunds are rare.
These credits almost always come with conditions: you must claim them within a defined window, provide evidence of the outage, and sometimes demonstrate business impact. Read these conditions carefully before signing.
The “Nines” Table: What 99.9% Uptime Actually Means
This is the most misunderstood aspect of SLAs. Sales teams see “99.9% uptime guaranteed” and assume near-perfect service. In reality, each additional “nine” reduces allowed downtime by a factor of 10.
| SLA Level | Common Name | Max downtime / year | Max downtime / month |
|---|---|---|---|
| 99% | “Two nines” | 87.6 hours | ~7.3 hours |
| 99.5% | — | 43.8 hours | ~3.6 hours |
| 99.9% | “Three nines” | 8.76 hours | ~43 minutes |
| 99.95% | — | 4.38 hours | ~21 minutes |
| 99.99% | “Four nines” | 52.6 minutes | ~4.4 minutes |
| 99.999% | “Five nines” | 5.26 minutes | ~26 seconds |
What this means for your sales team:
A 99.9% SLA legally allows up to 43 minutes of downtime per month. If your enrichment tool goes down on a Monday morning — the highest-activity day for most SDRs — those 43 minutes can translate into dozens of stalled sequences, unenriched leads, and a pipeline delay that’s hard to recover from.
A 99.99% SLA reduces that tolerance to under 5 minutes per month. The difference is substantial for teams that depend on continuous availability.
No SaaS vendor can guarantee 100% uptime. Planned maintenance, infrastructure updates, and unpredictable incidents are operational realities. Be wary of vendors who don’t mention an SLA at all — the absence of contractual guarantees leaves you without recourse if something goes wrong.
SLAs for B2B Tools: Specific Considerations for Prospecting and Enrichment
SLAs for prospecting and data enrichment tools have quirks you won’t find in a standard hosting agreement. Here’s what to watch for in your specific context.
API Availability vs. UI Availability
Most B2B tools expose two surfaces: a user interface (UI) and an API for automated integrations. The SLA may cover one without the other, or offer different levels for each.
For Mike, a Sales Ops manager at a growth-stage B2B company syncing his enrichment tool with HubSpot via Zapier, the graphical interface barely matters — it’s API availability that drives his workflows. If the SLA doesn’t explicitly mention the API, ask before signing.
Match Rate and Enriched Data Quality
Some enrichment tool SLAs go beyond technical availability to include data quality commitments: minimum match rates, email validity rates, and data freshness guarantees. These aren’t yet universal, but they’re becoming more common among premium vendors.
If your tool promises an 80% match rate but consistently delivers 50%, you have a performance problem. Without a contractual clause, you have no leverage. During negotiation, ask whether these metrics can be formalized in the SLA or in a performance annex.
Planned Maintenance Exclusions
SLAs almost universally exclude scheduled downtime (updates, nightly maintenance windows) from the availability calculation. These planned outages don’t count against the uptime percentage.
Two things to verify: how frequently maintenance occurs, and during which hours. A tool that takes downtime on Saturday at 2 AM has far less impact than one that cuts out on Tuesday at 9 AM. Some vendors let you configure preferred maintenance windows based on your time zone or peak activity periods.
Data Portability and Exit Clauses
Often overlooked in B2B SLAs: the reversibility clause. If you cancel the contract or the vendor shuts down, how quickly can you retrieve your data, and in what format?
For your prospecting data — enriched emails, phone numbers, LinkedIn profiles — portability is a critical business concern. Make sure the contract specifies a reasonable retrieval timeline and a usable export format.
How to Evaluate a B2B Enrichment Tool’s SLA: Your Checklist
Before signing up for a B2B lead generation or database enrichment tool, ask your sales rep these questions.
On Availability
- What is the guaranteed uptime rate, and over what calculation period (calendar month or rolling)?
- Does that rate apply to the UI, the API, or both?
- Are planned maintenance windows included or excluded from the calculation?
- Is there a public status page with historical availability data?
On Responsiveness
- What are the response time and resolution time commitments by incident priority level?
- Are SLA-backed support tiers included in all plans, or only at Enterprise level?
- What are the support coverage hours? Is English-language support available around the clock?
On Compensation
- How are SLA credits calculated and claimed?
- What’s the deadline for reporting an incident to be eligible for credits?
- What form does compensation take: billing credit, subscription extension, cash refund?
On Continuity
- What is the disaster recovery mechanism (RPO/RTO)?
- Where is data hosted? Which cloud regions (AWS, Azure, GCP)?
- In the event of vendor insolvency, how and when can you retrieve your data?
Common SLA Pitfalls: What to Read Between the Lines
A well-written SLA is a trust document. A poorly written one — or a strategically vague one — can leave you without recourse when it matters most. Here are the four most common traps.
Trap 1: An Uptime Number Without a Definition of “Available”
Some contracts display 99.9% without defining what “availability” actually covers. A service that is “technically online” but returning 500 errors on 40% of API requests is not functionally available. Require a precise definition: availability means the service is accessible AND functional for all critical features.
Trap 2: Overly Broad Exclusions
Exclusion clauses are legitimate for genuine force majeure events and third-party infrastructure outages (e.g., AWS region failures). But some vendors extend them to cover traffic spikes, third-party integration errors, or even “performance degradation” short of full outage. Read this section carefully.
Trap 3: Capped and Conditional SLA Credits
Compensation is often capped at 10-20% of your monthly invoice regardless of outage duration. And you typically need to claim credits manually — within a short window, often 30 days — with supporting evidence. If you don’t act, nothing happens, even in the case of a clear breach.
Trap 4: No SLA on Entry-Level Plans
Many SaaS vendors reserve contractual SLAs for Enterprise plans. Small teams on Starter or Growth plans often have no formal guarantees. That’s not necessarily disqualifying — but you need to factor this into how heavily you depend on the tool.
How to enrich your B2B database
Best practices for enriching your contacts and improving data quality across your prospecting workflows.
SLAs and GDPR: The Inseparable Link for Teams Handling Contact Data
For B2B tools that process personal data — which covers every prospecting, email enrichment, or phone finder tool — the SLA can’t be read in isolation. It must be accompanied by a DPA (Data Processing Agreement), the contractual framework governing how the vendor handles data on your behalf under GDPR.
The DPA clarifies roles: your company is the data controller; the SaaS vendor acts as a data processor. As such, the vendor must commit to:
- Data location (EU hosting or equivalent safeguards for transfers outside the EEA)
- Security measures protecting enriched contact data
- Breach notification within GDPR-mandated timelines (72 hours to notify the ICO or relevant supervisory authority)
- Data deletion at contract end or upon request
A tool that collects professional email addresses or phone numbers without a clear DPA creates compliance exposure. Before deploying an email verification or phone enrichment workflow at scale, confirm that the SLA and DPA are consistent and properly documented.
For a deeper dive into GDPR and cold emailing compliance, check out our dedicated guide.
How SLAs Are Evolving in 2025–2026
SLAs are no longer static legal documents. Several trends are reshaping their content and use across the B2B SaaS landscape.
Dynamic SLAs: some vendors are experimenting with commitments that adapt in real time based on usage patterns and application criticality. A real-time enrichment workflow during a live campaign might carry a reinforced SLA compared to an overnight batch job.
Cybersecurity integration: after years of attacks targeting SaaS vendors, SLAs now increasingly include security metrics — detection time, containment time, customer notification timelines. This matters especially for tools storing B2B contact data at scale.
Real-time transparency: public status pages (like those of Stripe, Notion, or HubSpot) have become table stakes. They allow users to monitor availability live, without waiting for a support email. When evaluating a new tool, check whether a status page exists — it’s often a reliable signal of operational maturity.
Sustainability commitments: hyperscalers are beginning to include energy efficiency metrics in their SLAs. Still niche, but indicative of how these agreements are expanding well beyond pure technical availability.
Key Takeaways
- An SLA is a contractual commitment from your SaaS vendor on availability, response times, and compensation — not a marketing promise
- 99.9% uptime allows up to 43 minutes of downtime per month, which can have real impact on your prospecting campaigns
- Verify that the SLA explicitly covers the API, not just the UI — especially if you rely on Zapier, Make, or n8n integrations
- SLA credits are often capped and conditional: read the claim process before signing
- For tools handling contact data (emails, phone numbers, LinkedIn profiles), require a GDPR-compliant DPA alongside the SLA
- No SLA on entry-level plans is common — calibrate your dependency accordingly
Conclusion: A Well-Negotiated SLA Is a Competitive Advantage
An SLA isn’t paperwork. For a sales team that depends on its tools to enrich contacts, automate sequences, and qualify leads, it’s the guarantee that what was promised actually holds when the pressure is on.
Take the time to read the availability appendix before deploying a new tool in your stack. Ask the right questions before you sign. Build your commercial infrastructure on vendors who commit contractually to their performance — not just on their demo slides.
A reliable B2B enrichment tool, built into Google Sheets
Derrick lets you enrich emails, phone numbers, and LinkedIn data for your prospects without leaving your spreadsheet. Free plan available, no credit card required.
FAQ
What is an SLA in IT? An SLA (Service Level Agreement) is a contract between an IT service provider and its customer that defines uptime commitments, incident response times, and compensation terms for non-compliance. It’s a standard component of any serious SaaS contract.
What’s the difference between response time and resolution time in an SLA? Response time is how long the vendor takes to acknowledge an incident after it’s been reported. Resolution time is the maximum time to fix the problem and restore the service. Resolution time is the more meaningful metric for end users.
Is a 99.9% SLA sufficient for a B2B prospecting tool? It depends on your use case. A 99.9% SLA allows roughly 43 minutes of downtime per month. For most sales teams, that’s acceptable. If you run real-time enrichment workflows or have mission-critical automations, look for 99.99% or negotiate maintenance windows outside your peak activity hours.
Can you negotiate an SLA with a SaaS vendor? Yes — especially at higher volumes or on Enterprise plans. You can negotiate uptime rates, response and resolution time targets, maintenance windows, and compensation levels. Entry-level or free plans rarely offer flexibility on this.
What should you do if your vendor violates the SLA? Document the incident immediately (date, duration, business impact). Then claim your SLA credits within the contractual window — typically 30 days after the incident. For serious or repeated violations, you may have grounds to terminate the contract for breach of obligations.
Jonathan Maurin
