A box whose lid is held shut by four different latches, one of them opened and the other three still closed.

6of 7

Map every stakeholder for B2B sales

The person using a product may not be the person paying for it or approving its adoption. Map who is involved, what each person needs and whose perspective could change your assessment.

Build & Validate
Customer discovery

By the EWOR Team2 min read

Your conversations with potential customers are going well. The people using the product are enthusiastic, the problem sounds painful and the value seems obvious. Then you discover that another department controls the budget, the IT team must approve the integration or managers will have to take on extra work to make the solution viable.

Suddenly, a promising opportunity looks more complicated.

Before settling on a problem statement, find out who else is involved and how the change would affect them. You do not need to interview everyone in the organisation. You do need to understand whose needs, decisions or concerns could make or break adoption.

Map responsibilities, not just job titles

Who does the work? Who relies on the result? Who pays, approves the purchase, implements the change or keeps things running afterwards? Include people affected indirectly, even if they have no say in the buying decision.

Job titles alone will not tell you how decisions happen. Ask someone to walk you through a recent purchase or workflow change. Who was involved, and what had to happen before the decision could move forward?

Keep the evidence for each role separate

Consider a field-service business. Technicians want less reporting, managers need reliable records, and the implementation team wants to avoid maintaining another integration. A product that makes life easier for technicians could still struggle if it creates more work for everyone else.

Record what each stakeholder needs, what burdens they face and how much influence they have. Keep direct feedback separate from secondhand accounts, and do not treat an unverified concern as an established fact. Store participant contact details separately with appropriate access controls.

Find the gap that matters

You will rarely have the full picture after a few conversations. Focus on the unanswered questions most likely to change your assessment. Is there a budget? Is a requirement mandatory? Would implementation create too much work?

Seek permission-based introductions to the people best placed to answer. Do not assume senior sponsors understand frontline frustrations, or that daily users know every procurement requirement. You also do not need to interview every department. Follow the evidence and expand your research when another stakeholder could affect adoption.

Give people room to speak honestly, sometimes without their manager present, so they can discuss problems without feeling pressured to give the expected answer.

Keep conflicting needs visible

Stakeholders will not always agree, and that is useful information. If one team wants speed while another needs stricter controls, document the trade-off rather than turning their views into one artificial customer need.

Distinguish formal requirements from established practices and individual expectations. Use the map to decide whom to speak with next, narrow your target customer or identify what still needs validating. An uncontacted stakeholder has not confirmed your assumptions, and a complete-looking map does not mean an organisation is ready to buy.

No comments yet.

Be the first to comment on this signal.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter

Continue learning

Related modules