What it is and what problem it solves
The usual mistake is to have one contact in the CRM and call that person "the customer." The rep talks to whoever picks up, builds the relationship, and when the deal reaches the committee, someone nobody had met shows up with an objection nobody had prepared for.
The map sorts that out before it happens. For each priority segment it captures the buying roles, the title that usually holds each one, what each person gains and risks, what objection they'll raise and who holds a veto. It is the foundation for writing promise and proof by role and for designing the commercial playbook. We cover the underlying concept in depth in the guide to the B2B buying center.
When to use it and when not to
It is built after the winnability matrix: one map per prioritized segment, not one for the whole market. It is essential when the sales cycle runs longer than a few weeks, when more than two people take part in the decision, or when deals die in the final stage without explanation.
It adds little to low-ticket transactional sales with a single buyer. When a colmado, a neighborhood corner store, restocks, the owner is user, decision-maker and payer at once. There, describing that person and their ordering routine well is enough.
How to build it
- Reconstruct real purchases. Five to ten recent deals, won and lost: who took part, in what order and who had the last word. Deliverable: a timeline per deal.
- Assign roles. Every person who appears is assigned one or more roles. Deliverable: roles with a typical title per segment.
- Interview. Three to six conversations per segment with customers and with people who didn't buy. Deliverable: motivations and objections in their own words.
- Locate the real power. Who signs, who holds a veto and who controls access. Deliverable: the map with veto points marked.
- Translate it into the playbook. Which conversation to have with each role, with what material and at what point in the cycle. Deliverable: a contact sequence by role, ready for the commercial playbook.
Anatomy of the deliverable
One map per segment. Here is the template, filled in with a hypothetical example of an industrial maintenance service sold to a food processing plant:
| Role | Typical title | What they gain | What they risk | Typical objection | How to reach them |
|---|---|---|---|---|---|
| Initiator | Maintenance manager | Fewer unplanned stoppages | Getting blamed if the switch fails | "Our current supplier already knows the machines" | A free, tightly scoped technical assessment |
| User | Plant technicians | Fewer emergencies | Learning curve | "Yet another procedure" | A hands-on demo on their own machines |
| Influencer | Quality director | Clean audits | Certification deviations | "Does it meet the standard we're audited against?" | Technical documentation and records |
| Decider | Operations director | Stable cost per ton | A shutdown in peak season | "What happens if you fail mid-season?" | A written contingency plan |
| Buyer | Purchasing | Better terms than last year | Justifying the change of supplier | "You're more expensive" | A total cost comparison with open assumptions |
| Gatekeeper | Executive or purchasing assistant | Protecting the calendar | Letting an irrelevant supplier through | Silence | An introduction through the initiator |
The two columns most often forgotten are "what they risk" and "how to reach them." They are the ones that turn the map into sales work.
The classic framework: Webster and Wind, brought down to job titles
Frederick Webster and Yoram Wind published their general model of organizational buying behavior in 1972. Their central contribution is the buying center: the group of people who take part in a purchase decision and share its goals and risks. They described five roles, users, influencers, buyers, deciders and gatekeepers, and later literature added the initiator, the person who spots the need. The model places the purchase inside four layers of influence: environmental, organizational, group and individual.
What we do is bring the roles down to job titles and conversations. You can't phone an abstract role; you can phone an operations director. We add two fields the model doesn't have: each role's objection in their own words, and the veto point. And we always separate who pays from who decides, because in Dominican family groups and in Spanish SMEs organized by regional branches they often differ: the branch decides and headquarters pays, or the second generation proposes and the first one signs.
Where it falls short: the model describes how organizations buy, not how to sell to them. And it treats the buying center as stable, when it shifts with the deal size and the stage. The people involved in a small order are not the ones who appear when the amount forces the deal through a committee.
Common mistakes
- Confusing title with role. The CEO doesn't always decide; sometimes they only ratify. It happens because teams assume the org chart instead of reconstructing real purchases.
- Mapping only the people we already know. The CRM holds the contacts the sales team has managed to get, not the ones who decide. That is why step 1 starts from deals, not from the database.
- Ignoring the gatekeeper. Purchasing, IT, legal or the executive assistant don't decide, but they can stop an entire deal.
- One map for every segment. A hotel chain and an independent hotel buy through opposite structures. An averaged map describes neither.
An illustrative scenario
Take a hypothetical supplier of professional cleaning products selling to chain hotels on the east coast of the Dominican Republic. Its deals move well with the executive housekeeper, who is the initiator, and die at central purchasing over price.
The map shows that the buyer had never seen a cost-per-room comparison, only the price per liter, and that the hotel's operations director, who carries weight in the decision, had never entered the conversation. The playbook changes order: operations first, with the consumption argument, then purchasing, with total cost. The result is measured against the baseline, period by period.