60-Min Sales Training: Champion Development

What champion development actually is and why one hour is enough

Champion development is the discipline of finding, testing, arming, and backing up the internal person who sells for you when you are not on the call. Most sales teams treat this as a personality trait — "Pat likes us" — when it is closer to a qualification stage with pass/fail criteria. The standard working definition, popularized by John McMahon in *The Qualified Sales Leader*, is a person with power and influence who is both willing and able to sell on your behalf in your absence. Both halves matter independently. Willing-but-powerless is a coach. Powerful-but-unwilling is a spectator. You need the intersection, and you need evidence, not vibes.

The reason a 60-minute block is the right container is that champion development fails on execution, not on comprehension. Reps already know they should multi-thread. What they lack is the exact sentence to say when a possessive champion says "just keep working with me, I'll handle the others." That is a muscle problem, and muscles are built with reps, not slides. A 60-minute session that spends 15 minutes on framework and 30 minutes on script memorization plus role-play produces behavior change by Wednesday. A 90-minute session with 60 minutes of theory produces notes nobody reopens.

The business case for spending the hour is straightforward even without leaning on any single vendor statistic. Deals that touch one contact are hostage to that contact's calendar, tenure, internal credibility, and mood. In enterprise SaaS, the average buying group has expanded well past a single decision-maker — Gartner's widely cited B2B buying research puts a typical complex purchase in the range of six to ten decision-makers, each arriving with independently gathered information. Every one of those people is a place your deal can die silently. Conversation-intelligence vendors including Gong have published analyses across large opportunity datasets showing multi-threaded deals win at meaningfully higher rates than single-threaded ones; treat the direction as reliable and the exact multiplier as vendor-specific, because the number moves with deal size, segment, and how the vendor defines a "thread."

There is also a churn argument that most training decks omit. A champion who leaves takes institutional memory with them. Median tenure for a B2B SaaS account executive sits somewhere between 18 months and three years depending on the survey, and buyer-side operations leaders churn on a similar clock. If your renewal depends on one person and that person's LinkedIn changes, you are renegotiating from zero with someone who has no history with you. Champion development done properly is therefore a retention program disguised as a sales skill.

The last framing worth putting on the whiteboard: champion development is not manipulation and it is not "using" someone. A real champion has a self-interested reason to want your outcome — a metric they own, a project they staked their name on, a promotion path. Your job in the hour is to teach reps to find and name that reason out loud. When a rep can articulate what their champion personally wins if the deal closes, the relationship is durable. When they cannot, they have a friendly contact and a forecast problem.

The 60-minute run of show, minute by minute

Print the agenda and hold to it. The single most common failure of this session is that the framework block eats the role-play block, and role-play is where the value is. Assign a timekeeper who is not the manager.

Minutes 0-5 — Setup. Open with the slide already up so no one watches you connect a cable. Manager states the exit criteria in one breath: by the end of the hour, every rep names one live single-threaded opportunity, has a written test for that champion, and has two next-thread targets with intro language drafted. Then run a 30-second-each lap around the room on one question: "Name a deal you lost in the last 90 days because your champion went dark, got reorged, or could not actually sell internally." Do not solve anything. You are surfacing the pattern so the next 55 minutes have a hook. On most teams you will hear the same story three or four times, and that repetition does more persuading than any statistic.

Minutes 5-20 — Framework teach. One definition, three tests, one data slide. Write the McMahon definition verbatim on the board and declare it the only definition the team uses from now on. Kill the synonyms explicitly: a coach is not a champion, a friend is not a champion, a user who loved the demo is not a champion. Then teach the three tests (detailed in the next section) and stop. Resist every temptation to add MEDDPICC in full, or org-chart theory, or a persona deck. Scope discipline here is what buys you the role-play time.

Minutes 20-35 — Verbatim scripts. Hand out a physical script card. Read each script out loud as a group — the manager reads it once, then two reps read it. No debate in this block; debate belongs in role-play. The goal is that reps have heard the words in their own voice before they say them to a buyer. Five scripts is the ceiling. More than that and nothing gets memorized.

Minutes 35-50 — Role-plays. Three rounds of five minutes, pairs rotating, with a third person observing against a printed rubric when headcount allows. If you have an odd number, the manager observes. Scoring is 1-5 on three behaviors per round, and the observer reads the scores out loud before rotating. Public scoring is uncomfortable and it is the reason the drill works.

Minutes 50-55 — Pitfalls. Five named failure modes, one fix each, delivered fast. This block exists to inoculate against the specific ways reps will water the scripts down over the next 72 hours.

Minutes 55-60 — Action items and the week's drill. Three dated deliverables in every notebook and one team-level accountability metric. End on the manager's closing line so it lands as the last thing anyone hears.

The three tests reps run on every suspected champion

