When does a 'champion' actually become a champion vs a contact?

The Three Commitments That Turn a Contact Into a Champion

Every serious sales methodology — MEDDIC, MEDDPICC, Command of the Message, The Challenger Sale — converges on the same underlying idea: a champion is defined by *behavior under cost*, not by warmth. Enthusiasm is free. Commitment is expensive. The three tests below are simply three different ways of asking, "What has this person actually spent on my deal?"

1. The Named, Calendarized Commitment. The first thing a real champion produces is a date with their own name — and ideally a colleague's name — attached to it. "Let's do a pilot the week of the 15th; I'll get our data ready by Tuesday and loop in our ops lead for the kickoff" is a champion sentence. "Send us a deck and we'll circulate it" is a contact sentence. The tell is in the *grammar*: champion-track conversations sound like joint project planning ("we'll need to sort out access before then," "who owns the security review on your side?"), while evaluation conversations sound like information gathering ("what does pricing look like," "can you send references"). If a person will not put a specific date on a shared calendar with a specific success criterion written down and a readout meeting on the back end, they are still evaluating you. That is fine — but it is not championship.

2. The On-the-Record Internal Statement. MEDDIC's champion criterion is often summarized as "sells on your behalf when you're not in the room." The operational version of that is: has this person said something supportive about you, in writing or in front of an audience, where their own boss can see it? A hallway "looks great," a nod after the demo, or a private "I'm rooting for you" are all worthless as evidence because they cost the person nothing and expose them to no risk. What counts is a message in a channel their VP reads, an email thread where they type "this solves our Q3 problem, I want to pilot it," or a meeting where they advocate out loud while you're present. The reason writing matters is durability: a spoken endorsement evaporates the moment the person leaves the room or the company; a written one survives reorgs, hand-offs, and procurement's memory. If you have never *seen or been copied on* your champion advocating for you internally, your working assumption should be that it has not happened.

