The person on your discovery call is rarely the whole story. Behind them is a network of influencers, approvers, skeptics, and beneficiaries, and the deal will be won or lost based on dynamics you never see if you don’t map them in real time.
Why Discovery Maps the Organization, Not Just the Problem
Trish Bertuzzi’s Sales Development Playbook opens with a warning that applies equally to freelancers: most deals that die late in the sales cycle, after a proposal has been submitted, often after verbal approval, are killed by a stakeholder nobody mapped.
The VP of Engineering who wasn’t on the discovery call. The CFO who was never briefed on the initiative. The department head whose team will be displaced by the new process. These are the stakeholders who kill proposals that seemed locked.
The stakeholder map built during discovery is your defense against late-stage ambush. It’s not a perfect intelligence document, it’s a working hypothesis of who matters, updated in real time as you learn more.
The Four-Box Framework
Draw a two-by-two grid on paper or in your Waco3 notes before the call starts. Label the boxes:
Box 1: Champion, The person who wants this solved and will advocate for it internally. Often the person you’re speaking to, but not always. Champions have a personal stake in the outcome and will do internal selling on your behalf if you equip them well.
Box 2: Signer, The person with budget authority. May be your champion; often isn’t. The signer’s concerns are usually financial risk, organizational fit, and precedent. They ask: “Is this the right use of this money?”
Box 3: User, The team or individual who will live with the solution. Users care about implementation friction, workload, and workflow compatibility. Unhappy users kill implementations even after the check clears.
Box 4: Blocker, The person who is skeptical, threatened, or opposed. Blockers can be overt (the CTO who doesn’t believe in external consultants) or structural (the internal team whose work will be replaced or complicated by your engagement).
As the buyer talks, fill in names and relationships. You won’t fill all four boxes in every call, but you should leave every call with at least a hypothesis for each.
A deal with a champion who is not the signer is a two-step process: you sell to the champion, and then you help the champion sell internally. If you don’t know this going into the proposal, you’ll write for the wrong audience.
The Questions That Fill the Boxes
These four questions surface the map without making the buyer feel like they’re being interrogated. Each is framed as due diligence, which it is.
To map the field: “Who else at your company would need to be involved in a decision like this?”
This opens the map. Most buyers will name two to four people. Listen for job titles, departmental allegiances, and how they’re described (warmly, cautiously, or with a qualifier like “he’ll need some convincing”).
To find users and blockers: “When something like this gets implemented, who’s most affected, both the people who’d benefit and the people it might create more work for?”
This question surfaces users by implication and blockers by acknowledgment. Buyers who have a blocker in mind will usually name them here, often as “there’s one person who…” Follow up: “Tell me more about where she’s coming from.”
To find the signer: “When a decision with this kind of investment gets made, who ultimately has to sign off on the spend?”
Don’t ask “are you the decision-maker?”, it’s a yes/no question that often gets a misleading yes. This version surfaces the process, not just the person, and gives you more useful intelligence.
To test the champion: “On a scale of urgency, where does this fall for you personally, is this something you’re driving, or something you’ve been asked to explore?”
A true champion is driving. A proxy, someone who was sent by the real champion, is exploring. The distinction matters enormously for how you structure the proposal and follow-up.
Drawing the Relationships
The boxes matter less than the arrows between them. After you’ve named the four roles, sketch the relationships:
Does the champion have direct access to the signer, or do they need to go through a layer? (More layers = more proposal summary work needed.)
Is the blocker in the same reporting line as the champion, or in a parallel function? (Parallel blockers are usually manageable; direct blockers are more serious.)
Does the user group have any voice in the final decision, or are they purely downstream? (User resistance can kill implementation even if the signer approves.)
These relationships tell you where the persuasion work actually lives, and that tells you where to invest your proposal and follow-up energy.
How to Use the Map Post-Call
The stakeholder map is a proposal engineering tool. Every name in a box is a decision you need to make about how to address them.
For the champion: Make the proposal easy to socialize internally. Include an executive summary they can forward. Offer a 15-minute call to walk them through the proposal before it goes to the signer.
For the signer: Anticipate financial and organizational risk questions. Include a ROI framing, a risk mitigation section, and a clear answer to “what happens if this doesn’t work?”
For users: Include an implementation section that acknowledges their workflow and reduces their concern about disruption. If you can reference their perspective specifically, “your customer success team” rather than “the team that will use this”, it signals attentiveness.
For blockers: If the blocker’s concern is identifiable, they were burned by a past vendor, they believe the problem can be solved internally, address it directly and specifically in the proposal. “You may be asking why an external engagement rather than an internal solution…” is a line that signals you’ve done your homework.
The stakeholder map isn’t a document you share, it’s a navigation tool you use. Every section of your proposal, every follow-up email, every check-in after submission should be oriented toward the specific people on that map and what they need to say yes.
When the Map Is Incomplete
Some buyers are protective of their organizational dynamics, especially in the first call. If the map is sparse after minute 25, you have two options.
Option 1: Ask the champion question directly. “I want to make sure the proposal is designed to work for everyone who matters here. If I were building a list of people whose concerns I’d want to address, who should be on it?”
Option 2: Acknowledge the gap in the proposal itself. “As you review this, I’d love to know if there are specific concerns from other stakeholders I should be building into this, I’ve seen proposals succeed or stall based on people I didn’t know to address.”
Neither option is a failure. Incomplete maps are common in single-call discovery. The goal is to know what you don’t know, and to keep filling the boxes.
