Free Multithreading & Champion Building Prompt

## StackSwap execution contract

You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.

1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.

### Output contract

Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.

### Evidence and verification

Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.

### Follow-on behavior

Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.

### Cross-platform behavior

This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.

---

---
name: multithreading-and-champion-building
description: "Map the buying committee and build a real champion so a deal survives a contact going dark. Produces a stakeholder map (champion, economic buyer, technical buyer, end users, blocker, procurement) with each person's stance and your coverage, a champion-vs-coach test, a champion-build plan, an EB-access play, and blocker management. MANDATORY TRIGGERS: 'map the buying committee', 'build a champion', 'multithread this deal', 'who are the stakeholders', 'I only have one contact', 'how do I get to the economic buyer', 'is my champion real', 'single-threaded deal'. STRONG TRIGGERS: 'champion went dark', 'deal died when my contact left', 'there is a blocker', 'I can't get to the decision maker', 'too reliant on one person', 'coach vs champion'. Do NOT trigger on: running the discovery call itself (use discovery-call-runner), building the ROI case (use business-case-and-roi-builder), or the close mechanics (use deal-negotiation-and-closing). DO trigger when a seller needs to widen a deal beyond one contact and build internal advocacy."
allowed-tools: Read Write WebSearch WebFetch
metadata:
  author: Nick French / StackSwap
  version: '1.0'
  product: Operator Playbook
  website: stackswap.ai/playbook
---

# Multithreading & Champion-Building

The rep has one great contact. They talk weekly, the contact loves the product, the forecast says commit. Then the contact gets reorged, goes on leave, or turns out to have zero budget authority, and a "95%" deal evaporates overnight. Single-threading is the most common cause of preventable deal loss in B2B SaaS. The buying committee has six to ten people who can say no, and the rep was talking to one of them.

> **A single-threaded deal is one resignation away from dead. You don't have a deal until you have a champion who sells for you when you're not in the room, and a map of every person who can kill it.**

This skill maps the buying committee, separates real champions from friendly coaches, builds the champion's ability to sell internally, gets you to the economic buyer, and neutralizes the blocker before it surfaces at signature.

---

## When to use this skill

Trigger on:

- "Map the buying committee" / "who are the stakeholders?"
- "I only have one contact"
- "How do I get to the economic buyer?"
- "Is my champion real?"

Don't run for:

- The discovery call itself (use `discovery-call-runner`)
- The ROI case (use `business-case-and-roi-builder`)
- The close mechanics (use `deal-negotiation-and-closing`)

---

## The framework

### 1. The buying-committee map

Name every role and the human in it:

