Discovery Call Questions That Lead to Proposals That Close
A proposal is only as good as the discovery behind it. Most proposals fail not because they're badly written — they fail because the consultant didn't extract the right information before they started writing. The proposal becomes a description of services rather than a case for a specific investment.
Three things make a proposal compelling enough to approve without negotiation. None of them can be invented after the call:
01
Quantified problems
Every issue attached to a dollar cost — not a description of pain, but a number the client agrees to
02
Value drivers
The 2–4 strategic themes that connect their problems to your solution's logic — the "why this, why now" structure
03
Price justification
Your fee as a percentage of the value they agreed is at stake — not a number you made up based on your rate
The questions below are organized to extract these three things from any discovery conversation. Use them in order, skip the ones that don't apply, and treat every answer as a data point you'll later turn into proposal copy. For the full discovery process — including how to structure the call, uncover budget, and use AI to prep beforehand — see the Discovery Call Framework.
Print this page to use as a call reference — it formats cleanly without the navigation and CTAs.
Before the call: the three things to research
Don't start cold. Spending 15 minutes on this before the call lets you ask sharper follow-up questions and signal competence from the opening.
Their revenue and headcount — gives you an order-of-magnitude sense of what problems cost at their scale, so you can sanity-check any estimates they give you
Their industry's cost benchmarks — know the typical denial rates, overhead ratios, or CAC ranges for their sector before you ask about theirs
What they've already tried — check their job postings, LinkedIn, and case studies; if they hired someone for this problem 18 months ago, that's context you want before minute one
Opening the call: set the frame
The first two minutes determine whether this is a discovery call or a sales pitch. Make it clear you're diagnosing before prescribing.
1
"Before I tell you anything about how I work — can you tell me what made you reach out now, specifically? What changed?"
Why: Surfaces the triggering event. "Now" is always more specific than "we have this problem" — the timing tells you whether there's real urgency or just vague interest.
2
"What would a great outcome from this conversation look like for you?"
Why: Tells you what they came to get. If they say "understand your services" they're browsing. If they say "decide whether to move forward" they're buying.
Problem quantification: turning pain into numbers
This is the most important section of the call. Most clients can describe their problems; very few have attached a cost to them. Your job is to help them arrive at a number they believe — not one you impose.
Rule: Never state a cost estimate first. Ask questions that lead the client to calculate it themselves. A number they arrive at is one they'll defend in the approval meeting. A number you give them is one they'll argue with.
3
"Walk me through what actually happens because of this problem — specifically, who's affected and what doesn't get done that should?"
Why: Opens the problem space without anchoring on a solution. Listen for headcount, hours, and frequency — these are your cost inputs.
4
"How many people does this touch? And roughly how much of their week does it eat up?"
Why: Lets you calculate labor cost: headcount × hours/week × fully-loaded hourly rate × 48 weeks. Even rough numbers give you a defensible floor estimate.
5
"If you had to put a number on what this is costing you annually — even a rough guess — what would you say?"
Why: Gets the client to state a cost. If they deflect ("hard to say"), follow with: "Okay, let's work it out together — how many people, how often…"
6
"What's the cost of doing nothing? If this problem isn't fixed in 12 months, what does that look like for the business?"
Why: Surfaces the cost of inaction — often larger than the cost of the problem itself. Clients who can articulate this are far easier to close.
7
"Is this the only problem, or is it connected to other things that aren't working?"
Why: Expands the problem surface. Most clients come in with one stated problem; the adjacent ones are often where the real cost lives.
8
"What would it mean for the business — in revenue or cost terms — if this worked the way it should?"
Why: Flips from problem cost to opportunity value. Some clients respond better to upside framing than cost elimination.
These answers become your Economic RoadmapProposalCraft's generator takes the problems and costs you just collected and structures them into the Value Driver framework automatically.
Value driver questions: connecting problems to strategy
Value drivers are the 2–4 themes that group the client's problems into a coherent narrative. They answer: "why does fixing these things matter strategically, and why does it matter now?" You're listening for the word "because" — the causal chain that connects a problem to a business outcome.
9
"If you had to pick one problem that's driving all the others — what would it be?"
Why: Identifies the root driver. Most surface-level problems share a single upstream cause; your solution should address that, not the symptoms.
10
"Why is this a priority now versus six months ago? What changed?"
Why: Reveals the strategic trigger — a board mandate, a new competitor, a compliance deadline, a growth target. This becomes the urgency frame in your executive summary.
11
"When you imagine this fixed — what does the business look like differently? What can you do that you can't do now?"
Why: Gets the client to articulate the strategic upside in their own words. Use their language verbatim in the proposal — it's more persuasive than yours.
12
"How does this connect to the company's goals for the next 12–18 months?"
Why: Links your engagement to the strategic plan — the thing the approver cares about. Proposals that can't answer this question get deprioritized.
History and context: what's been tried
This section tells you what not to propose and what language to avoid. It also surfaces the real objection — usually "we tried this before and it didn't work."
13
"What have you already tried to fix this? What happened?"
Why: Tells you what not to propose. Also surfaces the failure mode your engagement needs to explicitly account for — usually change management, not the technical solution.
14
"Have you worked with consultants on something like this before? What did they do well, and what fell flat?"
Why: The most direct insight into what this client buys. Their answer tells you how to position your approach and what risks to address in the proposal.
15
"Is there an internal person or team who owns this problem? How are they feeling about bringing in outside help?"
Why: Surfaces the internal politics. A resistant internal owner can kill implementation even after the proposal is signed. Knowing this lets you design around it.
Budget, timeline, and decision: the commercial questions
These feel uncomfortable to ask early. Ask them anyway — near the end of the problem section, not as a preamble. A client who won't engage with these questions at all is not ready to buy.
Framing tip: Don't ask "what's your budget?" — it sounds like you're asking how much you can charge. Ask "what investment range have you set aside for this?" or "what does success need to cost to still make sense?" These questions get real answers.
16
"What investment range have you set aside for this — or is that still being figured out?"
Why: Gives you the pricing anchor. If they say "we haven't set a number yet," follow with: "What would need to be true about the ROI for this to be an easy yes?" That gets you the real ceiling.
17
"Who else is involved in making this decision? Is this something you decide, or does it go to a committee or board?"
Why: Maps the approval chain. If there's a committee, your proposal needs to be written for someone who wasn't on the call — which means more context, cleaner structure, and explicit ROI.
18
"What's your timeline for making a decision? And separately — when does the work need to be done by?"
Why: Distinguishes decision urgency from project urgency — they're often different. A hard project deadline creates urgency; no deadline means the proposal can drift.
19
"What would make you not move forward with this, even if the proposal looked good on paper?"
Why: The most valuable question in the set. Surfaces the real objection before you've written a word — so you can address it in the proposal rather than discovering it in a "we're going in a different direction" email.
Closing the call: what to leave with
Don't end a discovery call without committing to a next step and confirming what you heard. A verbal summary at the end does two things: it lets the client correct any misunderstanding, and it gives you permission to quote their words back to them in the proposal.
20
"Let me make sure I've understood this correctly — you're dealing with [X], which is costing you roughly [Y], and the priority is to [Z] by [timeline]. Is that a fair summary?"
Why: Forces a verbal confirmation of your problem/cost/timeline understanding. If they correct you, update your notes immediately. If they agree, this is the opening of your executive summary.
21
"Is there anything you were hoping I'd ask about that I didn't?"
Why: Catches anything the client wanted to surface but didn't get a natural opening for. Often the most important thing they say in the whole call.
22
"I'll put a proposal together based on what you've described. Can we book 30 minutes in [X days] to walk through it together — so you can ask questions rather than reviewing it alone?"
Why: Locks in the presentation meeting before you've written a word. Proposals reviewed without the consultant present close at a fraction of the rate of presented proposals.
Turning your notes into a proposal
After the call, you have raw material: problem descriptions, rough cost estimates, strategic context, timeline, budget range, objections. The next step is converting that into the three components a proposal needs — and this is where most consultants lose momentum.
The structured approach:
List every problem mentioned with its cost (use the client's estimate, or calculate from the headcount/hours data you collected)
Group the problems into 2–4 value drivers — the strategic themes that give your solution structure (see: Economic Roadmap)
Set your fee as a percentage of total problem value — typically 8–25% of the annual cost identified, depending on scope and timeline
Write the executive summary last — one sentence each: situation, core problem + cost, what you're proposing, outcome at 12 months