multithreading

---
name: multithreading
description: Maps the missing decision-makers on a deal, tests whether you really have a champion, and drafts the introductions in the right order. Use when a deal is single-threaded, has gone quiet, or is about to meet an executive.
---

# Reach the other decision-makers before the deal stalls

A stakeholder map, a straight verdict on your champion, and introduction drafts sequenced so they do not backfire.

## Claude does

1. Asks for: company, deal size band, every contact spoken to with their real job title, how many meetings so far, and what your main contact has actually done for you. Claude refuses to guess titles, reporting lines or headcount.
2. Counts the gap. Gong's analysis of 1M+ executive sales cycles found a won $50K-$250K deal typically involves at least 10 stakeholders. Claude lists the missing roles: economic buyer, users, technical evaluator, finance, legal or procurement, the sceptic.
3. Runs the champion test first (MEDDICC: "No Champion, No Deal"). Your contact is not a champion if they will not give you access to stakeholders, do not share information, are not proactive, never tell you anything new, or will not commit. Claude names which of the five is failing.
4. Times the executive. Win rates drop about 6% when the evaluation opens with an executive and rise about 5% when executives come in around the third touchpoint. On touchpoint one or two, Claude says wait and names what must happen first.
5. Refuses the mass introduction. Gong warns against adding dozens of contacts early without a strong champion behind them. One stakeholder at a time.
6. Produces the routing table: per missing person, champion-ghostwritten invite, direct approach, or hold, with the reason.

## Then Codex does

Codex takes the routing table and does the bulk drafting: one message per stakeholder in the assigned format, plus the group agenda and the tracker. Mechanical, because every judgement (who, when, via whom) is fixed and there may be nine of them.

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

Claude fills in first: {DEAL_CONTEXT}, {STAKEHOLDER_MAP}, {CHAMPION_STATUS}, {ROUTING_TABLE}, {SENDER_NAME}.

## Claude checks

1. Every draft names whose name it goes out in. A ghostwritten invite reads as the champion's words, not yours.
2. No invented titles, team sizes, tools, budgets or quotes. Anything not in {STAKEHOLDER_MAP} is deleted, not softened.
3. If {CHAMPION_STATUS} is "no champion", nothing addressed to an executive survives.
4. Nothing drafted for all contacts at once. Sequence intact, holds still held.
5. The agenda carries the dissent question verbatim: "Who has a different opinion on the way we've outlined the problem here?"
6. Any check failing goes back to Codex with the failing line quoted. Never fixed silently.

## Rules

- Public information only.
- Never invent a fact, a number or a quote.
- Anything sent in someone's name says whose name it is.
- Do not open the evaluation with the executive.
- No champion, no introductions.
- Drafts only. The user sends.

## If Codex is not installed

Claude writes the drafts, agenda and tracker itself and says it did that half.

## Built from

- Gong Labs, multi-threading to executives, https://www.gong.io/blog/when-and-how-to-multi-thread-when-selling-to-executives - 1M+ executive sales cycles analysed.
- MEDDICC, 5 signs you don't have a champion, https://meddicc.com/resources/5-signs-you-dont-have-a-champion - published MEDDPICC champion test.
- louisblythe/Sales-Skills, https://github.com/louisblythe/Sales-Skills - 143 stars (api.github.com).

# Reach the other decision-makers before the deal stalls - Codex task

You are drafting stakeholder outreach for one sales deal. Every decision has already been made by the person handing you this file. You write the wording only.

## You are given

- {DEAL_CONTEXT} - company, what is being sold, deal size band, how many meetings have happened so far.
- {STAKEHOLDER_MAP} - the contacts already spoken to, with real job titles, and the missing roles (economic buyer, users, technical evaluator, finance, legal or procurement, sceptic).
- {CHAMPION_STATUS} - either the named champion, or "no champion" plus which of the five MEDDICC signs is failing.
- {ROUTING_TABLE} - one row per missing person: name or role, route (champion-ghostwritten invite / direct approach / hold), and the reason.
- {SENDER_NAME} - the person the direct messages go out from.

## Produce

1. `outreach/` - one Markdown file per row in {ROUTING_TABLE} whose route is not "hold". Each file: a subject line under 60 characters, a body under 120 words, and a first line stating whose name the message goes out in.
   - Champion-ghostwritten invites use this shape, with the brackets filled from {DEAL_CONTEXT}: "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]."
   - Direct approaches go out from {SENDER_NAME} and reference only what is in {STAKEHOLDER_MAP}.
2. `agenda.md` - a 30-minute group-meeting agenda for the stakeholders reached. It must include, verbatim, the question: "Who has a different opinion on the way we've outlined the problem here?"
3. `tracker.md` - one table: person, role, route, whose name it goes out in, status (drafted / held), reason held.

## Rules

- Write nothing that is not supported by {DEAL_CONTEXT} or {STAKEHOLDER_MAP}. No invented titles, team sizes, tools, budgets, metrics or quotes. If a field is missing, write `[MISSING: what is needed]`.
- If {CHAMPION_STATUS} is "no champion", produce no file addressed to an executive. Write the row into `tracker.md` as held.
- Never merge rows into one broadcast message. One person, one file.
- Do not add stakeholders that are not in {ROUTING_TABLE}.
- British English. No em dashes. Drafts only, nothing is sent.

## Return

Print: the count of files written, the full contents of `tracker.md`, and one line per outreach file giving the filename plus the name it goes out in. Then print any `[MISSING: ...]` markers you left, or `NO MISSING FIELDS`.