Every rep has asked a champion the same question near the end of a good call: "Who else should I be talking to?"
And every rep knows the answer. "Let me think about that and get back to you." Or one name, usually the person you already knew about. Or a polite "I will loop in the right people when the time comes", which means you will find out who the right people were when the deal stalls.
There is a better way to get that information, and it starts with being deliberately wrong.
Why "who else should I talk to?" fails
The question looks reasonable. It fails for four reasons.
- It is a blank page. You are asking the champion to picture their whole organisation, work out who matters to this decision and say it out loud, on the spot. That is real work, and most people do not do it well in the last two minutes of a call.
- It feels risky. Naming a colleague feels like volunteering them for sales calls. A champion who likes you still does not want to be the reason their boss got pestered.
- It produces the obvious names. When people recall under pressure, they name whoever is most visible. The quiet finance partner or the security lead with a veto rarely comes to mind first.
- It gives you no structure. Even when you get names, you rarely learn how those people relate to each other, who listens to whom, or who has blocked something like this before.
Being wrong on purpose
There is an old observation, often called Cunningham's law, that the fastest way to get the right answer online is not to ask a question but to post the wrong answer. People who would ignore a question will rush to correct a mistake.
The same instinct works in a sales call. A champion who goes quiet when you ask "who else is involved?" will happily say "no, no, Priya does not report to Daniel, she reports to the CFO, and you are missing Marcus, who runs procurement and will want to see this early."
Correcting something is easy. It takes no preparation and feels helpful rather than risky. The wrong org chart is just a prompt that makes them talk.
How to build the draft map
Your draft does not need to be right. It needs to be specific enough to react to. Spend an hour on it before the call.
Pull from what you can see:
- Public information. The company website, press releases, leadership pages and recent announcements.
- LinkedIn. Profiles and recent job changes for the teams involved, which are usually the best starting point for titles and tenure.
- Job postings. They often show which teams are growing, who they report to and which tools they use.
- Your own history. CRM notes, past deals with the account and anything your colleagues remember.
- Your network. Customers, investors and partners who know people at the account and can tell you how it is organised.
Then sketch it on one page. Use simple boxes for the roles that usually appear in a decision like yours: the likely economic buyer, your champion, technical evaluators, finance, procurement, security, legal and the team that will use the product. Draw the reporting lines as you best understand them.
Where you are unsure, guess, and mark the guess. A question mark next to a name is an invitation. Keep the design rough. A map that looks finished and polished invites approval. One that looks like a sketch invites edits.
How to run the call
Frame it honestly. "I have tried to sketch how I think this decision gets made on your side. I am sure parts of it are wrong. Would you mind fixing it with me?" You did your homework, but you are not claiming to know their company better than they do.
Share it on screen. Keep the map in the call rather than sending it around. You want a conversation, not a document they file for later.
Walk it from the top. Start with the senior roles and work down, pausing on each box to let them react.
Ask follow-ups that a blank page never would:
- "Who does she listen to before she makes a call like this?"
- "Who would be upset if they heard about this late?"
- "Has anyone here said no to something similar before? Why?"
- "Who is missing entirely?"
Edit live. Move boxes and add names while they watch. It shows you are listening.
Close with one question. "Of the people we just added, who should I understand first, and what is the best way to get to them?" Now you are asking for a specific next step, not a list.
What to do with the corrections
The corrections are the most valuable output of the call, so act on them the same day.
- Update the map and keep the champion's version as the source of truth. Note what changed from your draft.
- Use reporting lines for sequencing. Knowing who reports to whom tells you which conversations need to happen first and who will hear about you from whom.
- Use the "who matters" signals for priority. The person the champion described as the real decision maker gets more attention than the most senior title on the page.
- Treat every new name as a thread to build. Add them to the account plan with a reason to meet them.
- Give each relationship an owner. Decide who on your team should reach each person, using jersey matching so a peer covers each seat.
- Plan your whisper calls. Some of the people the champion added sit below or beside the executive. Short whisper calls with them will sharpen your point of view before the senior meeting.
Turning the map into meetings
A corrected map is only useful if it becomes meetings. This is where warm paths matter.
For each person you are missing, look for someone on your side who already knows them: a colleague who worked with them, a customer whose team overlaps with theirs, an investor or partner with a connection. A short introduction from someone they know gets a reply far more often than a cold note.
Be careful with your champion's goodwill. Ask them for an introduction only where they are clearly the best person to make it. For everyone else, use your own warm paths, so the champion is not spending their reputation on every connection. And make every ask specific: who, why them, why now and what you hope to learn. We cover how to build asks like that in why customer referral programs fail.
Warm, well-routed introductions are what turn a map into pipeline. 1mind closes nearbound deals at three times the rate of outbound (case study). For a fuller playbook on building relationships across a buying group, see our multithreading ebook.
The risks
This technique works because it builds trust. Two rules keep it that way.
Never present the map as fact. Call it a draft, say where you guessed and invite corrections from the start. A map presented as accurate makes the champion feel watched, and a map that shows personal details beyond names, roles and reporting lines makes it worse. Keep it to the professional picture.
Never share it outside the call. The corrected map contains your champion's private read on their colleagues: who has influence, who is a blocker, who is missing. That is confidential. Do not email it around, do not paste it into a deck for the executive meeting and never show it to anyone else at the account. If a colleague at the buyer ever sees what the champion told you, you lose the champion.
Where Boomerang fits
Boomerang AI helps at both ends of this. Before the call, Rudy, our AI agent, maps who on your team, among your customers, investors and partners knows people at the account, which gives you a stronger draft to bring. After the call, he finds warm paths into the people your champion added, routes each ask to whoever owns the relationship and drafts the note in their voice. The relationship owner approves and sends it; Rudy never sends anything on anyone's behalf.
To see the warm paths into your target accounts, book a demo or start free.
Frequently asked questions
What is Cunningham's law, and how does it apply to sales?
Cunningham's law is the observation that people are quicker to correct a wrong answer than to answer a question. In sales, it means a champion who goes quiet when asked "who else should I talk to?" will often correct a draft org chart in detail, revealing reporting lines, influence and missing stakeholders.
Why does asking a champion "who else should I talk to?" fail?
It asks them to build a map of their organisation from memory, on the spot, and it feels like volunteering colleagues for sales calls. The usual result is one obvious name or a promise to follow up later.
What should a draft power map include?
The roles likely to be involved in the decision (economic buyer, champion, technical evaluators, finance, procurement, security, legal and end users), the reporting lines as you understand them, and clearly marked guesses where you are unsure. Keep it to one rough page.
Should you send the draft org chart to your champion before the call?
It is better to share it on screen during the call. You want a live conversation and edits as you go, and keeping the map in the call means it does not get forwarded inside the account.
How do you turn the people your champion adds into meetings?
Look for warm paths: someone on your side who already knows each person. Ask your champion for introductions only where they are clearly best placed, use your own colleagues, customers, investors and partners for the rest, and make every ask specific about who, why and why now.




