Why the document alone never works
An SLA document is a set of numbers nobody agreed to out loud. A sales rep who never had a say in the "respond within 15 minutes" rule will not treat it as a rule. They will treat it as a suggestion from marketing, and suggestions from marketing lose to a ringing phone and an open Slack thread every time.
The fix is not a better document. It is a fifteen-minute conversation, run before the document exists, where sales negotiates the numbers instead of receiving them.
The alignment conversation, word for word
Book fifteen minutes with whoever owns follow-up, even if that is one person wearing four hats. Open with the cost, not the process:
"I pulled the numbers on our last 30 leads. The average time to first contact was 19 hours. Industry data says leads contacted inside 5 minutes convert at roughly 2.6x the rate of leads contacted after 24 hours. That gap is costing us pipeline every single week, and I don't think it's anyone's fault, I think it's because we never agreed on a number."
Then ask, don't tell:
"What response time do you think is actually realistic for you, given everything else on your plate?"
Whatever number they say, that is the SLA. Not because it is the best possible number, but because a rep who names their own commitment defends it. A rep handed a number from a slide deck resents it.
Close the conversation by writing down three things together: the response window, what counts as a "response" (a call attempt, not just a CRM status change), and what happens if it slips. That third one is the part everyone skips, and it is the part you need for the next section.
What to say when sales calls the leads garbage
This objection comes up in almost every one of these conversations. "I'd respond faster if these leads weren't junk" is not a rejection of the SLA, it is a data quality complaint wearing an SLA costume. Answer it as data, not defense:
"Let's actually check that. Pull the last 20 leads you marked as junk and I'll pull what triggered them. If more than a third are genuinely bad fits, I'll fix the qualification criteria this week, that's on me. If they're not, we still have a response time problem underneath the quality one."
This works because it does two things at once. It takes the objection seriously instead of arguing past it, and it sets a deadline for you to fix your side, which earns you the standing to enforce their side.
The breach script, without starting a blame war
The SLA will get missed. What determines whether it survives the first miss is whether the follow-up conversation feels like coaching or like a complaint.
When it happens once, a private message beats a public callout:
"Saw the Acme lead sat for 6 hours past our 2-hour window. Anything blocking you, or was it just a bad day? No action needed, just flagging so it doesn't become a pattern."
When it happens three times in two weeks, escalate the tone but not the audience. Still one-on-one, still specific:
"This is the third lead outside the window this month, all three from the demo-request source. I want to understand what's actually happening, is it volume, is it the source, is it something on my end feeding you bad information?"
Notice neither script assigns blame in the opening line. Both open with a fact, then a genuine question. The moment an SLA conversation opens with "you're not following the process," the rep stops listening and starts defending. Facts plus a real question keeps the door open.
The 30-day check-in that keeps it honest
Set a recurring 30-minute review, same day every month, non-negotiable on your calendar even if it feels unnecessary that month. Three questions, in this order:
- What's our actual average response time this month, and where did we land against the number we agreed on?
- Which lead source is missing the window most, and is that a volume problem or a quality problem?
- Does the number itself still make sense, or has our funnel changed enough to revisit it?
That third question matters more than founders expect. An SLA built for five leads a week breaks silently once you're at thirty, not because anyone stopped trying but because the math changed underneath the agreement. Revisiting the number on a schedule stops that silent breakage before it shows up as a quarter of missed pipeline.
What to do this week
Book the fifteen-minute alignment conversation before you write another word of process documentation. Use the opening line above almost verbatim, your own numbers instead of the example ones. Get sales to name their own response window out loud. Write down what counts as a breach and what happens next. Put the 30-day check-in on the calendar before you leave the first conversation, not after.
Frequently asked questions
What is a lead handoff SLA?
A lead handoff SLA is an agreement between marketing and sales that defines how fast a qualified lead gets a first response after handoff, what counts as a valid response, and what happens when that window is missed.
How fast should a sales team respond to a new lead?
Inbound demo requests and self-serve trial signups convert best inside 5 minutes. Enterprise or referral leads can tolerate a longer, more deliberate window, often measured in hours rather than minutes, since the buying process itself is slower.
What if sales refuses to agree to a response time?
Ask them to name a number they'd actually hit consistently, even if it's slower than you want. A realistic number a rep will honor beats an aggressive number that gets ignored within a week.
How do you handle repeated SLA breaches without damaging the relationship?
Open every breach conversation with a specific fact and a genuine question, never an accusation. Escalate frequency and tone gradually, and always pair enforcement with fixing anything on the marketing side that's contributing to the problem.
Does a lead handoff SLA still matter with a very small team?
Yes, arguably more. At a two- or three-person go-to-market team, one missed lead is a much larger percentage of your total pipeline than it would be at a fifty-person sales org, so the cost of an unspoken agreement is higher, not lower.
Most founders write the SLA document first and have the hard conversation never. Flip that order. The document is five minutes of typing once both sides have actually agreed to the number out loud, and the conversation is the only part that makes the number stick.