- **Champion**, has power, sells internally, has a personal win
- **Economic Buyer (EB)**, controls budget, makes the final call
- **Technical buyer**, validates fit, can veto on requirements
- **End users**, live with it daily; their enthusiasm or resistance is real
- **Blocker**, the no-voter (status-quo defender, competing vendor's champion, threatened incumbent owner)
- **Procurement / legal**, the paper-process gatekeepers

For each: their stance (champion / supporter / neutral / skeptic / blocker) and **your coverage** (who on your side owns the relationship).

### 2. Champion vs. coach (the distinction that saves deals)

The most expensive mistake is mistaking a coach for a champion:

- A **coach** gives you information and likes you. Useful, but powerless.
- A **champion** has organizational power, actively sells on your behalf when you're absent, and has a **personal win** if the deal closes (a promotion, a problem solved, a metric they own).

A friendly contact who can't get you a meeting with the EB is a coach, not a champion. Know which you have, and don't forecast a deal on a coach.

### 3. Building the champion

Champions are built, not found:

- **Give them the personal win**, connect the deal to what advances *them*
- **Arm them**, hand them the business case (`business-case-and-roi-builder`) so they can sell internally
- **Make them look good**, feed them insights, data, and wins they can take credit for
- **Test their power** (see §6)

### 4. The economic-buyer access play

Champion-gated deals are risky, if you've never met the EB, you're trusting the champion's read of someone you can't see. Get EB access:

- Trade for it: "To build the business case properly, I'd want 20 minutes with [EB], can you make that intro?"
- A champion who *can't or won't* get you to the EB is telling you something about their real power.
- Going over the champion's head burns them, always route *through*, with their buy-in.

### 5. Blocker management

Find the no-voter early. The blocker is often silent until late, then sinks the deal. Identify them, understand the *why* (fear of change, a competing relationship, a turf threat), and either **convert** (address the fear, give them a win) or **neutralize** (outweigh them with champion + EB + users). Never ignore them, a surfaced blocker at signature is a dead deal.

### 6. The champion test

Pressure-test whether your champion is real:

- Will they take your call *before* you've asked for anything?
- Will they get you the EB meeting?
- Will they give you a **bad-news heads-up** (a competitor's quote, a budget freeze) before you find out the hard way?
- Will they defend the deal in a room you're not in?

A "yes" on all four is a champion. Anything less is a coach you're over-trusting.

### 7. Multithreading mechanics (without burning the champion)

Expanding contacts can offend a possessive champion if done clumsily. Do it *with* them: "To de-risk this for both of us, I'd love to loop in [end user / technical buyer], can you help me set that up?" Frame multithreading as protecting *their* internal credibility, not going around them.

---

## The process when triggered

### Step 1: Map the committee
Every role, the human, their stance, your coverage (§1).

### Step 2: Classify your contacts
Champion vs. coach vs. supporter. Be honest (§2).

### Step 3: Build the champion
Personal win, arm with the business case, make them look good (§3).

### Step 4: Get EB access
Trade for the intro; read what the attempt tells you (§4).

### Step 5: Find and manage the blocker
Identify, understand the why, convert or neutralize (§5).

### Step 6: Test and multithread
Run the champion test; expand contacts with the champion's buy-in (§6-7).

---

## The artifact (template)

```markdown
# Buying-Committee Map, [Account], [Date]

## Stakeholder map
| Person | Role | Stance | Your coverage | Champion test | Next action |
| --- | --- | --- | --- | --- | --- |
| ... | Champion/EB/Tech/User/Blocker/Procurement | champ/support/neutral/skeptic/blocker | [your owner] | pass/fail | ... |

## Champion plan
- Champion: [name], power: H/M/L | personal win: ___ | armed with business case: Y/N
- Champion test result: [4 questions]

## EB access
- Met EB? Y/N | Path: [champion intro / exec sponsor] | Next step: ___

## Blocker
- Blocker: [name], why: ___ → plan: convert / neutralize

## Coverage gaps
- Roles with no relationship: ___ → multithread plan (with champion buy-in): ___
```

---

## Common mistakes

- **Confusing a coach for a champion.** A friendly contact with no power is not a champion. Run the test.
- **Single-threading.** One contact = one point of failure. Map and cover the committee.
- **Never meeting the EB.** Champion-gated deals are blind spots. Trade for EB access.
- **Ignoring the blocker.** The silent no-voter sinks deals at signature. Find them early.
- **Over-relying on one champion.** Even a real champion can leave. Build depth.
- **Not testing champion power.** Assumption is how "commit" deals collapse. Test the four questions.
- **Clumsy multithreading.** Going around a champion burns them. Expand *with* their buy-in.

---

## How to use the artifact downstream

1. **Sourced by discovery**, `discovery-call-runner` surfaces the committee and the power map.
2. **Champion armed by the business case**, `business-case-and-roi-builder` is the champion's internal-selling tool.
3. **Required for the close**, `deal-negotiation-and-closing` needs the EB engaged and the blocker neutralized.
4. **Deal-health signal for the forecast**, single-threaded or coach-only deals get a confidence haircut in `forecasting-and-pipeline-review`.

---

**A deal is not real until someone inside sells it for you when you're gone. Map every person who can say no, tell your champions from your coaches, arm the champions with a business case, get to the economic buyer, and neutralize the blocker before it surfaces. Reps with one happy contact get surprised. Operators who multithread get signatures.**

---

_Part of the StackSwap Operator Playbook. → stackswap.ai/playbook_

Free forever. No email gate.