← ALL PLAYBOOKS
── PLAYBOOK · SALES
✓ APPROVED

Win the whole buying committee

Single-threaded deals die. Stop chasing whoever replies and earn the whole committee.

[ BUILT GTM ]

Win the whole buying committee

Solvethe problem worth solving
Problem · 01Sales

Single-threaded deals die.

Stop chasing whoever replies and earn the whole committee.

Stackthe workflow, box by box
Salesforce01
Build a champion so the deal doesn't rest on one person.
Map the org chart: score who can champion and name every committee role still dark.
Powers up with
AI + human
Salesforce02
Get a straight verdict on every open deal.
Get the deal-verdict snapshot right now, not just who is mapped.
Powers up with
AI
Gong03
Read the whole relationship at a glance.
Track the reply-cadence trend over time, to catch a champion cooling before the verdict catches up.
Powers up with
AI + human
Salesforce04
Give the deal a dated path to signature.
Give the deal a dated path to signature.
Powers up with
AI
Splithow control passes: agents branch left, humans right
HUMAN + AI, IN THE LOOP
How control passes.
AgentsHuman
AI + human01
Build a champion so the deal doesn't rest on one person.
AI drafts, a human checks.
Agent02
Get a straight verdict on every open deal.
Salesforce runs it.
AI + human03
Read the whole relationship at a glance.
AI drafts, a human checks.
Agent04
Give the deal a dated path to signature.
Salesforce runs it.
The skills run the work. You stay in the loop on the calls that need judgment.
Outputwhat the workflow produces
OUTPUT · 01

A real champion

OUTPUT · 02

A read on every open deal

OUTPUT · 03

The relationship pulse

OUTPUT · 04

A dated close plan

Outcomethe result it drives
OUTCOME · 01

The Love Test

From reactive to whoever replied, to multi-threaded on every live deal.

Built GTM
── 01 / WHY RUN IT

One person replies, so you treat the deal as covered. Then that person goes quiet, gets promoted, or leaves, and the deal you thought was safe dies with no warning because nobody else in the account ever heard from you.

RUN THIS AND YOU CAN
A real champion, scored and armed with a forwardable one-pager
An honest verdict on every open deal, not just who is mapped
An early read on a champion cooling, before the deal shows it
A dated, milestone-owned path to signature
── 02 / THE RUN, STEP BY STEP

The workflow that solves it, one step at a time.

Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.

1✓ TESTED
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.

YOU GETThe champion score, the internal-sell narrative, and the thread map.
OPEN THE SKILL →
2✓ TESTED
Get a straight verdict on every open deal.

Healthy, slipping, stuck, or dead. Checks real activity, whether the rep qualified it, and whether the deal is multi-threaded.

YOU GETThe risk taxonomy, the activity checks, and the per-deal verdict format.
OPEN THE SKILL →
3✓ TESTED
Read the whole relationship at a glance.

Puts meetings, replies, and sequence activity on one timeline and flags the moment a champion goes dark.

YOU GETThe relationship timeline and the champion-drop detector.
OPEN THE SKILL →
4✓ TESTED
Give the deal a dated path to signature.

Builds a close plan with the champion: milestones, owners, dates, and exit criteria, written to send.

YOU GETThe backward-from-signature plan, owners and dates, and exit criteria.
OPEN THE SKILL →
WHERE YOU LAND

A real champion, a read on every open deal, the relationship pulse, and a dated close plan.

EVERY STEP, TESTED AND PASSED
EVAL RESULTPASS4/4 dimensions
HOW WE EVAL →
Skills resolve
Structure + proof
Example chat
Quality judge
  • All 4 chained skills resolve to real, scored skills.
  • Has a problem, an outcome, 2+ steps, and proof from a real build.
  • Ships an example chat showing the play run in Claude.
  • Reads in plain operator voice, grounded in a real build.
Last eval run 2026-08-05
DEEP EVAL · PASS
THE STANDARD →

We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: An AE has a large deal riding on one contact who replies, and it keeps dying every time that pattern repeats.

── 03 / SEE IT RUN

Watch the skills answer in order.

Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.

EXAMPLE CHATMarcus, Account Executive, running the loop in one sitting
M
My biggest deal is riding on one guy who replies to me. Every time I go single-threaded like this it dies. Help me build a real champion.
S
Step 1· Champion Plan
Let's turn that one contact into a real champion and stop the deal resting on him. I scored who can actually champion, wrote the narrative he uses to sell it internally, and mapped the other threads you need to open.
threadseconomic buyer, IT, end user
Receipt
Champion scored CHAMPION (power yes, pain high, will-act proven); a forwardable one-pager built plus 3 stakeholders to thread into.
M
Is this deal actually multi-threaded now or am I fooling myself?
S
Step 2· Deal Health Analyst
I gave the deal a straight verdict and checked whether the relationships are real or just the one reply thread. Right now it is still thin, with the economic buyer never having been in a live conversation.
Receipt
Verdict: slipping. Only 2 of 5 committee members have any recorded activity.
M
Who has gone quiet that I have not noticed?
S
Step 3· Conversation Analyst
I put every meeting, reply, and sequence touch on one timeline and watched for the trend. Your champion is cooling, replies have slowed over the last two weeks, well before the formal 21-day drop-off line, so you still have a window to act before it becomes a lagging signal.
Receipt
Reply cadence trend: every 2 days to 9 days between replies, a warning sign short of the formal 21-day drop-off threshold; a re-engage touch drafted.
M
Give the deal a real path to signature I can put in front of them.
S
Step 4· Mutual Action Plan
I built a dated close plan backward from signature with the champion: milestones, owners, and exit criteria, written so you can send it. It puts the committee on a shared timeline instead of your hopeful close date.
Receipt
MAP with 6 milestones to a signature date 34 days out, each with a named owner on their side.
── 04 / SEE IT IN PRODUCTION

Before you run it, I ran it for real.

This workflow is genericized from a real build. Here is the number it moved, and what I actually did.

THE BUILD · LENS: DEAL EFFORT
The Love Test
~2
touchpoints per account, on average, my reps
5%
win rate when a deal is single-threaded
40%
of deals die from single-thread dependency
6.8
stakeholders in the average B2B purchase
WHAT I DID
01
The love test. I ran the analysis: were reps earning attention through multi-step prospecting, or just reacting to whoever already showed it? The data was blunt. Reps averaged about two touchpoints per account and over-indexed on inbound, neglecting every other channel. Effort was following responsiveness, not opportunity.
02
Make persistence a motion, not a mood. If most deals need five or more touches and reps average two, the fix is not motivation. It is a multi-step prospecting motion that runs across every channel, whether or not the account has written back yet.
03
Thread the deal, not the champion. Ladder each altitude of the problem, personal, team, and org, to the person who owns it, so the deal survives any one contact going dark. Multi-threading covers the whole buying committee, not just the contact who answers first.

Reps invest effort where interest already exists. The fix is not more leads, it is a prospecting motion that earns attention before the account gives it: multi-step, every channel, threaded across the whole buying committee.

Dig into the full build
05 / INSTALL THE WHOLE PLAYBOOK

One plugin. 4 skills, bundled.

The whole playbook installs as a single plugin in Claude Code, no copy-pasting 4 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.

OR KICK IT OFF IN CHAT
Here is my situation: [describe your workflow or account in a sentence or two]. Walk me through Win the whole buying committee step by step, and run each skill as we go.
── GET THE NEXT PLAYBOOK

One runnable workflow a week. Free.