3. The Resource Commitment (Skin in the Game). The third test is the hardest to fake. A champion pays you — before you send an invoice — in three currencies: calendar (their team's hours blocked for a pilot or implementation), data (real, sanitized test data, which requires them to get internal approval), and political capital (spending their standing to unblock you when procurement or security stalls). A useful gut check is the fully-loaded cost of what they're spending. If someone blocks 10–15 hours of their team's time for a pilot, and that team is loaded at, say, roughly $150K/year — on the order of $75/hour fully loaded — they are quietly authorizing something like $1,000 of their department's cost on the *hypothesis* that you will win. People do not spend that on vendors they merely tolerate. The magnitude is less important than the fact of it: any real, non-trivial resource commitment is a signal that they've internally decided you're worth defending.

The rule is pass all three, or you don't have a champion. Two out of three is a strong coach with upside. One out of three is a friendly contact. Zero is a name in your CRM.

Contact → Interest → Coach → Champion → Advocate: The Full Ladder

Most reps collapse the buyer relationship into a binary — "champion or not" — and lose enormous forecasting accuracy in the process. The relationship actually moves through five distinct phases, and each one behaves differently. Naming the phase you're actually in is the single fastest way to stop lying to your own forecast.

Contact. You have an email address and a title. They receive your materials, maybe open them, maybe reply "thanks." There is no internal motion on your behalf. Most of a rep's CRM is contacts wearing the costume of opportunities.

Interest. They lean in. They request a demo, show up, ask follow-up questions, forward you an article. This feels like progress and often is — but the key diagnostic is that they are consuming information, not moving a deal. Interest is a buyer educating themselves; it is not yet a buyer spending anything. Reps routinely mistake a highly engaged, curious buyer for a champion because the conversations are pleasant and frequent. Engagement is a prerequisite for championship, not evidence of it.

Coach. This is the phase most often misread as championship, and the confusion is expensive enough to deserve its own section below. A coach gives you the internal map: who actually holds budget, who the real decision-maker is, when the procurement window closes, what the competing priority is, which VP killed the last tool like yours and why. This intelligence is genuinely valuable and you should cultivate it relentlessly. But a coach will not push. They'll tell you where the door is; they won't walk you through it or knock on your behalf. The line is: *coaches give you a map; champions walk the map with you.*

Champion. They cross the three commitments. They own a pilot, they lobby their boss or peers in writing, they unblock you when procurement drags, they return the IT security questionnaire fast because your win is now *their* win. The defining feature is risk transfer: their reputation is now visibly tied to your deal succeeding, and they behave accordingly. A champion doesn't just want you to win — they've made it personally costly for them if you lose.

Advocate. This is post-close and it's where retention and expansion revenue compound. An advocate takes peer reference calls without being begged, agrees to a public case study, and hands you names of three peers at other companies. The advocate phase is the seed of your next quarter's pipeline, which is why the best account teams treat the moment of "champion → advocate" as deliberately as they treat "coach → champion."

Two rules govern movement on this ladder. First, you cannot skip phases — a cold contact does not become a champion because you gave a great demo; they become interested. Second, phases are not permanent — a champion can slide back to coach after a reorg strips their authority, and a coach can be recruited up to champion with the right personal win. Your job is to always know which rung each key stakeholder is standing on this week.

Champion in MEDDIC / MEDDPICC: What the Methodology Actually Requires

Because "champion" gets used loosely, it helps to anchor on the definition from the methodology that made the term famous. In MEDDIC (and its extended cousin MEDDPICC), the "Ch" stands for Champion, and the framework is deliberately strict about what qualifies. A MEDDIC champion has three attributes, and all three must be present:

• Power and influence. They don't have to be the economic buyer, but they must have enough internal standing that their advocacy actually moves outcomes. A junior admin who loves your product but whom no one listens to is an enthusiast, not a champion. The champion's opinion has to *carry weight* in the rooms where decisions get made.
• A personal win. This is the part most reps skip and it's the most important. A champion fights for you because your deal getting done makes *them* look good, get promoted, hit their number, solve a problem their boss is measuring them on, or eliminate a pain they personally feel. If you cannot articulate the specific personal win your champion gets from your deal closing, you have not qualified a champion — you've qualified someone who's being polite. "Why does this person, specifically, want this to happen?" is the question that separates real champions from friendly contacts.
• They sell when you're not there. This is the behavioral test that maps directly onto the on-the-record commitment above. A MEDDIC champion actively advocates internally in your absence — in the budget meeting, in the Slack thread, in the CFO's office. If all the selling stops the moment your Zoom call ends, you don't have a champion.

MEDDPICC adds an explicit "Competition" and "Paper Process" dimension, which is relevant because a real champion helps you navigate both: they tell you honestly who else is in the deal and they walk you through the actual signature and procurement path rather than leaving you to discover the 90-day legal review the week you expected to close. The methodology also stresses testing the champion rather than assuming — a discipline covered in the next section.

The reason to lean on MEDDIC's definition rather than a looser one is that it forces a useful hardness: power *and* a personal win *and* internal selling. Drop any one of the three and the term dissolves back into "person who was nice to me."

Testing a Champion: Scripts, Signals, and the 48-Hour Rule

You do not have to guess whether someone is a champion. You can test it directly, and the best reps do so continuously rather than assuming once and coasting. Testing means asking a stakeholder to do something small that a real champion would do happily and a mere contact would dodge — then watching what actually happens.

The direct ask. The cleanest test is a plainly worded request: *"If the pilot goes well, will you champion this internally — meaning you'll set up the readout with your VP and recommend we move forward?"* Listen to the exact response. A champion answers "yes," and then — this is the tell — names the specific mechanism: "Yes, I'll get 30 minutes with Dana the week after the readout and walk her through it." A non-champion hedges: "I'll try," "I'll see what I can do," "let me feel out the room," or silence. Hedging is not a soft yes; it is a no wearing a polite outfit.

The small-favor test. Ask the person to do one concrete internal thing: forward a one-pager to their VP with a note, introduce you to the IT security lead, or get you 20 minutes with the economic buyer. A champion completes the favor within a day or two and reports back. A contact lets it sit, forgets, or "hasn't had a chance." Responsiveness to a small internal ask is one of the most reliable proxies for real internal commitment because it reveals whether they're willing to spend even a little social capital on you.

The 48-hour signal. Watch how fast friction gets cleared. When you send a security questionnaire, a mutual action plan, or a scheduling request, a real champion drives it through their organization in roughly a day or two. When those things sit for a week, the delay is information: either the person isn't a champion, or they've hit an internal blocker they haven't told you about — and either way you need to know.

The pre-mortem battery. Run these questions periodically against every stakeholder you've labeled a champion:

• *"If your boss changed tomorrow, would the new boss know who I am?"* — If no, the on-the-record test has failed; the advocacy has been invisible.
• *"In the last month, where have you talked about us internally?"* — If they can't quickly name a couple of specific rooms or threads, the internal selling isn't happening.
• *"If procurement pushes back in a few weeks, what's your move?"* — If they don't have a move, they won't fight for you when it counts.
• *"Who else on your side should I be talking to?"* — A champion introduces you to more people (they *want* you multi-threaded and safe); a gatekeeper guards access. Refusal to make introductions is a red flag that you're dealing with someone protecting their own position rather than championing your outcome.

The philosophy underneath all of these: memory of a private conversation is not evidence of public advocacy. Test for behavior that costs the person something, and update your label based on what they actually do, not on how the last call felt.

Operationalizing It: CRM Fields, Deal-Desk Gates, and the Pre-Mortem Battery

A definition you can't enforce in your system of record is a definition your team will quietly ignore under quota pressure. To make "champion" mean the same thing across every rep's forecast, encode the three commitments as required CRM fields and a deal-desk gate. For every deal above a meaningful threshold — pick a number that matches your ACV, e.g. $50K — require these fields to be populated before the opportunity can be marked as committed or advanced past the mid-funnel stage:

1. Champion name and title — free text, must be a *person*, never a department. "IT" is not a champion.
2. Named commitment date — a date field for the pilot, readout, or implementation window, ideally within the next 60 days.
3. On-the-record artifact — a link or screenshot of the actual internal advocacy (the Slack message, the email thread, the meeting notes). *The artifact itself, not your recollection of it.* If you can't attach the evidence, treat the internal advocacy as unproven.
4. Resource commitment — what they've actually spent: hours blocked, data provided, or capital expended, described concretely.
5. Last champion-check date — when you last re-tested this person. If it's more than two weeks old, the system should flag it stale, because champions decay.
6. Backup champion candidate — a second name in a different function. Requiring this field is the cheapest insurance you can buy against the single-threading time-bomb.

The enforcement rule is blunt: if any of these fields is empty, the opportunity cannot be forecast as Commit. This one gate catches a large share of would-be slipped deals before they slip, because the most common failure mode — "we had a champion, they went quiet, the deal died" — shows up first as an empty artifact field or a stale check date. Deal desks and sales managers should treat a missing champion artifact the same way they'd treat a missing signed order form: not yet real.

Beyond the fields, build the pre-mortem battery from the previous section into your pipeline reviews. Rather than asking reps "is this deal going to close?" (to which the answer is always an optimistic yes), ask "when did you last test the champion, and what did they actually do?" Force the evidence. A pipeline review that interrogates champion behavior instead of rep confidence is dramatically more accurate, because it replaces feelings with observed actions.

The Coach-vs-Champion Trap and Its Failure Modes

The most expensive mistake in this entire topic is labeling a coach a champion, because a coach *feels* exactly like a champion right up until the moment you need them to fight — and then they don't. The classic version: an ops person genuinely loves your product, gives an enthusiastic thumbs-up in the demo debrief, feeds you great intel about the committee, and then says, "I can't greenlight the budget — that's Finance." They are a coach. A champion would either *have* budget authority or actively lobby Finance alongside you in a shared meeting, spending their own credibility to do it. The heuristic bears repeating: if your "champion" has never said your product's name in front of their boss while you were watching, assume they haven't said it at all.

Even once you've correctly identified a real champion, championship can degrade. Three failure modes recur:

• The Departing Champion. They take a new job mid-cycle. The early warning signs are a sudden drop in response time, vague "I'm in transition" language, or a LinkedIn update. Because buyer tenure in many roles is measured in a small number of years, a long sales cycle carries a real, non-trivial chance of losing your champion to attrition before you close. The mitigation is to lock in a second-champion introduction early — inside the first month — so a departure doesn't zero out your standing in the account.

• The Demoted Champion. A reorg strips their authority, moves them off the project, or shifts budget away from them. Their advocacy may continue, but it no longer carries weight — they've slid from champion back down to coach without either of you announcing it. Any time you see an org-chart change, re-run the pre-mortem battery and re-confirm the champion still has the power half of the "power + personal win + internal selling" trio.

• The Burned Champion. A previous vendor failed publicly on this person's watch, and now they *under-advocate* even when they want you to win, because their political capital is depleted and they can't afford another visible failure. The mitigation is to ask directly about prior vendor experiences and to de-risk their bet — a milestone-gated pilot where they can point to concrete, early proof gives a burned champion the cover they need to advocate again.

In all three cases the technical remedy is the same: within the first month, identify a second potential champion in a different function — Finance, IT security, an end-user team lead — and run all three commitment tests on that person too. A single champion, no matter how strong, is a single point of failure, and the "we have a champion, we're set" mental model is precisely what turns a strong champion into a liability.

When the Framework Doesn't Apply: PLG, Regulated Procurement, and Single-Threading

This framework is powerful in its home context — a considered B2B purchase large enough and complex enough to *require* an internal advocate — and actively harmful outside it. Three situations break it:

1. Product-led / self-serve motions. For a low-cost, self-serve product where the user simply signs up and swipes a card, there is often no champion because there is no committee — the user *is* the buyer. Forcing the three-commitment test onto a swipe-the-card motion manufactures friction, lengthens what should be a fast cycle, and converts a frictionless purchase into an unnecessary procurement slog. In product-led motions, the right signals are product-qualified signals: seat expansion, weekly active usage, breadth of feature adoption, and how many people inside an account have organically started using the product. Champion artifacts are the wrong instrument here; usage data is the right one.

2. Regulated and public-sector procurement. In government, healthcare, financial services, and similar regulated environments, the very behaviors that signal championship in private SaaS can be disqualifying. An evaluator who publicly endorses a specific vendor before a fair procurement process closes can be removed from the panel or trigger a fairness challenge that voids the process. In these contexts, do not push for public Slack-style endorsements. Substitute compliant signals: willingness to introduce you to the contracting officer, on-time and complete responses to formal requirements, thorough engagement with your proposal, and detailed technical questions that show real intent to use the product. The underlying idea — someone spending effort on your behalf — still holds; the *permissible expression* of it is completely different, and mistaking one for the other can get your champion in real trouble and cost you the deal.

3. The single-threading time-bomb. Paradoxically, a great champion can be *worse* than a mediocre one if their strength lulls you into stopping your multi-threading. The failure isn't the champion — it's the over-reliance. Because buyer roles turn over and reorgs happen, a long cycle anchored to exactly one person is fragile in a way that isn't visible until the person vanishes. The tell that separates a safe champion from a dangerous one: a real champion helps you multi-thread. Ask them to introduce you to two peers and a VP in the first month. A genuine champion does it gladly, because they want the deal insured against their own absence. If they stall or refuse those introductions, you may not have a champion at all — you may have a gatekeeper who benefits from being your only path in. Either way, the fix is the same: always be recruiting a second and third relationship in different functions, so that no single person's departure can reset the account to zero.

FAQ

What's the difference between a champion and a coach? A coach gives you information; a champion spends resources. A coach maps the buying committee, tells you who holds budget, and warns you about the procurement timeline — genuinely valuable intelligence, but delivered privately and at no cost to them. A champion crosses three commitments: a named, calendarized action; on-the-record internal advocacy their boss can see; and real resource spend (their team's hours, data, or political capital). The blunt test: a coach won't defend you in a room you're not in, and a champion will. If all the support you're getting happens in private conversations with you and never surfaces internally, you have a coach.

