Service Level Agreement (SLA)
An internal commitment between teams — typically how quickly sales will work a lead marketing delivers, and what quality standard marketing will deliver.
What it commits to
A stated, measured obligation between functions — typically that leads passed will be contacted within a defined time, and that leads passed will meet a defined standard. Internally there is no contract to enforce, so an SLA holds only through measurement and visibility.
Three properties of one that works
Instrumented. The commitment is computed automatically from timestamps and reported without anyone having to ask. An SLA nobody measures is a preference.
Mutual. Both sides carry an obligation. A response-time commitment with no matching quality commitment binds the party who does not control the input, which is why it gets ignored.
Consequential. Something happens on breach — escalation, reassignment, a review. Not punishment; a defined next step. Without one, the commitment is advisory.
Set the threshold from your own data
Measuring it honestly
Report the distribution, not the mean. A mean inside the threshold is consistent with a substantial tail well outside it, and the tail is the loss.
Measure from record creation, not from assignment. Measuring from assignment excludes routing delay, which is frequently the largest component.
Report the breach rate by segment and source. Breaches usually concentrate rather than spread evenly, and the concentration identifies the cause.
Pair with a quality measure from the sending side — acceptance rate, or completeness of required fields — so both obligations are visible on the same report.
Where SLAs go wrong
The most common failure is an SLA that is met while the outcome worsens: contact happens inside the window, by an automated email that nobody answers. Where the commitment can be satisfied without the underlying work happening, the SLA measures compliance rather than service — which is the general failure mode of any measure used as a target.
RELATED TERMS
Lead Response Time
The elapsed time between an inbound lead arriving and a human making a genuine first attempt to contact them.
Lead Routing
The rules assigning each inbound lead to a specific owner — by territory, segment, product, account ownership or round-robin.
Marketing Qualified Lead (MQL)
A lead that marketing considers ready for sales attention, according to a definition both teams have agreed. Without that agreement it is a marketing activity metric wearing a pipeline costume.
COMMON QUESTIONS
- What is an SLA in revenue operations?
- A stated commitment between two functions — usually marketing and sales — on how quickly or completely work will be handled after a handoff. Internal SLAs have no contractual force, so they hold only if they are measured and visible.
- Why do internal SLAs fail?
- Three usual causes: the commitment is not instrumented so nobody knows it was missed; there is no consequence or escalation; or it is one-sided, binding the receiving function while the sending function has no obligation on quality.
- What should a lead response SLA be?
- Fast enough that response time is not the binding constraint, which is usually minutes rather than days for inbound demand. Measure your own conversion by response-time bucket and set the threshold where the curve flattens.
- Should an SLA be mutual?
- Yes. A response commitment from sales paired with a quality and completeness commitment from marketing is enforceable; a one-sided version tends to be ignored because the party bearing it cannot control the input.
FURTHER READING
Who Owns Lead Routing? Building a Responsibility Map
Two owners for a process step fails the same way as none. A practical method for mapping responsibility so that ownership is unambiguous and testable.
Lifecycle Stage Definitions That Settle the MQL Argument
The dispute between marketing and sales about lead quality is not a relationship problem. It is two teams using different definitions of the same handoff, and it is resolved by writing the definition down.
Coordination Cost at the Marketing–Sales Interface: A Dependency Analysis
Alignment is usually treated as a relationship problem. Coordination theory treats it as a set of managed dependencies with identifiable failure modes — and the marketing–sales interface has all of them.
Learn how to apply this: RevOps 101: Revenue Operations Foundations
Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.
See the course