You run a perfect discovery call. You uncover deep pain, map the gap, and leave with the buyer excited. You write a strong proposal. Then nothing, two weeks of silence, followed by “we’re still evaluating.” What happened? You didn’t know that the person you spoke with needs CFO approval for any engagement over $5,000, and the CFO has never heard your name. The decision-process mapping questions fix that.
The Real Buyer Problem
The Challenger Sale research, conducted by Gartner across thousands of B2B purchases, found that the average buying decision involves 6.8 stakeholders. In freelance and small-to-medium B2B sales, that number is lower, but it’s rarely one person.
The “real buyer” is not simply the person with the most interest in solving the problem. It’s the person (or combination of people) who can say yes, allocate budget, and make the engagement happen. Your discovery contact is often the most interested party, but not always the one who controls the decision.
The 7-question decision-process sequence is designed to map the full decision landscape without making your contact feel interrogated or doubted. The tone is collaborative process-curiosity: “I want to understand how this works so I can make this easy for you”, not “I need to verify that you’re actually important.”
Question 1, The Process Question
“How does your organization typically handle vendor decisions for work like this?”
This is the entry point. The word “typically” is doing important work, it invites a description of process, not a defense of authority. Most buyers can answer this easily, and the answer immediately tells you whether there’s a formal process (procurement, legal review, competitive bids), an informal one (founder decision, team discussion), or no process at all (which usually means whoever champions the decision hardest wins).
Question 2, The Stakeholder Question
“Who else tends to get involved when a decision like this is being made?”
Note the framing: “tends to get involved” (process language) rather than “needs to approve” (authority language). The first invites description. The second invites defensiveness.
Common answers: “Just me,” “me and the CEO,” “I’ll need to loop in our CFO for anything over X,” “our procurement team will need to be involved,” “the full leadership team weighs in on this kind of spend.”
Each answer gives you a different proposal strategy. A solo decision-maker gets a direct proposal. A multi-stakeholder decision gets a proposal with an executive summary and a section that addresses financial ROI for non-technical readers.
The most dangerous answer to the stakeholder question is “just me” when it isn’t true. Buyers sometimes overstate their authority, either because they believe it or because they want to seem important. Your follow-up questions (especially Question 5 about budget thresholds) are your backstop against this.
Question 3, The Criteria Question
“When a decision like this gets evaluated, what are the things that matter most to the people involved?”
This question surfaces evaluation criteria that may differ by stakeholder. Your champion might care most about quality and timeline. The CFO might care most about ROI and risk. The founder might care most about strategic fit.
The answer to this question directly shapes your proposal’s argument structure. If the CFO cares about ROI, your proposal needs an ROI section. If legal cares about contract terms, your proposal needs a clear scope and IP clause. Proposals that speak to the evaluation criteria of all stakeholders close faster than proposals that only speak to one person’s priorities.
Question 4, The History Question
“Has your organization worked with freelancers or external partners on projects like this before? How did that go?”
The history question reveals two things: the baseline expectation and the risk profile. A company with a good track record with external partners is easier to close, they have a reference point for success. A company with a bad track record is harder to close but higher-value to get right, because trust in the category is low and a positive experience is memorable.
The “how did that go” probe surfaces previous failures, which are the organizational ghosts that will haunt your proposal. If they had a bad experience with a freelancer before, address that experience directly in your proposal. Don’t ignore it hoping they’ve forgotten.
Question 5, The Budget Approval Question
“Is there a budget approval step for engagements at this level, or is that something you manage directly?”
This is your authority verification question, phrased without challenging authority. The question acknowledges the possibility that they manage budget directly (which flatters the legitimate decision-maker) while also opening the door to the approval-required scenario.
Common answers: “I have authority up to $X, anything above that needs sign-off,” “this would go through normal procurement,” “it’s my call,” “I’d need the founder to sign off on any external spend.”
Now you know the real approval threshold and the real approver.
Question 6, The Competitive Question
“Are you evaluating other options, or is this more of a direct search for the right fit?”
You need to know if you’re in a competitive evaluation. Competitive evaluations require different proposals, shorter, faster, with clearer differentiation. Non-competitive searches allow for more collaborative, consultative proposals.
“Are you evaluating other options” is less threatening than “am I the only one you’re talking to”, the first is a process question, the second sounds needy. The answer is equally useful and the framing is more professional.
Question 7, The Timeline Question
“What does the timeline look like for making a decision, and what’s driving that date?”
The timeline question closes the decision-process map. It tells you two things: how urgently they want to move, and why. A decision that needs to be made by month-end because of a budget cycle is a different situation from a decision that “would be nice to make in the next few weeks”, one has a hard deadline, one doesn’t.
The “what’s driving that date” follow-up is essential. Deadlines without causes are weak. Deadlines with causes, “we need this running before our product launch,” “we have to show results by the board meeting”, are hard constraints that produce real urgency.
Writing the Multi-Stakeholder Proposal
After running the 7-question decision-process sequence, you have a map: who decides, who influences, what criteria they each care about, whether there’s a competitive process, and what the timeline looks like.
Use it. Structure your proposal to address each stakeholder explicitly. An executive summary for the decision-maker. A scope section for the champion. An ROI section for the financial gatekeeper. A risk/process section for legal or procurement.
Proposals that speak to every voice in the room don’t just close faster, they close at higher values, because the people who control budget see their concerns addressed before they have a chance to raise them.
