The meeting that cannot say yes is the most dangerous one in the room

A stakeholder map is a working record of who in the buying organisation can say yes, who can say no, and who only feels entitled to an opinion. Most pitch teams draw one on a whiteboard once and never touch it again, which is roughly as useful as writing a BATNA (Best Alternative to a Negotiated Agreement) and then never checking whether it has changed. The map earns its keep only if it is built before you present and revised as you learn more.

The exercise starts with a plain question for every name on the account: what can this person actually decide, and what can they only influence? A procurement lead can block a deal by refusing sign-off on terms; they usually cannot approve the spend. A technical champion can get you into the room and argue your case when you have left it; they cannot commit the budget. Confusing influence with authority is the single most common reason a well-received pitch dies quietly afterwards, in a meeting the pitching team was never invited to.

Once you have placed these roles in the buying organisation, you still have to decide who from your side presents to each of them, because not every role responds to the same messenger. An economic buyer weighing risk to their own budget may want brevity from someone senior enough to negotiate terms on the spot, while a technical champion building the internal case may want detail from a peer who can answer the questions procurement will ask later. See the right person to sell to for how to match presenter to audience.

Where the gaps actually appear

The first gap is a missing economic buyer: the person with real budget authority, distinct from the champion or the user, has never been identified, so the whole pitch is built for an audience that cannot approve it. The second is an unmapped blocker, someone with the standing to stop the deal who was never consulted and therefore has no reason to defend it when asked. The third is treating a committee as a single mind, when in practice each member is weighing something different: cost to one, risk to another, credit for the initiative to a third.

None of these gaps show up in the room. They show up two weeks later, in the silence after a pitch that seemed to land well. That gap between a good reception and a stalled decision is usually not a flaw in the material. It is a flaw in the map.

Filling the gaps before you present

Filling them is mostly a matter of asking, directly. Who signs this off once the room agrees? Who has to be satisfied but will not be in the room? Who has killed a similar proposal before, and why? A champion who cannot answer these questions is telling you something about how much real influence they have.

• Name the person with actual budget authority.
• Ask your champion directly who else needs to be brought round, and when
• Check whether procurement's role here is to block, to compare, or to negotiate terms after the decision is made elsewhere
• Note anyone who has stopped a similar deal previously, and find out what they objected to

This is groundwork, not diagram-drawing. A map with four boxes and some arrows tells a team what it already believed. A map built from direct answers, updated as those answers change, tells a team something it did not know going in, and that is the version worth having before the pitch.

A stakeholder map is a working record of who in the buying organisation can say yes, who can say no, and who only feels entitled to an opinion. Most pitch teams draw one on a whiteboard once and never touch it again, which is roughly as useful as writing a BATNA (Best Alternative to a Negotiated Agreement) and then never checking whether it has changed. The map earns its keep only if it is built before you present and revised as you learn more.

The exercise starts with a plain question for every name on the account: what can this person actually decide, and what can they only influence? A procurement lead can block a deal by refusing sign-off on terms; they usually cannot approve the spend. A technical champion can get you into the room and argue your case when you have left it; they cannot commit the budget. Confusing influence with authority is the single most common reason a well-received pitch dies quietly afterwards, in a meeting the pitching team was never invited to.

Where the gaps actually appear

The first gap is a missing economic buyer: the person with real budget authority, distinct from the champion or the user, has never been identified, so the whole pitch is built for an audience that cannot approve it. The second is an unmapped blocker, someone with the standing to stop the deal who was never consulted and therefore has no reason to defend it when asked. The third is treating a committee as a single mind, when in practice each member is weighing something different: cost to one, risk to another, credit for the initiative to a third.

None of these gaps show up in the room. They show up two weeks later, in the silence after a pitch that seemed to land well. That gap between a good reception and a stalled decision is usually not a flaw in the material. It is a flaw in the map.

Once you have identified these roles in the buying organisation, you also need to decide who from your team should present to each of them, since not every role responds to the same messenger: the person who wins over an economic buyer is rarely the person who wins over a technical champion. See the right person to sell for guidance on matching presenter to audience.

Filling the gaps before you present

Filling them is mostly a matter of asking, directly. Who signs this off once the room agrees? Who has to be satisfied but will not be in the room? Who has killed a similar proposal before, and why? A champion who cannot answer these questions is telling you something about how much real influence they have.

• Name the person with actual budget authority.
• Ask your champion directly who else needs to be brought round, and when
• Check whether procurement's role here is to block, to compare, or to negotiate terms after the decision is made elsewhere
• Note anyone who has stopped a similar deal previously, and find out what they objected to

This is groundwork, not diagram-drawing. A map with four boxes and some arrows tells a team what it already believed. A map built from direct answers, updated as those answers change, tells a team something it did not know going in, and that is the version worth having before the pitch.

A stakeholder map is a working record of who in the buying organisation can say yes, who can say no, and who only feels entitled to an opinion. Most pitch teams draw one on a whiteboard once and never touch it again, which is roughly as useful as writing a BATNA (Best Alternative to a Negotiated Agreement) and then never checking whether it has changed. The map earns its keep only if it is built before you present and revised as you learn more.

The exercise starts with a plain question for every name on the account: what can this person actually decide, and what can they only influence? A procurement lead can block a deal by refusing sign-off on terms; they usually cannot approve the spend. A technical champion can get you into the room and argue your case when you have left it; they cannot commit the budget. Confusing influence with authority is the single most common reason a well-received pitch dies quietly afterwards, in a meeting the pitching team was never invited to.

Where the gaps actually appear

The first gap is a missing economic buyer: the person with real budget authority, distinct from the champion or the user, has never been identified, so the whole pitch is built for an audience that cannot approve it. The second is an unmapped blocker, someone with the standing to stop the deal who was never consulted and therefore has no reason to defend it when asked. The third is treating a committee as a single mind, when in practice each member is weighing something different: cost to one, risk to another, credit for the initiative to a third.

Once you have identified these roles in the buying organisation, the next decision is who from your team presents to each of them. Not every role responds to the same messenger: a technical champion often wants command of detail and is unimpressed by seniority for its own sake, while an economic buyer is more often persuaded by someone with equivalent standing in the room. See the right person to sell to for guidance on matching presenter to audience.

None of these gaps show up in the room. They show up two weeks later, in the silence after a pitch that seemed to land well. That gap between a good reception and a stalled decision is usually not a flaw in the material. It is a flaw in the map.

Filling the gaps before you present

Filling them is mostly a matter of asking, directly. Who signs this off once the room agrees? Who has to be satisfied but will not be in the room? Who has killed a similar proposal before, and why? A champion who cannot answer these questions is telling you something about how much real influence they have.

• Name the person with actual budget authority.
• Ask your champion directly who else needs to be brought round, and when
• Check whether procurement's role here is to block, to compare, or to negotiate terms after the decision is made elsewhere
• Note anyone who has stopped a similar deal previously, and find out what they objected to

This is groundwork, not diagram-drawing. A map with four boxes and some arrows tells a team what it already believed. A map built from direct answers, updated as those answers change, tells a team something it did not know going in, and that is the version worth having before the pitch.