# Firm Buying Committee Map

> Maps the roles in a client's buying decision (signs, funds, uses, can block, wrote the brief, runs it after), with what each role has said it needs and its source, stated or assumed, met or not met, and one question through your contact for each unmet role. Use for "run firm-buying-committee-map", "who decides on this engagement", "map the buying roles", "I have only met one person", "the signer never saw my pitch", "who else has to agree", "which roles have I not met", part of the Claude for Consultants · Team in Claude Pack by 90n.

- Skill: `polar-bear-org/firm-buying-committee-map` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/firm-buying-committee-map`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/firm-buying-committee-map/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/firm-buying-committee-map

---


# Buying Committee Map

## When To Use
One person at the client likes you and answers your emails. Everyone else in the decision is a blank: who releases the budget, who has to live with the result, who could quietly stop it. Run this when your whole view of the client passes through a single contact and you are about to write for that one reader.

## When Not To Use
If you doubt the opportunity deserves any effort yet, start with MEDDIC Qualification. When the task is planning whom to hear about the problem itself, that is Stakeholder Interview Plan; this map covers the purchase, not the diagnosis.

## Inputs
- Notes, emails and the client's brief (anything naming a role, a step or a concern)
- What your contact has told you about how a purchase like this gets approved
- Any written process you know of (procurement, legal review, a committee date)
If you have none of this, I start from the six standard roles and your contact's job title, and mark the map as a first draft made mostly of questions.

## Approach
Research on business buying describes purchases decided by a group of roles, seldom by one person; it is described here generically, with no figures. The map records each role's stated position separately and in its own words, before anything is merged into "what the client wants". Rows are roles and positions, never personalities, influence or attitudes. The failure it prevents is the proposal tuned to your contact's priorities that reaches a signer who cared about something else.

## Workflow
1. Ask, in one go: whom have you spoken to, and in what role? What did your contact say about how this gets approved? Is there a written step such as procurement, legal or a committee date?
2. Set six rows: signs, funds, uses the result, can block (legal, procurement, IT, data protection), wrote the brief, runs it after you leave. One person may hold two roles and a row may stay empty.
3. Per role, record what that role has said it needs, in its own words where you have them, with the source and date. Keep each role's view apart: your contact relaying a colleague's concern is your contact's account, not a second voice.
4. Mark every need stated (said to you or written down) or assumed (your guess, to test). A first map is usually mostly assumed, and seeing that is the point.
5. Mark each role met or not met. For every unmet role, write one question to put through your contact, or one introduction to ask for. Nothing here goes around your contact.
6. Where two roles appear to want different things, write it as a question to explore, never as a conclusion about anyone. Then stop: I do not order people by power or influence, and you choose whom to ask for and when.

## Output Format
```markdown
# Buying Roles Map
Client: [organisation] · Your contact: [role] · Updated: [date]
## Roles in the buying decision
| Role in the decision | Held by (public role) | What this role has said it needs | Stated or assumed | Source | Met |
|---|---|---|---|---|---|
| Signs | [role or unknown] | [their words] | [stated / assumed] | [call, date] | [yes / no] |
| Funds · Uses · Can block · Wrote the brief · Runs it after | [role or unknown] | [need] | [stated / assumed] | [source] | [yes / no] |
## Unmet roles
| Role | Question through your contact, or introduction to request | By |
|---|---|---|
| [role] | [question] | [date] |
## Differences to explore
- [Role] has said [x]; [role] has said [y]. Question: [question]
## Decision
[Your name] decides which introductions to ask [contact role] for, and in what order, by [date].
```

## Done When
- All six roles have a row, even when it reads "unknown"
- Every need is marked stated or assumed, and each stated need has a source
- Every unmet role has a single action, routed through your contact

## Quality Bar
- Public role and words said in this purchase only; nothing about a person's private life
- No power grid, no influence order, no personality label, no rating of anyone
- An assumed need is never written as if the client said it
- Roles and stated positions only, each with its source; I add no view the client did not give, and you decide whom to approach.

## Next
Run firm-bid-no-bid (Bid/No-Bid Decision) to decide whether the opportunity deserves the pursuit.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

