Build a champion so the deal doesn't rest on one person.
Scores who can champion, arms them with the internal-sell narrative and a forwardable one-pager, and maps the multi-thread.
Inside: The champion score, the internal-sell narrative, and the thread map.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads the contact roles, titles, and engagement automatically, so the champion scoring and the thread map match the real account.
pulls who is actually replying and who has gone quiet, so the multi-thread plan is based on real engagement, not the org chart.
fills in titles, seniority, and reporting lines so you can see who your champion still needs to reach.
This was built for a B2B SaaS org selling into a buying committee. Set these to your stack:
Your definition of a champion is yours. The skill scores against the traits you set, not a generic profile.
| Set this | What it is | Default / Example |
|---|---|---|
| CONTACT ROLES | how you see who is on a deal | OpportunityContactRolebuyer role field |
| CHAMPION traits | what makes a real champion for you | has power or accessfeels the painwill act |
| THREADS_TARGET | how many engaged contacts you want | 3 (re-tune to your deal size) |
| ENGAGEMENT source | where replies and touches live | TaskEventemail or meeting tool |
| ONE_PAGER format | how your champion forwards the case | your templateyour brand |
| ENRICHMENT | source for titles and reporting lines | your enrichment connector |
Everything the skill does, in full.
Takes an account and turns one interested contact into a champion who sells for you when you are not in the room. It scores who on the deal can actually be a champion, writes the narrative they use to make the case internally, builds the one-pager they can forward without editing, and maps the other threads you need so the whole deal does not hang on a single relationship. One champion is one point of failure; this removes it.
- 1Identify the champion (score, do not assume)
Not every friendly contact is a champion. Score each contact on three things: do they have power or access to it, do they personally feel the pain you solve, and will they actually spend capital to act. A contact who likes you but cannot move anyone is a coach, not a champion. Name the difference.
- 2Arm them with the internal-sell narrative
Your champion has to sell this when you are not there, to people you may never meet. Write the case in their language: the problem in the organization's terms, why now, what it costs to do nothing, and what the win looks like for their team. Short enough to say in a hallway.
- 3Build the one-pager (forward without editing)
Give the champion something they can send up the chain untouched: the problem, the solution, the value, and the ask, on one page in their voice. If they have to rewrite it, they will not send it. Make it forwardable as-is.
- 4Map the multi-thread (do not rest on one person)
List every role the deal needs on side: the economic buyer, the technical evaluator, the blocker, the coach. Mark who is engaged and who is dark. Every single-threaded deal is one departure away from dead. Plan the next thread to open and who opens it.
- 5Test the champion (before you rely on them)
Give the champion a small ask that proves they will act: a meeting with their boss, an internal intro, a piece of information only an insider gets. If they deliver, they are real. If they stall, you have a coach, and you plan a second thread now, not later.
- No contact is called a champion without evidence they have access and will act, not just interest.
- The thread map names the roles that are still dark, never only the ones already engaged.
- The one-pager is written to be forwarded unedited, in the champion's terms, not yours.
- Engagement claims are grounded in real touches where that data is available, and flagged as assumption where it is not.
- Any name or title carried from the account is shown as given or sourced, never invented.
CHAMPION PLAN · Acme Corp (illustrative) Champion scoring Dana (VP Ops) power: yes pain: high will act: proven -> CHAMPION Sam (Analyst) power: no pain: high will act: yes -> coach Priya (Finance) power: yes pain: low will act: unknown -> reach Thread map (target: 3 engaged) Economic buyer CFO DARK <- open next, via Dana Technical eval Sam engaged Champion Dana engaged Blocker Security lead unknown Next moves: 1. Arm Dana with the one-pager for the CFO conversation. 2. Ask Dana for the intro to Finance. That is the champion test. 3. Open the security thread before it becomes a late surprise.
Where an operator takes this next.
Scoring one account by hand catches the risk before it costs you the deal. Here's the version that watches every open deal at once.
A champion tested once by hand is a habit once it runs on every deal automatically.
Connect Salesforce contact roles to a scheduled Claude task that scans open opportunities weekly and surfaces any deal with only one engaged contact.
Wire Gong or your email tool so a champion who stops replying triggers a Slack alert to the rep before the silence becomes a lost deal.
Connect this to your business-case skill so the moment a champion is scored, the forwardable one-pager drafts itself in their voice, ready to send up the chain.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.