How can I tell if someone is a friendly contact rather than a true champion? Ask them to do something small that costs a little internal capital — forward a one-pager to their VP with a personal note, or introduce you to the economic buyer — and watch what happens over the next day or two. A true champion completes it quickly and reports back; a friendly contact lets it sit, forgets, or "hasn't had a chance." Then ask directly whether they'll set up the readout and recommend moving forward. A champion says yes and names the specific meeting; a contact hedges with "I'll try" or "let me feel out the room."

Why does a named pilot date matter so much? Because a specific date with a named participant forces accountability and reveals commitment. "We're interested" can drift indefinitely and costs the buyer nothing. Putting a real date on a shared calendar — with success criteria written down and a readout meeting on the back end — means someone has decided to spend their team's time on the hypothesis that you'll win. It also changes the grammar of the relationship from vendor evaluation ("send us a deck") to joint project planning ("we'll need data ready by Tuesday"), which is the single clearest verbal signal that a contact has crossed into championship.

Can a champion emerge later in the sales cycle? Yes, and often the best champions are recruited rather than found. You cultivate a coach by being genuinely useful with intel and insight, then give them a reason to advocate — a personal win, a way to look good to their boss, a problem you visibly solve that they're measured on. What you can't do is *assume* someone will become a champion when the pressure hits. If a key stakeholder hasn't crossed the three commitments by the time procurement and legal engage, don't forecast the deal as if they have. Recruit deliberately, test continuously, and update the label based on behavior.