The framework block teaches exactly three gates. Each one is a question a rep can answer with evidence, not opinion, and each one has a specific remedy when the answer is no.

Test one: power. Does this person have political capital and a path to the economic buyer? The diagnostic is not their title. It is whether they can describe how budget actually gets approved at their company and whether they have personally been part of a purchase at your price point before. Ask directly: "Walk me through how the last tool in this category got bought here — who signed, who pushed back, how long did it take?" A person with capital narrates that story fluently in ninety seconds. A person without it gives you a shrug and a guess. Failing this test does not end the relationship; it demotes the person to coach and triggers immediate multi-threading.

Test two: influence. Will the economic buyer take their call? The cleanest evidence is response latency. If your contact emails the EB, do they hear back inside a day? You can test this without being rude by asking your contact to loop the EB on something small and low-stakes — a date confirmation, a scope question — and watching what happens. Loud is not the same as influential. In practice the most responsive person in a buying group is often the most available person, and availability and political capital are inversely correlated more often than reps want to believe.

Test three: give-to-get. Will they do something that costs them something? This is the test that separates the framework from generic relationship advice. Asking a champion to accept a meeting costs them nothing. Asking them to forward a business-case email to their CFO with you copied on the reply costs them credibility if the case is weak. That is precisely why it works as a test. A real champion says yes within roughly 48 hours, or comes back with a counter-proposal ("I'd rather bring it up in our Thursday staff meeting — can you get me a one-pager by Wednesday?"). A coach hedges, defers, or goes quiet. Silence is a no, and treating silence as a maybe is how deals sit in commit for two quarters.

The output of the three tests is a status you write down: tested champion, coach, or unknown. Put it in CRM as a field — a simple picklist plus a date-tested field is enough. The reason to persist it in the system rather than in a rep's head is that it makes the pipeline review question mechanical. Instead of "how's the Acme deal feeling," the manager asks "when was the champion last tested and what did they do for you?" A stale test date is itself a risk signal.

One important nuance: passing all three tests does not end multi-threading. It reduces urgency, not the requirement. Even a perfect champion is one reorg away from irrelevant. The rule reps should leave with is that a tested champion plus one additional live thread is the floor for any deal you would put in commit.

The five verbatim scripts and why each word is load-bearing

Scripts get diluted the moment a rep paraphrases them, so teach them verbatim and explain the mechanism behind the phrasing.

Script A — the give-to-get test. "Pat, I appreciate everything you've done so far. To make sure I'm setting you up well 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 load-bearing element is the last sentence, which gives an explicit permission to decline. Without it, the buyer's cheapest response is a soft yes they never act on. With it, a no is socially available, and a no you hear in week two is worth more than a maybe you chase until week twenty. The other load-bearing element is what happens after the question: nothing. The rep stops talking. Six seconds of silence feels endless and is where the actual answer lives.

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 security or finance gets surprised at the end. Can you introduce me to Jamie in IT and Sam in Finance now, while there's time to build context, so they're not seeing our name for the first time in legal? I'll write the intro for you." Two mechanisms: the framing positions multi-threading as protecting the champion's reputation rather than going around them, and the closing offer reduces their effort to forwarding a paragraph. Champions are busy and under-resourced. "I'll write the intro for you" converts a task into a click, and it is the single highest-leverage phrase in the whole card.

Script C — the arming email. This is the email the champion forwards, written by you, in three short paragraphs. Paragraph one: the pain in their language plus a quantified cost. Paragraph two: one sentence on how your approach differs from the incumbent or the do-nothing option, plus two or three comparable companies and the outcome they saw. Paragraph three: a specific ask for a 30-minute working session with named attendees and a proposed date, with a one-page agenda attached. The rule to teach: champions cannot forward a 40-slide deck internally. Nobody forwards a deck. They forward a short email with one attachment. If your enablement team has only produced decks, the rep's job is to compress one into this shape before the meeting.

Script D — re-engaging a dark champion. "Pat, no response is feedback too. If priorities have shifted on your side, just tell me and I'll respect it. If something changed internally, I'd rather hear it directly so I can either help or get out of your way." This forces a binary and removes the guilt that keeps buyers silent. Ban the alternatives out loud in the session: "just checking in," "circling back," and "wanted to bump this to the top of your inbox" all signal that the rep wants something and has nothing to offer. The give-them-an-out pattern is well established in modern outbound coaching — Josh Braun's writing on making it easy to say no is the common reference — and it applies cleanly to a stalled champion.

Script E — the first economic-buyer meeting. "Thanks for the 20 minutes. Pat asked me to walk you through what we found, but before I do, 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?" You are testing authority and timeline in the first minute rather than the last week. Force Management's coaching language for this is going up early — meeting the economic buyer to qualify, not to ask for a signature. If the EB cannot articulate a bar, you have learned the deal has no internal sponsor above your champion, which is exactly the thing you wanted to learn in month one.

