champion-builder

---
name: champion-builder
description: Turns your notes on one deal into an internal selling kit your champion can forward without editing. Use when the decision happens in a room you are not in.
---

# Give your champion the words to sell you internally

A one-page internal case in your champion's voice, a ghostwritten executive invite, and answers to the objections they meet without you.

## Claude does

1. Asks for: champion name and title, the problem in their words, the metrics they own, the other stakeholders and titles, what the champion has done unprompted, your price. Missing items are asked once, then written as UNKNOWN, never guessed.
2. Scores the champion against MEDDICC's five signs you do not have one: no stakeholder access, will not share information, not proactive, tells you nothing new, will not commit. Three or more means a coach, not a champion; Claude says so and names one test to run this week.
3. Fixes the sequence. Executives join around the third touchpoint, where win rates rise about 5%; opening with one drops them about 6%. A won 50k to 250k deal involves at least 10 stakeholders.
4. Writes the one-page narrative in the champion's voice: problem, cost of standing still, what was evaluated, the recommendation, the risk of being wrong.
5. States the recommendation and the risk reversal outright. Bans urgency and scarcity, which backfired 84% of the time. Indecision loses 40% to 60% of deals, 56% of those to fear of failure, not a competitor.
6. Lists the objections the champion meets alone, each with a two-sentence spoken answer.

## Then Codex does

Codex repeats the approved narrative mechanically: one variant per stakeholder aimed at the metric that person owns, the executive invite, the objection table, consistent file names. Bulk formatting, no judgement.

```
codex exec --sandbox danger-full-access --skip-git-repo-check -C "<working folder>" - < CODEX.md
```

Claude fills in first: {CHAMPION}, {NARRATIVE}, {STAKEHOLDERS} as name, title, metric owned, {PROBLEM} in the champion's words, {VENDOR} your name and company.

## Claude checks

1. Each variant speaks to that stakeholder's own metric; identical copy is a reject.
2. No deadline pressure, scarcity or fear of missing out anywhere.
3. The invite reads as the champion's, with the vendor a guest, not the sender.
4. No number, quote or customer name the user did not supply; one invented figure rejects the run.
5. Every asset states whose name it goes out in.
6. Buyer and seller reasons for a loss match only 15% of the time, so assumed objections are flagged for the champion to confirm.

Reject and rerun with the failing point quoted. Never patch it quietly.

## Rules

- No champion, no deal. Say so rather than dressing up a coach.
- Never mass-invite stakeholders before the champion is real.
- Recommend; do not manufacture urgency.
- Public information only.
- Never invent a fact, a number or a quote.
- Anything sent in someone's name says whose name it is.

## If Codex is not installed

Claude writes the variants, invite and objection table itself and says it did both halves.

## Built from

- MEDDICC, Andy Whyte, https://meddicc.com/resources/5-signs-you-dont-have-a-champion - author of the MEDDICC book; the five signs.
- Gong Labs, https://www.gong.io/blog/when-and-how-to-multi-thread-when-selling-to-executives - over 1M executive sales cycles.
- The JOLT Effect, Dixon and McKenna, https://www.jolteffect.com/blog/what-is-the-jolt-effect - indecision and urgency data.
- Clozd, https://www.clozd.com/blog/5-lies-your-crm-is-telling-you-about-your-buyers - 1,000 closed-lost deals versus buyer interviews.

# Champion selling kit - Codex task

You are formatting an already-approved internal business case into a pack one buyer-side champion can forward. You are not writing strategy and not adding facts.

## You are given

- {CHAMPION} - name and job title of the person who will send everything.
- {NARRATIVE} - the approved one-page internal case, written in the champion's voice.
- {STAKEHOLDERS} - a list of name, job title, and the single metric that person owns.
- {PROBLEM} - the problem in the champion's own words.
- {VENDOR} - the seller's name and company.

## Produce

Write into the working folder:

1. `champion-pack/00-narrative.md` - {NARRATIVE} unchanged, with a header line naming {CHAMPION} as the sender.
2. `champion-pack/10-<lastname>.md` - one file per entry in {STAKEHOLDERS}. Each is the same argument rewritten to open on that person's owned metric, 150 to 200 words, ending with one question addressed to them. Sender line: {CHAMPION}.
3. `champion-pack/20-exec-invite.md` - a short message from {CHAMPION} using this structure exactly, with the brackets filled from the inputs:
   "As we consider [PROBLEM], I've asked [Your Name] at [Company] to spend 30 mins with our team. They had some unique perspective on [PROBLEM], based on [X and Y]."
   Add one line below it: "Who has a different opinion on the way we've outlined the problem here?"
4. `champion-pack/30-objections.md` - a table with columns Objection, Who raises it, What {CHAMPION} says. One row per objection carried in {NARRATIVE}. Answers are two sentences, spoken language, no jargon.
5. `champion-pack/README.md` - the file list, one line each, plus the sender name for every asset.

## Rules

- Use only the words and figures in the inputs. If a stakeholder has no metric, write UNKNOWN and leave the opening generic rather than inventing one.
- No deadlines, no countdowns, no scarcity, no "before the quarter ends".
- No customer names, case studies or statistics that are not already in {NARRATIVE}.
- Every file carries a first line: "Sent by: {CHAMPION}".
- British English. No em dash characters.
- Do not edit {NARRATIVE} itself.

## Return

Print, in this order:

1. The list of files created with byte counts.
2. The number of {STAKEHOLDERS} entries received and the number of stakeholder files written. These must match.
3. Each stakeholder file's opening sentence, one per line, so the metric used can be checked.
4. Any field marked UNKNOWN, with the file it appears in.
5. The literal line "NO INVENTED FACTS" only if every figure in the output also appears in the inputs.