Should I still worry if I already have a strong champion? Yes — a strong single champion is a single point of failure. Buyer roles turn over, reorgs happen, and budgets move, so a long cycle anchored to exactly one person is fragile. The counterintuitive rule is that a *real* champion helps you reduce your dependence on them: they'll introduce you to peers and other decision-makers because they want the deal insured against their own absence. If your champion resists multi-threading and works to remain your only contact, treat that as a warning sign rather than a comfort. Recruit a backup champion in a different function within the first month, regardless of how strong your primary one seems.

What happens if I advance a deal without all three commitments? You're forecasting on goodwill, which is the most fragile input in a pipeline. Deals riding on a coach mislabeled as a champion are the ones that "surprise" everyone by slipping a quarter — the advocate you were counting on never actually spent anything, so when procurement pushed back or a competing priority emerged, no one inside the account fought for you. Encoding the three commitments as required CRM fields and refusing to mark an opportunity "Commit" without a champion artifact is the cheapest way to catch these deals before they slip rather than after.

Sources

• Gartner — The B2B Buying Journey (research on buying groups of six to ten stakeholders and how buyers actually make decisions): https://www.gartner.com/en/sales/insights/b2b-buying-journey
• MEDDIC Academy — the Champion criterion within MEDDIC / MEDDPICC (power, personal win, sells on your behalf): https://meddic.academy/
• Harvard Business Review — sales and B2B buying research, including work on consensus-driven buying committees: https://hbr.org/topic/subject/sales
• Force Management — Command of the Message and champion/decision-criteria qualification: https://www.forcemanagement.com/
• HubSpot Sales Blog — practical guidance on identifying sales champions vs. coaches and multi-threading deals: https://blog.hubspot.com/sales
• Winning by Design — B2B revenue methodology on buyer roles, deal qualification, and expansion: https://winningbydesign.com/

Related on PULSE

• [A champion keeps slipping the demo (slip-then-slip). How do we know when to move to a new contact or escalate around them?](/knowledge/q330)
• [How do you track multi-thread depth on enterprise deals using only native CRM contact roles?](/knowledge/q10469)
• [How are 2027 buying committees using generative AI to compare vendor pricing before any contact?](/knowledge/q16659)
• [How are 2027 B2B marketing teams recalibrating MQL definitions when AI chatbots pre-screen 90% of inbound leads before human contact?](/knowledge/q13585)
• [Can Zoho CRM integrate seamlessly with QuickBooks for invoicing and contact sync?](/knowledge/q14448)

TAGS: champion-identification,buying-committee,deal-momentum,pilot-commitment,internal-advocacy,meddic