Cost, cadence, and what the numbers actually look like

The direct cost of this session is loaded labor time. For a team of eight reps plus a manager, one hour is nine person-hours. Using a fully loaded cost of roughly $70-$110 per hour for a mid-market AE — a reasonable range once you gross up base salary, benefits, and overhead on a $60K-$90K base — the session costs somewhere in the $600-$1,000 band, plus manager prep. Prep is real: budget 60-90 minutes the first time to build the script card, the observer rubric, and the CRM field, and about 15 minutes for each repeat. Printing script cards costs nothing worth measuring.

Cadence matters more than polish. Run the full 60-minute version once, then convert it into a 15-minute Friday standup that asks one question — "what did your champion do for you this week that was uncomfortable for them?" — every week thereafter. Re-run the full hour quarterly, and always within two weeks of onboarding a new hire. Skill decay on verbatim scripts is fast; without a weekly touch, most teams revert to old phrasing inside a month.

Timeline to visible pipeline effect runs on the length of your sales cycle, and managers who expect faster are setting themselves up to abandon the program early. Expect leading indicators in one to two weeks: threads added per opportunity, champion-tested fields populated, EB meetings booked. Expect lagging indicators — stage conversion, win rate, cycle length — no sooner than one full sales cycle, which in mid-market SaaS commonly runs 30-90 days and in enterprise 6-12 months. If your average cycle is two quarters, do not evaluate win-rate impact at week six.

Measurement design is where most programs get sloppy. Pick three metrics and instrument them before the session, not after:

• Contacts engaged per open opportunity. Count distinct people who have participated in a two-way interaction, not everyone CC'd on a thread. Baseline it the week before training so you have a comparison.
• Percent of commit-stage deals with a dated champion test. This is a hygiene metric and it should approach 100% within a month. If it stalls at 40%, your CRM field is in the wrong place or the manager is not asking about it in reviews.
• Percent of opportunities with an economic-buyer meeting before the final third of the cycle. This catches the "going up late" failure directly.

Resist adding a fourth. Every additional metric halves the attention on the first three.

On tooling cost: none of this requires a purchase. A CRM custom field, a printed card, and a recurring calendar block are the full stack. Conversation-intelligence platforms make the coaching easier by letting managers review whether reps actually delivered Script A verbatim, and if you already own one, build a tracker for phrases like "would you be willing to." If you do not own one, do not buy one for this — observer scoring in role-play covers the same ground at a fraction of the cost.

Where teams get this wrong

Mistaking the most responsive person for the champion. Fast email replies feel like enthusiasm and often signal available calendar time, which correlates poorly with political capital. The fix is the influence test: if they cannot get the economic buyer to respond inside a day, they are a coach and should be treated as one — valuable for intelligence, insufficient for closing.

Accepting a possessive champion's request to stay single-threaded. "Just work with me, I'll handle the others" sounds like ownership and usually means the person is either protecting their internal position or is not confident enough to expose the deal to scrutiny. Strong champions want backup because their own credibility is exposed if the project stumbles. The reframe is Script B's opening: multi-threading protects them from a late-stage ambush.

Skipping the give-to-get test because the rep likes the champion. Rapport is pleasant and it is not commitment. This is the most common failure among tenured reps, who have enough relationship skill to feel confident without evidence. The managerial fix is a standing pipeline-review question with no acceptable dodge: what did your champion do for you this week that cost them something? "We had a great call" is not an answer. If the honest answer is nothing, the deal moves to commit-risk regardless of what the rep's gut says.

Sending a deck when the moment calls for an arming email. Reps forward the corporate overview because it exists and it feels substantial. Champions do not forward decks internally — the social cost of pushing 40 slides at a CFO is too high. Rewrite it as Script C every time, and keep a team folder of the three best arming emails anyone has sent so new reps have a pattern to copy.

Treating the economic buyer as a closer rather than a qualifier. Waiting until late stage to meet the EB means the first conversation with the person who controls budget is a request for signature from a stranger. Use Script E early. The information you get — their bar, their timeline, whether they have even heard of the project — is worth more in week three than in week thirty.

Running the session and never running the drill. A one-time training with no Friday check produces a spike in behavior for about eight days. The accountability metric is not decoration; it is the entire mechanism by which the hour turns into pipeline. If a manager can only protect one of the two, protect the Friday standup and shorten the training.

Choosing your next move on any given deal

The decision framework reps carry out of the room is small enough to memorize. Start from the champion's tested status and the presence of a second thread, and the right action falls out.

