An organisation chart tells you who reports to whom. It does not tell you who will decide whether your software gets bought. In large companies, purchases are shaped by a group of people with different jobs, different worries and different amounts of influence, and the person with the grandest title is not always the one who matters most. A power map is a seller’s working picture of that group.
A buying committee in practice
Picture a mid-sized private bank evaluating a new customer onboarding platform. The seller’s first contact was the head of digital banking, who is enthusiastic. Over a few weeks, other people appear:
- The chief information security officer, who worries about where customer data will be stored and how the vendor will be audited.
- The CFO’s office, which wants to know whether this replaces existing spending or adds to it.
- The head of operations, whose teams currently process applications manually and who will own the change.
- An enterprise architect, who prefers extending the bank’s existing core platform rather than adding a new vendor.
- Compliance, which must confirm the platform supports KYC requirements under the regulator’s directions.
- Procurement, which will run the commercial process.
Each of these people can slow or stop the deal. Each wants something different: digital wants speed, security wants control, finance wants savings, the architect wants simplicity. A seller who keeps talking only to the enthusiastic first contact is likely to be surprised.
What to record about each person
A useful power map captures a few attributes for each stakeholder, kept brief enough to update after every meeting:
- Role in the decision. Common labels include economic buyer (the person who can release the budget), champion (an insider who actively sells on your behalf), technical evaluator, end user, influencer, and gatekeeper such as procurement or legal.
- Influence. How much weight their view carries, regardless of title. A trusted senior architect may outweigh a vice president who joined last month.
- Stance. Supporter, neutral, sceptic or opponent, towards your solution specifically.
- What they care about. Their personal and professional stakes: a target they are measured on, a risk they fear, a project they own.
- Relationships. Who listens to whom, who has worked together before, who competes for the same budget.
- Coverage. Who on the selling team has a relationship with them, and how recent the last real conversation was.
The most common visual is a simple grid with influence on one axis and stance on the other. High-influence opponents in one corner and high-influence supporters in another give an immediate sense of where the deal stands.
Reading the map
Back to the bank. After a month, the seller’s map shows the head of digital as a high-influence supporter, the head of operations as a neutral with moderate influence, the CISO as a high-influence sceptic, and the enterprise architect as an opponent whose views the CIO respects. The CFO’s office has not been met at all.
Three conclusions follow. First, the deal currently rests on a single champion, which is fragile; if the head of digital changes jobs, the opportunity may vanish. Second, the CISO’s concerns are specific and answerable: data residency, audit rights, certifications. Addressing them early, through a session with the vendor’s own security team, could turn a sceptic into a neutral. Third, the architect’s opposition is about strategy, not features. Arguing with him directly may harden his position. A better approach might be to understand his preferred alternative honestly, work out what it would cost and how long it would take, and let the bank compare the two on its own terms.
Conflicting priorities are normal
When IT wants security, finance wants savings and the business wants speed, the instinct is to tell each group a different story. That tends to fail, because the committee eventually meets in one room and compares notes. A sturdier approach is to build one storyline that acknowledges every concern and shows how the trade-offs are handled: a phased rollout that delivers early wins for the business, a security model the CISO’s team has reviewed, and a cost profile that finance can see replacing existing spend over time. Each stakeholder hears their priority addressed, and they hear the others’ priorities addressed too, which makes internal agreement easier.
Where power maps go wrong
Mistaking friendliness for support. A contact who takes every call and praises the demo may have no influence or no intention of spending political capital. A real champion does things: introduces you to the economic buyer, shares internal information, tells you about risks.
Mapping titles instead of influence. Influence comes from expertise, track record, ownership of the budget and relationships with the decision-maker. These are discovered by asking questions such as “Who else will weigh in on this?” and “When the last major platform was chosen, how was that decision made?”
Letting it go stale. Reorganisations, resignations and new priorities change the map. An entry that says “supporter” based on a meeting three months ago is a guess.
Treating it as a manipulation tool. The purpose of a power map is to understand who needs what to make a good decision, and to make sure their questions are answered. Sellers who use it to play stakeholders against each other usually get found out, and in a large account that reputation follows them into every future deal.
A final point: the power map belongs to the deal team, not to one individual. Solution engineers, executives and partners often know stakeholders the account executive has never met. Building the map together, and reviewing it in deal reviews, catches blind spots before they become losses.
Written by the RP Strativa Team. The bank and stakeholders in the example are illustrative.
Leave a Reply