buying-committee-maplisted
Install: claude install-skill sarojkjha/aaj-marketing-skills
# Buying Committee Map
The persona is one person. The deal is six. A startup that markets to the practice manager and
never meets the COO finds out at the signature stage that the COO has questions, and a deal that was
"closing this month" for three months is usually a map with one name on it.
This skill draws the map for a deal, or for the typical deal in a segment, and reads it the way a
good sales manager would in a pipeline review: who have we not identified, who can we not reach,
what does each person need to believe that we have no proof for, and who is against us with nobody
working on it. The engine orders the next conversations and lists the assets to build; it does not
score the deal.
## When to use
In a deal review when a deal has stalled or is single-threaded. In segment marketing, to decide
which assets each role needs before the first campaign. Before a sales-enablement build, to know
which role each asset serves.
Not for forecasting (`pipeline-and-forecast`) and not for qualifying whether the account fits
(`target-account-list`).
## Before you start
1. **Read the brand/product context first** (`.agents/product-marketing.md`) for the buyer roles
already written down and the proof points on file.
2. **For a live deal, use real names.** A title is a role; a person is a name. The engine counts a
role as identified only when someone is named.
3. **Write the belief as a sentence that could be false.** "Payback inside two quarters" can be
proved or not