If the champion is untested, the next action is always Script A — you cannot plan around a person whose willingness is unknown, and the test is cheap. If they pass and you have no second thread, run Script B this week. If they pass and you already have a second thread, arm them with Script C and move on to the economic-buyer meeting. If they fail the give-to-get test, do not escalate pressure on that person; demote them to coach in CRM, use them for intelligence and org mapping, and open two new threads. If they have gone dark for more than roughly ten days despite two follow-ups, run Script D to force a binary rather than sending a third check-in.

One judgment call worth naming: when a champion fails the test, reps often want to keep pushing because switching threads feels like starting over. It rarely is. The coach you just demoted can still tell you who owns the budget, when the fiscal year turns, and which competitor already presented. Harvest that, then build elsewhere. The sunk cost is the relationship time, and that time already produced its return in intelligence.

Related questions

How do you run this session for a fully remote team?

Keep the same 60 minutes but use breakout rooms for role-play with three people each — rep, buyer, observer — and a shared scoring doc so observers type scores live. Have the manager drop into each room for one round. Cameras on for role-play only.

What if a rep has no single-threaded deal to name?

Have them name the deal with the weakest second thread instead, or pair them with a teammate's deal as the buyer for all three role-plays. Do not excuse them from the drill; the accountability metric applies to whichever opportunity they named.

Should SDRs attend champion development training?

Yes, for the framework and Script B, which teaches them to ask for referrals sideways during prospecting. Skip Scripts C and E — arming emails and economic-buyer meetings sit outside their motion and dilute the hour.

How do you coach a rep who softens the give-to-get ask?

Record or observe the actual call, play back the exact sentence they used, and have them deliver Script A verbatim three times before their next call. Softening is almost always discomfort with the silence, so drill the pause separately.

Does this framework work for renewals and expansion?

Yes, with one change: the test shifts from "will you sell us internally" to "will you defend this line item in your budget review." Same three gates, different give-to-get ask, and the tenure risk is higher because you have often single-threaded through one admin for years.

FAQ

What exactly makes someone a champion rather than a coach?

A champion has power, influence, and demonstrated willingness to act on your behalf when you are not in the room. A coach gives you information and goodwill but cannot move budget or get the economic buyer to respond. Both are useful; only one closes deals, and confusing them is the most expensive error in complex sales.

How long should the manager spend preparing this session?

Roughly 60-90 minutes the first time: build the script card, print the observer rubric, add the CRM field, and pick the opening loss question. Subsequent runs take about 15 minutes of prep. Anything beyond that usually means slides are being built that will crowd out role-play time.

Can this be run in 30 minutes instead of 60?

You can compress it, but you have to cut framework, not practice. A 30-minute version is five minutes of setup, five minutes on the three tests, ten minutes reading Scripts A and B, and ten minutes on one role-play. Never run a version that has theory and no rehearsal — that produces notes, not behavior.

What CRM changes does this require?

Two fields on the opportunity: a champion-status picklist with tested, coach, and unknown, plus a date-last-tested field. Optionally a count of engaged contacts if your CRM does not surface that natively. Keep it to two fields; adoption falls sharply past that, and an unused field is worse than no field.

How do you keep the training from decaying after two weeks?

Convert it into one recurring question in the Friday standup and one question in every pipeline review: what did your champion do for you this week that was uncomfortable for them. The weekly repetition is what holds the behavior. Re-run the full hour quarterly and for every new hire within their first two weeks.

What is the single most important thing reps should leave with?

One sentence: a champion who has not done something costly for you is a contact, not a champion. Everything else in the session — the tests, the scripts, the role-plays — exists to turn that sentence into a specific action they can take before Friday.

Sources

• https://www.gong.io/blog/ — Gong Labs research posts on multi-threading, buying-group size, and deal outcomes across large opportunity datasets.
• https://www.gartner.com/en/sales/insights/b2b-buying-journey — Gartner research on B2B buying groups and the number of decision-makers in complex purchases.
• https://www.forcemanagement.com/blog — Force Management's coaching material on champions, economic buyers, and qualifying up early.
• https://revenue-builders.simplecast.com/ — Revenue Builders podcast with John Kaplan and John McMahon, including episodes on champion development and testing.
• https://meddicc.com/ — MEDDICC resources on the Champion element, including how to identify and test one.
• https://www.saleshacker.com/ — Sales Hacker articles on multi-threading, stakeholder mapping, and enterprise deal strategy.
• https://joshbraun.com/blog/ — Josh Braun on giving buyers permission to say no, applicable to re-engaging a silent champion.
• https://hbr.org/2017/03/the-new-sales-imperative — Harvard Business Review on the complexity of modern B2B buying groups and consensus purchases.
• https://www.bridgegroupinc.com/research — The Bridge Group's SaaS AE metrics research, including tenure, ramp, and quota-attainment benchmarks.

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)