Stakeholder mapping

Stakeholder mapping is the practice of identifying everyone who influences a buying decision and recording what each of them wants, how much power they hold, and where they stand on your proposal. It is a map of the decision, not of the organization.

Why it matters in B2B sales

B2B purchases above a modest size are made by groups, and the group is usually larger than the seller thinks. Six to ten people is typical on enterprise software, more when procurement, security, and legal are counted. Each has a different reason to care and a different reason to object, and most of them never speak to the vendor.

Deals lose to people who were never in the room. A security lead who was not consulted raises an objection in week nine. A finance director with no stake in the outcome sees only the cost. The map exists to make those positions visible early enough to do something about them, which usually means finding someone inside the account to make the argument you cannot make yourself.

What to record about each stakeholder

Their role in the decision rather than their job title: economic buyer, technical evaluator, end user, blocker, coach. What they personally want, which is rarely what the requirements document says and often concerns their own risk or workload. Their level of influence, which correlates loosely with seniority and sometimes not at all.

Then their current position: supportive, neutral, opposed, or unknown, with unknown recorded honestly rather than optimistically. And the relationships between them, since who defers to whom decides more outcomes than any individual preference. Finally, who owns the relationship on your side and when they last spoke. Frameworks like MEDDIC formalize parts of this, and the fields matter less than filling them in truthfully.

Stakeholder mapping vs an org chart

An org chart shows reporting lines. A stakeholder map shows influence over one decision, and the two frequently disagree. A mid-level architect whose technical judgment the CTO trusts can carry more weight on a platform choice than a VP two levels above them.

The org chart is also static and public, while a stakeholder map is specific to this purchase and changes as the deal moves. Someone neutral in month one becomes a blocker when the pricing reaches them. Treating the org chart as the map is the most common version of this mistake, and it produces a plan that engages the visible people and misses the influential ones. The decision-maker is often not the most senior name on the chart.

A concrete example

A vendor selling into a retail group maps eight stakeholders. The IT director is supportive, the head of stores is the economic buyer and neutral, and an operations manager with no formal authority is opposed because the rollout adds work to her teams. The rep spends two sessions with the operations manager rather than with the buyer, agrees a phased rollout that changes her workload profile, and she becomes the person who argues for the purchase in a meeting the vendor never attends.

How it shows up in a modern proposal workflow

What the map contains has to reach the documents. A proposal written without it addresses the requirement generically and gives each reader the same argument, when the buying committee is exactly the audience that needs different arguments in different sections. Cobl keeps the deal and its material in one workspace, so what the team knows about who is reading is present when the proposal is produced.

An executive summary written for the economic buyer and a technical section written for the evaluator is not a formatting choice. It is the map, applied.

Frequently asked questions

How many stakeholders are involved in a B2B purchase?

Commonly six to ten on significant purchases, and more in regulated sectors or where procurement runs a formal process. The number matters less than the spread: the risk is not volume but having no visibility of two or three of them.

What is the difference between a champion and a coach?

A champion has influence and actively argues for you internally. A coach gives you information and guidance about the process and the politics but may not advocate. Both are valuable, and mistaking a coach for a champion is a common way to overrate a deal.

When should you map stakeholders?

From the first qualified conversation, and keep updating it. Mapping late, once a bid is underway, gives you the picture without the time to act on it. Positions also shift as pricing and implications reach new people, so a map built once is out of date within weeks.