Lead Lifecycle SLA Framework

Design Principles That Actually Hold

Before we get into the mechanics, I want to lay out the principles behind this framework. Skip this section and you’ll implement the tactics without understanding why they’re designed the way they are — and when reality diverges from the plan, you’ll make the wrong tradeoffs.

Principle 1: Definitions before SLAs. Always.

You cannot set a meaningful response time SLA for an MQL if Marketing and Sales don’t agree on what an MQL actually is. This sounds obvious. It almost never is in practice. I’ve sat in rooms where a CMO says “we generate 500 MQLs a month” and a VP of Sales says “we see maybe 80 that are worth a call.” Both are telling the truth. Both are using the word MQL. The gap between 500 and 80 is where your pipeline silently bleeds out every single week.

This framework starts with definitions. Every stage has a crisp, documented description with specific, measurable entry criteria. Those definitions need sign-off from Marketing, SDR leadership, and Sales leadership together — not just RevOps writing something down and calling it done. If it takes three sessions, do three sessions. The downstream time savings are enormous.

Principle 2: SLAs are bilateral — not obligations imposed on one team by another.

The most common SLA mistake is treating it as something one team imposes on another. Marketing creates the MQL and hands it over with a 5-minute response SLA attached. SDRs resent it because half the leads are missing phone numbers. Marketing says SDRs aren’t working hard enough. Round and round, nobody wins, and deals quietly die in the friction between the two teams.

Every SLA in this framework runs in both directions. If Marketing holds SDRs to a 5-minute response window, Marketing has a matching obligation: the lead meets the agreed definition, is properly enriched, and lands with the right SDR. If Marketing fails their half, the SDR’s clock doesn’t start. This one structural change — making SLAs bilateral — shifts the dynamic from policing to genuine partnership.

Principle 3: If it can’t be automated, it won’t be enforced consistently.

An SLA that lives only in a spreadsheet and requires a human to manually check compliance will be enforced when someone is angry and ignored when everyone is busy — which is most of the time. Every SLA in this framework is designed to be tracked in your CRM using timestamp fields, automated alerts, and reportable dashboards. If your tooling can’t support a particular SLA, either simplify the SLA or fix the tooling. Don’t let infrastructure gaps make your process invisible.

Principle 4: Escalation is a designed feature, not evidence of failure.

One of the most damaging cultural patterns in revenue orgs is treating escalation as embarrassing — proof that something went wrong on someone’s team. The result is predictable: people stop escalating, problems fester, deals die quietly, and by the time leadership notices the pipeline gap, the causes are months old. In this framework, escalation is designed in from the start. When something escalates, it means the system is working exactly as intended.

Principle 5: Review quarterly. Adjust without ego.

Your first version of this framework will be wrong in at least three important ways. Your MQL volume will be different than expected. Some response window will turn out to be unrealistic given how you’re actually staffed. One stage definition will prove ambiguous when a real edge case hits it. Build the framework, run it for 90 days, look at the data honestly, and adjust. A framework that’s gone through three quarterly iterations is worth ten times one that’s theoretically perfect but untested.

The Lead Lifecycle Map

Before we put SLAs on anything, we need a shared map of the territory. This is the full lifecycle — every stage, every handoff, and which team carries the ball at each point. If your team can’t agree on this diagram, you have a bigger problem than SLAs and this is where you start fixing it.

Stage definitions at a glance

Inquiry to MQL

This is Marketing’s domain entirely. The SLA here isn’t really about response time — it’s about quality and consistency. Specifically: are you applying your MQL definition uniformly, and are leads being qualified and routed without sitting in limbo?

What actually makes a good MQL definition?

An MQL is a lead Marketing believes is worth handing to an SDR. That belief needs to be grounded in explicit, documented criteria — not gut feel, not a webinar registration in isolation, not someone who opened three emails and happens to work at a big company. The bar matters enormously. Set it too low and you flood your SDR team with garbage, eroding the trust that the whole system depends on. Set it too high and you starve the pipeline while perfectly good leads sit in nurture indefinitely.

The right threshold is one where, if a capable SDR calls that lead, there is a 20–35% probability of converting them to an SQL. If your MQL-to-SQL rate is below 15%, your definition is too loose — you’re promoting noise. If it’s consistently above 50%, you’re leaving real volume on the table by being overly conservative with the gate.

MQL Entry Criteria — Every Box Must Be Checked

Intent Tier Definitions

