# The Sales–Marketing SLA: How to Write One That Actually Holds

# The Sales–Marketing SLA: How to Write One That Actually Holds

> **Quick answer:** A **sales–marketing SLA** is a written, two-way agreement defining what qualifies as a lead, how many marketing will deliver, how fast sales will follow up, and what happens when either side misses. Most SLAs fail because they're one-way (marketing promises volume, sales promises nothing) or because they lack a rejection-reason loop. A working SLA has shared definitions, mutual commitments, a rejection mechanism, and a standing review meeting.

**Key takeaways**

- **Two-way or worthless.** Marketing commits to quality and volume; sales commits to speed and feedback.
- **Definitions first.** If MQL and SQL aren't defined jointly, nothing else in the SLA is enforceable.
- **Rejection reasons are the engine.** They're how marketing learns what to change.
- **Enforce with a rhythm,** not a document. A monthly review beats a signed PDF.
- **Measure the SLA itself:** compliance rate, not just pipeline.

Every B2B SaaS company has a version of the same argument: marketing says it delivered leads, sales says they were junk, and the pipeline number doesn't move. A **sales–marketing SLA** is how you end that argument with data rather than seniority. This guide covers what belongs in one, why most fail, and the review rhythm that makes it stick.

## What is a sales–marketing SLA?

A **sales–marketing SLA (service level agreement)** is a documented agreement between the two teams specifying: what counts as a qualified lead, how many marketing will deliver per period, how quickly and how many times sales will follow up, how leads are rejected and why, and how both sides are measured. It converts an interpersonal argument into an operational contract with observable metrics.

## Why do most sales–marketing SLAs fail?

1. **They're one-directional.** Marketing commits to an MQL number; sales commits to nothing. Volume then becomes the only incentive, and quality falls.
2. **Definitions weren't agreed.** Marketing's MQL bar and sales' SQL bar were written separately, so leads clear one and fail the other by design.
3. **There's no rejection loop.** Sales rejects leads silently, marketing never learns, and the same bad leads keep arriving.
4. **Nobody reviews it.** The document is signed, filed, and never opened again.
5. **The volume target is the wrong metric.** Measuring marketing on MQL count rewards loosening the definition.

## What belongs in a sales–marketing SLA?

| Section | Marketing commits to | Sales commits to |
|---|---|---|
| Definitions | Deliver leads matching the agreed MQL criteria | Accept leads meeting those criteria |
| Volume | An agreed number of MQLs per period | Capacity to work them |
| Speed | Route and enrich leads immediately | First contact within the agreed SLA window |
| Persistence | Provide qualification context at handoff | An agreed number of contact attempts before closing |
| Feedback | Act on rejection data | Log a rejection reason for every rejected lead |
| Reporting | Report source and quality by channel | Report acceptance and conversion by source |

The right-hand column is what separates a real SLA from a marketing quota.

## How do you define MQL and SQL together?

Put both teams in one room and define the criteria against a single ICP. Fit criteria (company size, industry, role, geography) form the gate; engagement determines priority within it. Write the definitions down in plain language, have both leaders sign off, and store them where the CRM fields live. This is the foundation for everything else — a scoring model built on undefined terms produces the fit-blind scoring described in our [lead scoring guide](https://www.growthspreeofficial.com/blogs/lead-scoring-b2b-saas), and the low conversion rates covered in [improving MQL-to-SQL conversion rate](https://www.growthspreeofficial.com/blogs/improve-mql-to-sql-conversion-rate).

## What should the follow-up commitments be?

Sales' side of the SLA is usually two numbers: a **first-touch window** (how fast) and a **contact attempt minimum** (how persistent) before a lead can be closed as unworked. Set the first-touch window at something the team can consistently meet during business hours — the value is in it being written, alerted, and measured as a median, not in matching an external benchmark. See [speed to lead](https://www.growthspreeofficial.com/blogs/speed-to-lead-b2b-saas) for how to instrument it.

> **Field note:** The clause that makes an SLA work is the mandatory **rejection reason**. Without it, "these leads are junk" is an opinion. With it, marketing sees that 60% of rejections from one channel are "wrong role" and fixes the targeting in a week. Make the reason field required, keep the list short (bad fit, wrong role, no budget, unreachable, timing), and review it monthly. It's the cheapest alignment mechanism in B2B SaaS.

## How do you enforce the SLA?

Not with the document — with a rhythm and a dashboard:

1. **Instrument both sides in the CRM.** Time-to-first-touch, contact attempts, acceptance rate, rejection reasons.
2. **Report SLA compliance weekly.** Percentage of leads contacted within the window, and percentage of rejections with a logged reason.
3. **Hold a monthly review.** Both leaders, one agenda: rejected MQLs by source, SLA breaches, and one change each side will make.
4. **Recalibrate quarterly.** Definitions drift as the ICP evolves; update them deliberately rather than by accident.
5. **Make the data effortless.** Connecting your CRM to an AI assistant — via the [HubSpot CRM MCP](https://www.growthspreeofficial.com/blogs/hubspot-crm-mcp) or [Salesforce MCP](https://www.growthspreeofficial.com/blogs/salesforce-mcp) — turns the review prep into a prompt: *"Show MQL acceptance rate and rejection reasons by source last month."*

## What should you measure?

- **MQL acceptance rate** by source and campaign (the SLA's headline health metric)
- **Median time-to-first-touch** and % of leads inside the SLA window
- **Rejection reasons** by source — the correction signal
- **MQL→SQL rate** trend, segmented by channel
- **SLA compliance on both sides**, reported together

Report both teams' numbers in the same document. An SLA where only one side's compliance is visible is a quota with extra steps.

## Frequently Asked Questions

### Q1. What is a sales-marketing SLA?
It's a written, two-way agreement between sales and marketing defining what qualifies as a lead, how many leads marketing will deliver, how fast and how persistently sales will follow up, how leads are rejected and why, and how both sides are measured.

### Q2. Why do sales-marketing SLAs fail?
Most fail because they're one-directional — marketing commits to lead volume while sales commits to nothing — or because MQL and SQL were defined separately, there's no rejection-reason loop, and nobody reviews the agreement after signing it.

### Q3. What should be in a sales-marketing SLA?
Shared MQL and SQL definitions, a marketing volume commitment, a sales first-touch window and minimum contact attempts, a mandatory rejection-reason field, and agreed reporting on both sides' compliance.

### Q4. How do you enforce a sales-marketing SLA?
With a rhythm, not a document: instrument both sides in the CRM, report compliance weekly, hold a monthly review of rejected leads by source, and recalibrate definitions quarterly as the ICP evolves.

### Q5. What's the most important part of the SLA?
The mandatory rejection reason. Without it, complaints about lead quality stay anecdotal. With it, marketing can see exactly which sources produce wrong-role or bad-fit leads and correct targeting quickly.

**Sources & further reading**

- HubSpot and Salesforce documentation — lifecycle stages, lead status, and rejection-reason fields.
- Establish SLA targets from your own CRM cohort data rather than external benchmarks.

---

*Related guides: [How to Improve MQL-to-SQL Conversion Rate](https://www.growthspreeofficial.com/blogs/improve-mql-to-sql-conversion-rate) · [Lead Scoring for B2B SaaS](https://www.growthspreeofficial.com/blogs/lead-scoring-b2b-saas) · [Speed to Lead](https://www.growthspreeofficial.com/blogs/speed-to-lead-b2b-saas) · [HubSpot CRM MCP](https://www.growthspreeofficial.com/blogs/hubspot-crm-mcp).*