Multi-Thread the Account

---
name: multi-thread-the-account
description: Use when planning to expand contact beyond a single champion in an enterprise deal. Triggers on "multi-thread", "expand the contacts", "single-threaded", "champion is leaving / out".
---

# Multi-Thread the Account

The data is clear: single-threaded deals close at half the rate of multi-threaded deals. But aggressive multi-threading without a plan reads as going-over-their-head and burns champions. This skill threads the needle.

## Required inputs

1. **Who you've met so far** — name, role, relationship strength, what they've committed to
2. **Who you need to meet** — based on the buying motion (economic, technical, security, procurement, end users)
3. **Why each one matters** — not "stakeholder coverage" — the specific risk if they're not engaged
4. **What your current champion knows about your multi-threading plan** — and whether they'd support it

If your champion would actively block your multi-threading, your champion isn't a champion — they're a gatekeeper. Plan for that reality.

## The plan

### Map: the people, ranked
For each unmet stakeholder, rate:
- **Risk if not engaged** (H/M/L) — what they could veto
- **Reachability** (H/M/L) — how easily you can connect
- **Sequencing** (1st, 2nd, 3rd) — order in which to engage

### The pretext per person
You can't just "want to connect." Each outreach needs a specific reason that benefits THEM:
- For the CFO: ROI model they need for budget approval
- For Security: a Q&A session ahead of vendor review
- For end users: a hands-on workshop or pilot
- For procurement: a paper-trail handoff session
- For a peer of the champion: a peer-reference call

### How to involve the champion
Two options:
1. **Champion-led** — they make the intro. Best when relationship is strong and trust is mutual.
   - Script: "Hey, I'd love to involve [name from CFO's office] for the ROI discussion. Could you intro?"
2. **Champion-informed** — you reach out directly, but tell the champion first so it doesn't look like an end-run.
   - Script: "I'm going to reach out to [name] about [specific topic], since it'll move faster if we get them involved early. Wanted you to know so it doesn't surprise you."

Option 1 is preferred. Option 2 is the fallback. Never option 3 (reaching out without telling the champion) — that's the move that ends relationships.

### The artifact each new contact gets first
Don't show up with a generic pitch. Show up with the specific thing that's useful to that person:
- CFO: ROI 1-pager with their inputs
- Security: SOC 2 report + DPA + last pen-test summary
- End user: short demo recording or trial access
- Procurement: order form + standard terms

### Cadence
- Don't do all the new outreach in one week — that reads as panic
- Space it 1–2 outreach per week, woven into deal progression
- Always weave it into a deal moment (right after a successful demo, etc.) so it feels organic

### Tracking
| Stakeholder | Contacted | Met | Engaged | Status |
|---|---|---|---|---|

"Met" = one conversation. "Engaged" = they've asked for something or volunteered info.

## Failure modes to plan for

- **Champion gets defensive**: pre-empt with "I want to make sure I'm not creating extra work for you — should I route through you or reach out directly?"
- **New contact ignores you**: have a 2nd-touch plan (a different artifact, a different pretext) before you start
- **New contact gives different info than champion**: don't surface the contradiction immediately — confirm with both before flagging
- **Champion leaves mid-deal**: the whole point of multi-threading is this scenario. If you've done it well, the deal survives.

## Tone

- Strategic, not desperate
- Respectful of the champion's political reality
- Patient — multi-threading takes weeks, not days
- Document everything in CRM so your manager / future-you can see the map