Marketing’s SLA Commitments (Inquiry to MQL)

SAL Rejection Taxonomy — Required Reason Codes

MQL to SAL — Marketing to SDR

This is the most consequential handoff in your entire revenue process. The research on speed-to-lead has been replicated so many times it is no longer debatable: the probability of reaching a lead drops by roughly 80% if you wait more than 5 minutes versus calling immediately. That is not a marginal difference. It is the difference between a real conversation and a voicemail nobody listens to.

When someone fills out a demo request, they are often in active comparison mode — your product open in one tab, two competitors in others. The rep who calls first does not just get a shot at the deal. They get to set the evaluation frame before anyone else has spoken. That is a structural advantage available to any team willing to move fast enough to capture it.

SDR Response SLA Tiers

SAL Acceptance — what it actually means

An MQL becomes an SAL the moment an SDR formally accepts it for outreach. Acceptance is not passive. It is a deliberate decision that starts the qualification clock and commits the SDR to working the lead properly. Many teams skip this step entirely. Don’t. SAL acceptance is the moment of committed accountability, and without it your pipeline data is guesswork dressed up as reporting.

The SDR Outreach Cadence

Different prospects respond to different channels. Some pick up the phone; others only reply to email; a few respond to LinkedIn who would ignore a call entirely. A good cadence covers all three channels with messaging that genuinely varies — not the same pitch delivered seven times through different pipes.

SAL to SQL — SDR Qualification

The SAL-to-SQL conversion is where SDRs do the real work. Getting someone on the phone is table stakes. What matters is what happens on that call — specifically whether the SDR can run structured enough discovery to determine if this person actually deserves time with a quota-carrying AE.

The stakes cut both ways. Promote a weak SQL and you waste an AE’s time and chip away at the trust the SDR-to-AE relationship depends on. Hold back a lead that’s clearly ready to buy and you lose momentum, possibly to a competitor who moved faster. Threading this needle correctly is the real SDR skill, and it requires absolute clarity on what “qualified” actually means in your specific org.

SQL Qualification — MEDDPIC Lite

We use a simplified version of MEDDPIC for SDR qualification — and the key word is simplified. SDRs are not AEs. We are not asking them to run a 45-minute enterprise discovery on a 15-minute intro call. We are asking them to establish a minimum threshold that justifies putting an AE’s calendar at risk.

The Three Hard SQL Gates — All Must Be True

• Confirmed need: The prospect has articulated a specific problem your solution addresses. Not vague curiosity. Not “our VP mentioned you.” A real, stated challenge with enough detail that the SDR can write it clearly in the handoff briefing doc.
• Confirmed timeline: The prospect expects to make a decision or begin implementation within 12 months. Longer than that and they go to long-term nurture. This keeps your pipeline realistic and keeps AE capacity focused on deals that can actually close.
• Meeting booked: A discovery call with an AE is on the calendar with a confirmed date, time, and acknowledgment from the prospect. Not “they seemed interested.” Not “I’ll follow up to schedule.” A booked meeting. This is the hardest gate to enforce and the most important one in the entire framework.

SAL-to-SQL SLA Requirements

SQL to Opportunity — SDR to AE

The SDR-to-AE handoff is where well-run revenue orgs separate from everyone else. A bungled transition here is demoralizing for the SDR who did the qualifying work, potentially fatal for the deal, and deeply frustrating for a prospect who was just ready to have a real conversation.

The Warm Handoff Protocol

Every SQL handoff needs to be warm — not a CRM notification or a forwarded email. A deliberate, structured transition where the SDR introduces the AE in a way that preserves relationship momentum and signals to the prospect that your team is organized. Prospects notice when reps haven’t talked to each other. It plants a seed of doubt early in the process that is very hard to uproot later.

AE Response SLA

AEs have obligations here that are as binding as SDR response times. An AE who sits on a hot SQL is not just being inefficient — they are burning the SDR’s qualifying work, cooling the prospect’s momentum, and quietly teaching their SDR team that lead quality does not matter. Leadership must be willing to hold AEs accountable with the same seriousness they hold SDRs. If they are not, the framework breaks at exactly this point.

AE Rejection Taxonomy

Opportunity Stage SLAs

Once a deal hits pipeline, most teams think the SLA work is done. It is not. Pipeline hygiene is chronically under-managed in most B2B sales orgs. Deals sit in Stage 2 for two months with “waiting to hear back” in the notes. Close dates get pushed with a comment about shifted priorities. Forecast calls become creative interpretation exercises. This section is how you prevent that from becoming the norm.

