SLA
Also: Service Level Agreement, Service-Level Agreement, Service Level Agreements, Accord de niveau de service, Contrat de niveau de service, Dienstgütevereinbarung, Service-Level-Vereinbarung
A formal commitment defining the service level a provider guarantees to a customer, with measurable targets and consequences if they are missed.
What It Is
An SLA (Service Level Agreement) is a written commitment between a service provider and a customer that sets specific, measurable targets for how a service will perform, along with what happens when those targets are missed. It moves a promise from vague reassurance ("our platform is reliable") to a number that can be checked ("99.9% uptime, response within four business hours"). SLAs appear in cloud contracts, software subscriptions, marketing agency retainers, outsourced support, and increasingly in the delivery agreements between internal teams.
Why it matters
For a senior leader, the SLA is where risk becomes explicit and pricing gets justified. A weak SLA transfers operational risk onto your organization without you noticing until an outage hurts revenue or reputation. A CFO reads the SLA to understand what "guaranteed" actually covers and what the penalty (often a service credit rather than cash) is really worth. A CMO signing with a martech vendor checks whether campaign data will be available during peak launch windows. A CDO relying on a data platform confirms latency and recovery-time commitments before betting reporting on it. The SLA also shapes internal accountability: sales and marketing teams frequently agree an internal SLA (marketing delivers X qualified leads, sales follows up within Y hours), turning a recurring argument into a tracked metric.
How it works
An SLA rests on a few components. Service metrics define what is measured: availability, response time, resolution time, throughput. Targets set the threshold (for example 99.95% monthly availability). Measurement rules state how and by whom performance is tracked, since a target means nothing without an agreed way to count it. Remedies specify the consequence, usually service credits scaled to the severity of the miss, plus escalation and termination rights for repeated failures. Exclusions carve out what does not count, such as scheduled maintenance or customer-caused issues. In practice, a leader negotiating an SLA should push on three things: is the metric one that matters to my business outcome, is the measurement independent and visible to me, and is the remedy large enough to change the provider's behavior. A service credit worth a fraction of one month's fee rarely does.
See also
Frequently asked questions
What is an SLA?
An SLA (Service Level Agreement) is a written commitment between a service provider and a customer that sets measurable targets for how a service will perform, plus what happens when those targets are missed. It replaces a vague claim like "our platform is reliable" with a verifiable number such as 99.9% uptime or a response within four business hours. SLAs are common in cloud contracts, software subscriptions, agency retainers and outsourced support.
Why should an executive read the SLA rather than leave it to legal?
Because the SLA is where operational risk and pricing become explicit. A weak SLA quietly transfers risk onto your organization, and you only discover it when an outage hits revenue or reputation. A CFO reads it to see what "guaranteed" actually covers and what the penalty is worth, a CMO to check that campaign data will be available during peak launch windows, a CDO to confirm latency and recovery-time commitments before basing reporting on a platform.
What components make up an SLA?
Five: service metrics (availability, response time, resolution time, throughput), targets that set the threshold such as 99.95% monthly availability, measurement rules stating how and by whom performance is tracked, remedies when targets are missed, and exclusions that carve out what does not count. Measurement rules matter more than people expect, since a target means nothing without an agreed way to count it.
What do you actually get when a provider misses its SLA target?
Most often a service credit scaled to the severity of the miss, not a cash payment, with escalation and termination rights if failures repeat. That distinction matters: a credit worth a fraction of one month's fee rarely changes a provider's behavior. When you negotiate, check whether the remedy is large enough to make the provider invest in avoiding the failure.
Can an SLA be used between internal teams and not just with a vendor?
Yes, and it is increasingly common in delivery agreements between internal teams. Sales and marketing frequently agree an internal SLA: marketing delivers X qualified leads, sales follows up within Y hours. The effect is to turn a recurring argument into a tracked metric that both sides have signed off on.