60-Min Sales Training: Champion Development

1. Setup (5 min)

Setup (5 min)

Walk in with the slide already up. Headline reads: "Single-threaded deals close at 5%. Multi-threaded deals close at 30%." That is the Gong Labs number from their 1.8M-opportunity dataset, and it is the only stat that matters this hour.

Manager opening, verbatim: *"Today is not theory. By 9:55 you will each name one deal in your pipeline that is single-threaded through one champion, you will have a written test for that champion, and you will have two next-thread targets with intro scripts ready. If you cannot do that by 9:55, that deal is at risk and we will work it together this afternoon."*

Warm-up question, go around the room, 30 seconds each: *"Name one deal you lost in the last 90 days because your champion went dark, got reorged, or could not actually sell internally."* No solutions yet — just surface the pattern. Most teams will hear the same story four times in a row. That is the hook for the next 55 minutes.

Agenda on the board:

1. Setup (5)
2. Champion Framework Teach (15)
3. Verbatim Arming + Testing Scripts (15)
4. Role-Plays (15)
5. Common Pitfalls (5)
6. Action Items + Drill (5)

2. Framework Teach (15 min)

Framework Teach (15 min)

Teach one definition and three tests. Do not let this section sprawl.

The McMahon definition, written on the whiteboard: *"A champion is a person with power and influence who is both willing AND able to sell on your behalf when you are not in the room."* From John McMahon's "The Qualified Sales Leader" — the CRO who took PTC, Ariba, BladeLogic, Geo-Tel, and BMC public and now sits on the Snowflake and MongoDB boards. This is the only definition the team uses going forward. "Coach" is not "champion." "Friend" is not "champion." "User who likes the demo" is not "champion."

The three-part test, taught as a flowchart (this is your first mermaid):

Why all three tests matter, manager scripting:

• Power test: *"Does this person actually have political capital, or are they just enthusiastic? Enthusiasm is free. Capital is scarce."*
• Influence test: *"If your champion emails the economic buyer right now, does the EB reply within 24 hours? If not, your champion is not influential — they are loud."*
• Give-to-get test: *"This is McMahon's killer. A real champion will do something uncomfortable for you — set the meeting with the CFO, share the procurement timeline, send your one-pager to their boss. If they will not give, they are not your champion."*

Then the data slide:

• Multi-threading lifts deal-over-$50K win rate by 130% (Gong Labs, 1.8M opps).
• Strategic enterprise deals have an average of 17 stakeholders involved on won deals (Gong Mega-Deal report).
• Tested champions close at 70%+. Untested "advocates" close at 25% (MEDDPICC community data, salesmethods.com).
• 77% of deals already involve multiple contacts — winners have 2x as many buyer contacts as losers.

The lesson, on the board in one line: "One champion is a single point of failure. Two tested champions plus one coach is a deal."

3. Verbatim Scripts (15 min)

Verbatim Scripts (15 min)

Hand out the script card. Read each one out loud as a team. No discussion in this block — memorization first, debate in role-plays.

Script A — The Give-to-Get Champion Test (use in next discovery call):

*"Pat, I appreciate everything you've done so far. To make sure I'm setting you up for success internally and not wasting your time, I need to ask one thing: would you be willing to forward a 90-second business-case email to your CFO this week and copy me on the reply? If that's not a fit right now, just tell me — I'd rather know now than three months in."*

The pause after this question is the entire test. A real champion answers within 48 hours with a yes or a counter-proposal. A coach goes silent or hedges. Silence is a no.

Script B — The Multi-Thread Permission Ask:

*"Pat, we both want this to go through cleanly. I've seen deals at companies your size stall when the security team or the head of finance gets surprised at the end. Can you introduce me to Jamie in IT and Sam in Finance now, while there's still time to build context, so they're not seeing our name for the first time in legal? I'll write the intro for you."*

The "I'll write the intro for you" line is non-negotiable. Champions are busy. Reducing their effort to a forwarded email is the difference between yes and "let me circle back."

Script C — The Arming Script (the email your champion forwards internally):

Subject: *"Quick context on [Vendor] before next week's review"*

Body, written for the champion to forward, three short paragraphs:

1. *"We've been evaluating [Vendor] to solve [specific pain]. Right now, [quantified problem — $X / Y hours / Z% churn] is costing us roughly [number]."*
2. *"Their approach is different from [incumbent / alternative] because [one differentiator, one sentence]. Three peer companies — [Logo 1], [Logo 2], [Logo 3] — saw [specific outcome, e.g., 22% lift in pipeline coverage] within two quarters."*
3. *"I'd like to bring [Rep name] in for a 30-minute working session with you, [EB], and Jamie from IT on [proposed date]. Agenda attached."*

The agenda attachment is the trick. A pre-built one-page agenda makes the meeting nine times more likely to happen — Gong's enterprise mega-deal data on "committed next step" language.

Script D — The Re-engagement Script when champion goes dark:

*"Pat, no response is feedback too. If priorities have shifted on your side, just tell me and I'll respect it. If something inside the org changed, I'd rather hear it directly so I can either help or get out of your way."*

This script forces a binary. It is borrowed from Josh Braun's "It's OK to Say No" pattern and it kills zombie deals fast.

Script E — The Economic Buyer First-Meeting Opener:

*"[EB name], thanks for the 20 minutes. Pat asked me to walk you through what we found, but before I do that I want to confirm: if everything I show you lines up with what Pat described, what would need to be true for you to move forward this quarter? I'd rather know your bar now than guess at it."*

You are testing the EB's authority and timeline in the first 60 seconds. This is the John Kaplan / Force Management "go-up-early" discipline.

4. Role-Plays (15 min)

Role-Plays (15 min)

Pair the team. Rotate every 5 minutes. Observer scores on the rubric below.

Role-Play 1 — The Give-to-Get Test (5 min). Setup: Rep has had three good calls with VP of Sales Ops at a 400-person SaaS company. No EB meeting yet. Buyer (other rep): Play warm but evasive. Say things like *"Let me think about that"* and *"Our CFO is really busy."* Rep job: Use Script A verbatim, then hold the silence. Do not rescue them. Observer rubric — score 1-5:

• Did the rep deliver the give-to-get ask without softening it?
• Did the rep stay silent for at least 6 seconds after the ask?
• Did the rep get a specific commitment (date + action) or did they accept "let me think"?

Role-Play 2 — The Multi-Thread Permission (5 min). Setup: Champion is enthusiastic but possessive. Says *"Just keep working with me, I'll handle the others."* Buyer (other rep): Push back politely twice before yielding. Rep job: Use Script B, then offer the "I'll write the intro" close. Observer rubric:

• Did the rep frame multi-threading as protecting the champion, not bypassing them?
• Did the rep offer to write the intro?
• Did the rep get two named contacts and a forwarded intro within the role-play?

Role-Play 3 — The Dark Champion (5 min). Setup: Champion has not replied in 11 days. Rep has sent two follow-ups already. Buyer: Stay dark for 30 seconds, then respond. Rep job: Use Script D in a voicemail format, then a follow-up message. Observer rubric:

• Did the rep avoid the words *"just checking in"* and *"circling back"*?
• Did the rep give the champion a clean out?
• Did the message create a binary (yes / no / not now)?

Manager closes the role-play block: *"Pick the one you scored lowest on. That is the script you drill solo for 10 minutes tomorrow morning before your first call."*

5. Common Pitfalls (5 min)

Common Pitfalls (5 min)

Pitfall 1 — Mistaking the loudest user for the champion. The person who replies to your emails fastest is usually the most available, which means they have the least political capital. Fix: Run the influence test. If they cannot get the EB to reply in 24 hours, they are a coach.

Pitfall 2 — Single-threading because the champion asked you to. A possessive champion is a red flag, not a strong champion. Strong champions want backup because they know their own credibility is on the line. Fix: Reframe multi-threading as *"protecting your reputation if this deal hits a bump."*

Pitfall 3 — Skipping the give-to-get test because the rep "likes" the champion. Reps confuse rapport with commitment. Fix: Manager asks in every pipeline review, *"What did your champion do for you this week that was uncomfortable for them?"* If the answer is nothing, the deal moves to commit-risk.

Pitfall 4 — Forwarding a deck instead of an arming email. Champions cannot forward 40-slide decks internally. They forward three-paragraph emails with one attachment. Fix: Use Script C every time.