Pipeline Hygiene — The Rules That Do Not Bend

• No next step, no active deal. Every open opportunity must have a logged next step with a specific date. After 7 days without one, the deal is automatically flagged as stale in the CRM. System-enforced, not manager-reminder-enforced.
• Close dates are not wishful thinking. A close date can be pushed at most twice in the same quarter without manager documentation. The third push triggers a mandatory deal review — no exceptions, no discretion, no “but this one is special.”
• Activity minimums exist for a reason. Every open opportunity needs at least one logged activity every 10 business days. An AE claiming a deal is “progressing” with no logged touchpoints in two weeks is describing hope, not pipeline. Zero-activity deals are auto-flagged.
• Stage age limits are enforced automatically. Deals exceeding their stage age cap trigger an automated manager alert for a pipeline review. This is not punitive — it is a prompt to either advance the deal or make a clear-eyed call about whether it is real.
• Champion documentation before Stage 4. No deal moves to Proposal without the champion’s name, title, and specific role in the decision documented in the opportunity record. If the AE does not know who their champion is, they do not have a real deal — they have a contact.

Swimlane Reference

Print this page. Laminate it if necessary. Put it in every new hire’s onboarding deck. Reference it in every QBR. When someone says “I thought that was their job” — and they will — this is the document that ends the conversation without anyone losing face.

Escalation Triggers & Response Protocols

Escalation is the piece most SLA frameworks are completely missing. They define what should happen. They say nothing about what happens when it does not. To be direct: an SLA without an escalation protocol is a suggestion. A well-intentioned one. Still just a suggestion.

The MQL Response Escalation Chain

This covers the full range — from the ideal (SDR responds within minutes) to the critical failure mode (48 hours with nothing logged). Every step has a named actor, a specific required action, and a clear accountability. Nothing is left to interpretation when this runs in the field.

The SQL-to-Opportunity Escalation Chain

The AE-side escalation carries a different kind of weight. When an SDR passes a qualified SQL and an AE does not engage with it, it is not just a process failure — it is a morale failure. SDRs who watch their best work disappear into an AE’s backlog eventually stop caring about qualifying leads properly. Do not let the culture get there.

Stale Opportunity Escalation Protocol

Recycling & Disqualification

Lead recycling is misunderstood constantly. Most teams treat a recycled lead as a failed lead — evidence the outreach did not work. That is exactly backwards. A properly recycled lead is future pipeline being preserved rather than abandoned. The real failure is the lead that gets quietly dropped with no formal recycling, no suppression window, no re-engagement plan — just a cold record sitting in the CRM going nowhere.

The Metrics That Actually Matter

You can design the most elegant SLA framework imaginable. If you cannot measure compliance in real time, you do not have a framework — you have a beautifully formatted document that people reference in arguments and then ignore. This section covers what to track, how to track it, and what to do when the numbers are not where they need to be.

Primary SLA Compliance Metrics

Contact Rate vs. Response Time

This is the chart every skeptic in your leadership team needs to see. The relationship between how fast you respond and whether you actually reach the prospect is dramatic and non-linear. Moving from 30 minutes to 5 minutes is not a marginal improvement — it is a categorically different outcome. Show this chart at your next QBR and watch the room go quiet.

The Review Cadence That Keeps It All Alive

Data without a structured review rhythm is just noise. Here is the meeting cadence that makes this framework work in practice rather than in theory:

Where Frameworks Break Down

After enough implementations — the ones that worked, the ones that fell apart, and the ones that started strong and quietly died by Q3 — the failure patterns become very predictable. Here are the eight that take teams down most consistently, and what to actually do about each one.

Rolling This Out Without Chaos

Implementation sequencing matters more than most people expect. Teams that try to go from zero to full SLA compliance in 30 days almost always fail — not because the framework is wrong, but because they skipped the alignment and tooling work that makes enforcement possible. Give yourself 90 days. Do it in phases. It is genuinely worth the patience.

Reference Materials

A. Complete SLA Reference Table

B. MQL Scoring Model Template

MQL Threshold: 60 points minimum. Leads below 60 stay in nurture. Leads scoring 40–59 can be surfaced for SDR manager review at their discretion — not auto-routed.

C. SDR Handoff Briefing Template

D. Glossary