B2B Sales: The 11 Conversations That Decide a Six-Figure Deal

A SaaS company we worked with hadbuilt sophisticated deal forecasting. Pipeline weighting by stage,multi-threading scores, engagement signals from email and meetings — allflowing into a forecast the leadership team reviewed weekly. The forecastaccuracy was middling. Deals that looked like sure things slipped or died withno warning. Deals that looked weak occasionally came in. Sales leadership hadgrown skeptical of their own forecast.

We analyzed twelve months of their closeddeals — won and lost — against the conversation history of each. A patternemerged that the pipeline data didn’t show. Every six-figure deal that closedhad between nine and thirteen specific conversations that determined theoutcome. Some were obvious — the demo, the proposal review. Most weren’t —early-discovery conversations with secondary contacts, an objection-handlingcall that turned a doubting stakeholder, a champion-development conversationthat hadn’t been logged. The deals that died had usually missed three or fourof these decisive conversations entirely. The pipeline stage said they wereactive. The conversations said they were already over.

The lesson wasn’t that the company neededmore conversations. It was that the conversations that decided deals weren’tthe same as the activities the pipeline tracked. A measurement system built onstage progression and engagement signals was systematically missing the momentswhere deals were actually being won or lost.

The 11-ConversationPattern

Enterprise B2B deals consistently turn on a similar small set ofconversations, though the timing and order vary.

The deals we’ve analyzed typically include: - Initial discoverywith the primary contact, establishing fit and pain - Multi-stakeholderdiscovery uncovering the full buying group - Champion development —a conversation where the primary contact decides whether to advocate - Technicalvalidation with implementation stakeholders - Objection-handling forthe most consequential concern - Pricing framing before formal proposal- Decision-criteria alignment — making explicit what will drive thechoice - Executive sponsorship at decision-maker level - Competitivedifferentiation when an alternative is in play - Risk-and-implementationconversation addressing change concerns - Decision and next-step framingthat secures movement

Each of these is decisive in its own right. Missing one is usuallyrecoverable. Missing two or three is usually fatal. The pattern is consistentenough across deals that it operates as a checklist for deal health that mostpipelines don’t capture.

What the PipelineData Misses

Standard pipeline tracking misses these moments for predictablereasons.

Activity logging captures surface, not substance. A call gets logged with duration and contact name. Whether the callwas substantive champion development or a polite check-in is invisible to thelog. Two deals with identical activity logs can be in completely differentstates.

Stage progression tracks seller actions, not buyer movements. When a deal moves from “discovery” to “proposal,” it reflects theseller having sent a proposal — not the buyer having reached adecision-readiness state. The two often diverge substantially.

The conversations that matter most aren’t always with the primarycontact. Champion development happens with theprimary contact. Decision-criteria alignment often happens with a procurementcontact. Executive sponsorship requires a different conversation entirely.Pipeline systems often track the primary contact and miss the others.

Engagement signals from email and meetings don’t predictconversation quality. Two meetings get scheduled.One produces substantive movement; the other doesn’t. The engagement signallooks identical. The deal trajectory diverges.

What ConversationAnalysis Adds

Conversation analyticsapplied to deal cycles can identify which of the 11 conversation types have actuallyoccurred, with whom, and to what depth.

This shifts deal review from “what stage is this deal in” to “whichdecisive conversations have happened and which haven’t.” A deal in proposalstage that’s missed champion development and decision-criteria alignment isn’ta healthy deal. A deal in discovery stage that’s already had executivesponsorship and clear champion commitment is further along than its stagesuggests.

The forecast accuracy improvement that comes from this reframe issubstantial. Deals that look healthy on activity but missed key conversationsget flagged as at-risk. Deals that look weak on activity but had decisiveconversations get marked as more likely to close. The forecast startsreflecting deal substance rather than deal motion.

The Coaching Implication

The same data that improves forecasting improves rep development.When you can see that a rep consistently misses the decision-criteria alignmentconversation, the coaching is specific. When you can see that another rep doesdiscovery brilliantly but loses deals at executive sponsorship, the developmentpath is clear.

This is different from generic methodology training. It’s targetingthe specific conversation type each rep struggles with, with real examples fromtheir own pipeline, against a known pattern of what decides deals.

Five Things You Can Do This Week

1. Audit your last 10 closed-wondeals for the 11-conversation pattern. How many ofthe decisive conversations actually happened? The pattern will be moreconsistent than expected.

2. Audit your last 10 closed-lostdeals for the same pattern. The missingconversations will be specific and informative.

3. Identify the conversation type yourteam most often misses. It’s usually one specifictype. That’s your highest-leverage coaching priority.

4. Add conversation-completioncriteria to your stage exit definitions. A dealdoesn’t exit discovery without discovery, multi-stakeholder discovery, andchampion development. Make the gates real.

5. Stop forecasting on stage alone. Augment the stage signal with which decisive conversations haveactually occurred. The forecast accuracy will improve materially within aquarter.

The six-figure deal isn’t decided in thedemo or the proposal. It’s decided across a small number of specificconversations, and most pipeline systems track the wrong things to know whetherthose conversations have happened. The deals that slip without warning aren’tslipping without warning — the warning was in the conversations that didn’thappen. You just weren’t measuring for them.

Client
Burnice Ondricka

The AI terminology chaos is real. Your "divide and conquer" framework is the clarity we needed.

IconIconIcon
Client
Heanri Dokanai

Finally, a clear way to cut through the AI hype. It's not about the name, but the problem it solves.

IconIconIcon
Arrow
Previous
Next
Arrow