Pitfall 5 — Treating the EB as a closer, not a qualifier. Reps wait until late-stage to meet the EB and then ask for signature. The EB has not been part of the journey. Fix: Use Script E in the first EB meeting to get the bar early. Force Management calls this "going up early."

6. Action Items + Drill (5 min)

Action Items + Drill (5 min)

Everyone leaves with three deliverables in their notebook before they walk out:

1. By end of day Monday: Name one live opportunity that is single-threaded. Write the champion's name, the EB's name (or "unknown"), and two next-thread targets with title and reason.
2. By Wednesday EOD: Send Script A (give-to-get) to that champion. Log the response — yes, no, or silence — in CRM under a new field called "champion_tested" with the date.
3. By Friday EOD: Send Script B (multi-thread permission) and either get two new threads booked or escalate the deal to the manager as commit-risk.

Accountability metric for the week: Two new threads added to one stalled deal per rep. Track it on the team Slack channel #champion-drill with a screenshot of the calendar invite or forwarded intro.

Friday's 15-minute stand-up: each rep shares the response they got, what they learned, and what they will do differently next week.

Post-meeting drill plan (second mermaid):

Manager's closing line, verbatim: *"If your champion did nothing uncomfortable for you this week, you do not have a champion. You have a contact. We work that deal together on Monday."*

Related on PULSE

• [The Champion Development Reboot — 60-Min Training](/knowledge/st204)
• [The Multi-Thread and Champion Build Reboot — 60-Min Training](/knowledge/st150)
• [The Champion Enablement Workshop — 60-Min Training](/knowledge/st0066)
• [The Champion Departure Save — 60-Min Training](/knowledge/st0033)
• [Prospecting on LinkedIn: Interactive Template for a 20-Minute Sales Session](/knowledge/st0795)
• [Sales Forecasting Accuracy: Template for a Team Meeting Focused on Data Hygiene](/knowledge/st0796)

FAQ

What is the main goal of this 60-minute sales training? The training transforms reps from single-thread feature pitchers into champion-builders. By the end, each rep creates a written champion test plan for a live opportunity and memorizes three verbatim arming scripts.

How does the training measure success or accountability? A Friday accountability metric requires each rep to add two new threads to a stalled deal. Gong-validated multi-threading can lift win rates by a significant margin on larger deals.

What tools or methods are used to validate the training’s impact? The training relies on Gong-validated multi-threading data, which shows substantial win rate improvements for deals over a certain threshold. No specific third-party stats or prices are cited.

Who is this training designed for—individual reps or teams? It’s designed for the entire sales team, turning every rep into a champion-builder. The session is structured as a 60-minute Monday training that applies to all team members.

Do reps need prior experience with multi-threading or champion development? No prior experience is required. The training provides a step-by-step framework, including written test plans and memorized scripts, so even newer reps can participate effectively.

Is this training a one-time event or part of an ongoing program? It’s presented as a single 60-minute session with a clear Friday accountability check. However, the skills and metrics are designed to be reused and reinforced in future deals.

Sources

• John McMahon, "The Qualified Sales Leader" — the foundational text on champion testing and give-to-get; chapters 4 and 7 specifically.
• Force Management — "A Closer Look at Champions" (Revenue Builders Podcast, John Kaplan + John McMahon, Episode 105).
• Force Management blog — "Developing Buyer Champions with Richard Rivera".
• Gong Labs — "How to Win Mega-Deals: The Multi-Threading Playbook" (1.8M-opportunity dataset, 130% win-rate lift).
• Gong Labs — "Data-Driven Strategies for Closing Six-Figure Deals" (average 10+ stakeholders on won $50K-$250K deals, 17 on strategic).
• MEDDICC — Andy Whyte, "MEDDICC: The Ultimate Guide to Staying One Step Ahead in the Complex Sale", 2nd edition.
• Salesmethods.com — "MEDDPICC Explained: How to Find and Develop a Champion" (70% close rate on tested champions vs. 25% on untested).
• Pavilion — CRO School curriculum on stakeholder mapping (Sam Jacobs / Kathleen Booth track).
• Bridge Group — 2026 SaaS Sales Compensation and Performance Report (multi-threading correlations with quota attainment).
• Josh Braun — "It's OK to Say No" cold outreach pattern, applied to dark-champion re-engagement.
• Spotlight.ai — "Champion vs. Economic Buyer: Why Confusing Them Kills Enterprise Deals".