.svg)
Overview
Sales blames marketing for sending bad leads. Marketing blames sales for not following up fast enough. This argument has been happening in every B2B company for decades, and the reason it never gets resolved is that most teams have no shared definition of what "good" looks like, no agreed-upon timelines for action, and no system that enforces accountability on either side. The fix is not another alignment meeting. It is a service-level agreement with teeth.
A sales-marketing SLA is a documented contract between sales and marketing that defines what each team commits to deliver, the quality standards those deliverables must meet, the timelines for action, and the consequences when commitments are missed. For GTM Engineers, SLAs are infrastructure: they define the rules your automation enforces, the metrics your dashboards surface, and the feedback loops that keep both teams honest. This guide covers how to design SLAs that actually work, build the automation that enforces them, create reporting dashboards both teams trust, and close the feedback loops that make the whole system improve over time.
The Anatomy of a Sales-Marketing SLA
An effective SLA has four components. Miss any one of them and the agreement becomes a document that sits in a Google Drive folder and changes nothing.
1. Lead Definitions and Qualification Criteria
Before you can agree on SLAs, you need shared definitions. What is an MQL? What is an SQL? What is a "qualified" lead? These definitions should be specific enough that a computer can evaluate them, not just a human exercising judgment.
| Stage | Definition | Owner | Example Criteria |
|---|---|---|---|
| MQL | Lead that meets marketing qualification thresholds | Marketing | Lead score ≥ 50, ICP fit score ≥ 70, at least one engagement action |
| SAL | Sales-accepted lead; confirmed as worth pursuing | Sales | Rep confirms valid contact, real need, correct persona within 48 hours |
| SQL | Sales-qualified lead; discovery completed, opportunity created | Sales | Budget/authority/need confirmed, next step scheduled |
| Disqualified | Lead that does not meet minimum criteria | Either | Wrong industry, too small, no budget, competitor employee |
The critical piece most teams miss is making these definitions machine-evaluable. Your lead scoring model should be able to apply MQL criteria automatically. Your CRM should have required fields that force reps to select a disposition reason when accepting or rejecting a lead. If definitions require human interpretation to apply, they will be applied inconsistently, and the SLA becomes meaningless.
2. Marketing Commitments
Marketing's side of the SLA typically commits to:
- Lead volume -- A monthly or quarterly target for MQLs delivered to sales. This should be tied to pipeline coverage goals, not arbitrary round numbers.
- Lead quality -- A minimum percentage of MQLs that should convert to SAL. If marketing commits to 500 MQLs per month with a 60% SAL acceptance rate, that is 300 usable leads. Anything below that rate signals a quality problem.
- Data completeness -- Every MQL should arrive with a minimum set of enriched data fields populated. No lead should reach a rep with just an email address and a first name.
- Enrichment and context -- Beyond basic fields, marketing should deliver leads with enough context for reps to act: engagement history, content consumed, ICP fit score, and any relevant signals.
3. Sales Commitments
Sales' side of the SLA typically commits to:
- Response time -- A maximum number of hours to make first contact on an MQL. Industry benchmarks suggest that response within the first hour converts at dramatically higher rates than responses after 24 hours. Define the clock start and the clock stop.
- Follow-up cadence -- A minimum number of touches within a defined window. If a rep makes one call, gets voicemail, and marks the lead as "unresponsive," that is not a real follow-up effort.
- Disposition requirements -- Every MQL must be dispositioned with a reason code within a defined timeframe (typically 5-7 business days). Accepted, disqualified with a reason, or deferred with a timeline.
- Feedback quality -- When sales disqualifies a lead, the rejection reason must be specific enough for marketing to act on. "Bad lead" is not feedback. "Wrong persona: individual contributor, not decision-maker" is feedback that marketing can use to improve targeting.
4. Consequences and Escalation
An SLA without consequences is a suggestion. Define what happens when either side misses their commitments:
- Weekly review trigger -- If either side misses targets for two consecutive weeks, a joint review is triggered to diagnose the root cause.
- Escalation path -- Define who gets involved when issues persist. Typically: first to team leads, then to VP level, then to CRO/CMO.
- Quarterly recalibration -- SLA targets should be reviewed and adjusted quarterly based on actual performance data, market changes, and capacity shifts.
The Metrics That Matter
SLA dashboards get bloated fast. Every stakeholder wants their metric included, and before long you are tracking 30 numbers that nobody looks at. Here are the metrics that actually drive accountability and improvement.
Marketing-Side Metrics
| Metric | Formula | Benchmark | Why It Matters |
|---|---|---|---|
| MQL Volume | Count of leads meeting MQL criteria per period | Varies by segment | Pipeline input; too low means sales starves, too high often means quality drops |
| MQL-to-SAL Rate | SALs / MQLs | 50-70% | Quality indicator; below 50% signals targeting or scoring problems |
| Data Completeness | Fields populated / required fields per MQL | 95%+ | Directly impacts rep efficiency and sequence enrollment |
| Lead-to-Opportunity Rate | Opportunities created / MQLs delivered | 15-25% | End-to-end quality measure that neither side can game alone |
Sales-Side Metrics
| Metric | Formula | Benchmark | Why It Matters |
|---|---|---|---|
| Speed to First Touch | Time from MQL creation to first outreach | Under 1 hour for hot leads | Lead value degrades with every hour of delay |
| Follow-Up Completion | MQLs receiving full cadence / total MQLs | 90%+ | Catches reps who cherry-pick easy leads and ignore the rest |
| Disposition Rate | MQLs dispositioned within SLA window / total MQLs | 95%+ within 5 days | Prevents leads from going into a black hole |
| Feedback Quality | Disqualified leads with actionable reason codes / total disqualified | 100% | Powers the feedback loop that makes marketing better |
If you can only track one shared metric, make it MQL-to-Opportunity conversion rate. It captures both marketing quality and sales effort in a single number, and neither side can improve it alone. When this metric moves, the whole funnel moves with it. Use it as the north star for your SLA, and let the component metrics explain why it is moving up or down.
Enforcement Automation
SLAs only work if they are enforced automatically. Relying on managers to manually check compliance is a system that degrades the moment anyone gets busy. The GTM Engineer's job is to build the automation that makes SLA violations visible and impossible to ignore.
Speed-to-Lead Enforcement
Configure your CRM or routing system to start a timer when an MQL is created. If the lead has not been contacted within the SLA window, trigger an automated escalation:
Disposition Enforcement
Build a scheduled automation that scans for MQLs older than your disposition SLA window that lack a status update. Send daily digest emails to reps listing their undispositioned leads, with a direct link to each record. Escalate to managers for leads that are more than double the SLA window. This simple workflow eliminates the "lead graveyard" problem where hundreds of MQLs sit unworked because reps forgot about them or deprioritized them.
Feedback Loop Enforcement
When a rep marks a lead as disqualified, require a structured reason code from a predefined list. Make the reason code field mandatory in your CRM so the record cannot be saved without it. Aggregate these reason codes weekly and surface them in the joint marketing-sales dashboard. If "wrong persona" is the top disqualification reason three weeks in a row, marketing has a specific, data-backed signal to adjust their persona targeting.
Building Dashboards Both Teams Trust
The SLA dashboard is the single source of truth for alignment. If sales and marketing are looking at different numbers, or if the numbers are easy to dispute, the SLA collapses into another round of "your data is wrong" arguments.
Dashboard Design Principles
- Use the same data source. Both teams should be looking at CRM data, not marketing's HubSpot reports versus sales' Salesforce dashboards. Unify reporting on one system or build a reporting layer that pulls from both and reconciles automatically.
- Show trends, not just snapshots. A single week's SLA performance is noisy. Show 8-12 week trendlines so both teams can see whether things are improving, degrading, or stable. Trends are harder to argue with than individual data points.
- Separate controllable from uncontrollable. If lead volume drops because of a seasonal dip, that is market context, not a marketing failure. Include external benchmarks or year-over-year comparisons where possible to distinguish performance from environment.
- Make it visible. Put the SLA dashboard on a TV in the office. Send a weekly Slack summary with the key metrics and trend arrows. The dashboard only drives behavior if people actually see it. Build reporting pipelines that push insights rather than waiting for people to pull them.
Schedule a 15-minute weekly standup where sales and marketing leadership review the SLA dashboard together. No agenda beyond the numbers. This is not a strategy meeting. It is a performance check. If the numbers are green, move on. If something is red, assign an owner and a deadline. Keep the meeting short enough that people actually show up, and consistent enough that it becomes a habit.
Closing the Feedback Loop
The SLA is not a static document. It is a system that should get smarter over time. The mechanism for improvement is the feedback loop: structured data that flows from sales back to marketing about lead quality, and from marketing back to sales about what context and content is working.
Sales-to-Marketing Feedback
Every disqualified lead should carry a reason code that marketing can aggregate and act on. Beyond reason codes, build a quarterly feedback session where sales shares the patterns they are seeing:
- Which lead sources produce the best conversations?
- What objections are coming up most frequently?
- Which personas convert and which consistently stall?
- What qualification signals correlate with deals that actually close?
Marketing-to-Sales Feedback
Marketing should surface data that helps sales improve their approach:
- Which content assets a lead engaged with before converting, so reps can reference the right topics.
- Which intent signals are firing on the account, so reps know what the prospect is researching.
- Which campaigns are driving the highest-quality leads, so reps can prioritize appropriately.
- Which messaging themes test best in campaigns, so reps can mirror them in their outreach.
Continuous SLA Calibration
Review and update the SLA quarterly based on empirical data. If the MQL-to-SAL rate has been above 80% for three months, either raise the volume target or tighten the quality criteria. If speed-to-lead is consistently met, consider tightening the window. SLAs that never change become irrelevant because the team outgrows them or the market shifts around them.
FAQ
For inbound demo requests and hand-raises, the target should be under 5 minutes for automated acknowledgment and under 1 hour for human outreach. For MQLs from content engagement or scoring thresholds, 2-4 hours is more realistic and still effective. The key principle is that every lead has a "freshness window" and the SLA should fall inside it. Research shows that responding within 5 minutes is 21x more effective than responding after 30 minutes.
Yes. SDRs typically own MQL follow-up and should have speed-to-lead and follow-up cadence SLAs. AEs own SAL-to-SQL conversion and should have SLAs around discovery scheduling, opportunity creation timelines, and deal progression. The metrics differ because the workflows differ. Separate SLAs for each role create more precise accountability than a one-size-fits-all agreement.
Build overflow logic into your routing system. When inbound volume exceeds a rep's capacity threshold (e.g., more than 15 MQLs per day), excess leads auto-route to a backup pool or get prioritized by lead score. The SLA should have a documented "surge protocol" that adjusts expectations during events, product launches, or campaign spikes. The alternative is reps cutting corners on follow-up quality, which is worse than slightly delayed response on lower-priority leads.
Start with data, not opinions. Pull 90 days of lead data and analyze which leads converted to opportunities and which did not. Identify the attributes that correlate with conversion and build your MQL definition around those empirical patterns. When definitions are data-driven, there is less room for argument. If disputes persist, have the CRO or CEO arbitrate, with the understanding that the definitions will be reviewed after the next quarter's data is in.
What Changes at Scale
SLAs between one marketing team and one sales team are manageable. SLAs across multiple segments, geographies, product lines, and sales motions are a coordination challenge that spreadsheets and Slack reminders cannot handle. When you have enterprise SDRs with different follow-up expectations than SMB SDRs, and regional marketing teams generating leads with different qualification criteria, the number of SLA permutations explodes.
The underlying problem is that each tool in the stack holds a piece of the picture. The marketing automation platform knows engagement history. The CRM knows deal stage and ownership. The enrichment tools know data quality. The sequencer knows follow-up activity. But no single system has the full context needed to evaluate whether the SLA is being met end-to-end. Enforcement automation becomes a web of Zapier connections and custom reports that nobody fully understands and everyone is afraid to touch.
This is where Octave changes the equation. Octave is an AI platform that automates and optimizes your outbound playbook, connecting to your existing GTM stack to operationalize the handoffs that SLAs govern. Its Qualify Agent evaluates leads against configurable qualifying questions and returns scores with reasoning, ensuring that what marketing passes to sales is pre-validated. Its Sequence Agent generates personalized email sequences per lead, auto-selecting the best playbook, so the time between lead acceptance and first outreach shrinks to near-zero. For teams operating across multiple segments and sales motions, Octave eliminates the manual steps that make SLA compliance practically impossible at scale.
Conclusion
Sales-marketing SLAs are not about assigning blame. They are about creating a shared operating system that both teams can trust. The definitions remove ambiguity. The commitments create accountability. The automation removes the human failure modes that let leads slip through cracks. And the feedback loop ensures the system gets better quarter over quarter.
Build your SLA in layers. Start with shared definitions and lead stage criteria. Layer on the specific commitments each team makes. Build the enforcement automation that makes compliance automatic, not optional. Create dashboards that show real-time SLA performance with trendlines that tell the story over time. And close the loop by turning disqualification reasons and conversion data into targeting improvements. The teams that run this system consistently are the ones that stop arguing about leads and start generating pipeline together.