Cold calling is a conversation system, not a pitch script
The original SD Lab cold calling guide ran 17 pages and 10 lessons. This is that material rebuilt as a working reference: the mechanics of a call, the sequence underneath it, and how each part connects to the rest of the outbound operating system.
Recovered from original SD Lab source material · 17 pages · 10 lessons
What this guide covers
- A cold call has four core mechanics. Most teams only practise one of them.
- The underlying sequence is Curiosity → Trust → Commitment, in that order.
- Objections are handled through understanding, not through rebuttal lines.
- The goal of the call is earning the next step, not winning the conversation.
- Aim comes before activity: who you call decides how the call can go.
Where this guide came from
This started as a 17-page cold calling guide written by Tom Slocum and Wayd Davis, built out of calls actually made rather than theory. It carried 10 lessons, and it holds the early lineage of the TAB cold-calling framework used across SD Lab work since.
The guide is reproduced here as a working reference rather than a facsimile. The lessons, the mechanics and the sequence are the same; the presentation has been rebuilt so the material connects to how outbound is executed today.
The premise: a system, not a script
A script tells a rep what to say. A system tells a rep what is happening and what to do about it. Scripts break the moment a prospect goes off the expected path, which is nearly always, because there is nothing underneath them.
Treating the call as a conversation system means every part of it has a job. The opener buys attention. Relevance earns a few more seconds. Discovery finds out whether there is anything real here. The ask converts that into a next step. When something fails, you can see which part failed instead of blaming the rep.
You cannot coach a script beyond delivery. You can coach a system: because each mechanic can be reviewed, isolated and rebuilt on its own.
The four core call mechanics
The guide teaches four mechanics that make up a cold call. They are sequential in a live call, but they are practised separately.
- The opening: earning permission to keep talking, without pretending the call is expected.
- Relevance: giving the prospect a specific reason this call is about them, not about your product.
- The transition into discovery: moving from the reason for the call into a real conversation about how they operate.
- The ask: making a clear, small, specific request for the next step.
Curiosity → Trust → Commitment
Underneath the mechanics is a sequence, and it does not reorder. Curiosity comes first: the prospect has to want to know where this is going. Trust comes second: they have to believe you understand their situation before they will tell you anything true about it. Commitment comes last, and only after the first two exist.
Most failed cold calls are sequence failures. A rep asks for commitment while the prospect is still deciding whether to be curious. The ask is not wrong: it is early.
Commitment is what a conversation earns. It is not what an opener extracts.
The early TAB framework
The TAB cold-calling framework that shows up across later SD Lab work has its early form in this guide. It is the structural spine that keeps the four mechanics in order under pressure. A way for a rep to know where they are in a call and what the next move should be.
Later material develops it further. This guide is where it starts.
How the mechanics connect to the rest of the system
Cold calling is not a standalone skill. Each mechanic in this guide maps to a theme that runs through the wider SD Lab operating system.
- Aim and target clarity: the call starts before the dial, with who is on the list and why.
- Relevance: the same discipline that governs outbound messaging governs the first fifteen seconds of a call.
- Opening and transition: the two moments where most calls are actually lost.
- Listening and discovery: the conversation only becomes useful once the rep stops presenting.
- Handling objections through understanding: an objection is information about their situation, not an obstacle to talk past.
- Earning the next step: a clear, small ask that the prospect can say yes to honestly.
How to use this with a team
Do not hand this to a team as reading. Take one mechanic at a time, review real recorded calls against it, and rebuild that mechanic before moving to the next. The lessons compound in order; skipping to the ask produces the same failure the sequence warns about.
- Pick one mechanic per week and coach only that.
- Review live calls, not role-plays, wherever recordings exist.
- Ask where in the sequence the call stopped, curiosity, trust or commitment.
- Fix the earliest broken link first; later mechanics rarely repair on their own.
Related reading
Reading it is one thing. Installing it is another
The Revenue Rebuild puts these mechanics into a team's live calls, coaching cadence and pipeline system rather than leaving them on the page.