The discovery call is the most leveraged 45 minutes in a consulting practice. A good discovery call surfaces the real scope of the engagement, the real budget, the real decision authority, and the real probability of close. A bad discovery call produces a 3-page proposal aimed at a problem the client wasn't actually trying to solve.
This is the working set of 12 questions that turn a discovery call into actionable proposal input.
Open the call with structure, not small talk
The first 90 seconds of the call sets the tone. Don't open with "so tell me a little about your business" — that's an interview question for someone who hasn't done their homework. Open instead with: "Before this call I looked at [X public information about their situation]. The reason I wanted to talk is [Y specific hypothesis]. Did I get that right?"
This signals that you came prepared, anchors the conversation around your hypothesis, and invites the client to correct your framing. The conversation goes uphill from there.
The 12 questions
Question 1: What's the problem you're trying to solve?
Not "what does your business do," not "what do you need from a consultant." The specific problem they're trying to solve. Listen for whether they describe it as a state ("we're not growing fast enough"), an event ("our COO left in November"), or a decision ("we're trying to decide whether to enter the X market"). Each requires a different engagement structure.
Question 2: When did this become urgent enough to consider hiring someone?
The answer tells you whether this is a real engagement opportunity or research. "Last quarter" usually means a budget exists. "We've been thinking about it for a while" usually means you're educating, not selling.
Question 3: What have you already tried?
Surfaces both the maturity of their thinking and the things you should not propose. If they've already tried internal task forces, a fractional executive, and a Big Four study, your proposal needs to credibly do something those didn't.
Question 4: Who else have you talked to?
You will be benchmarked. Ask who is in the consideration set so you understand the comparison. The answer also tells you their procurement style — informal one-conversation buyer vs. structured RFP.
Question 5: Walk me through how you're thinking about the decision.
A discovery call is part hypothesis-testing and part procurement audit. This question reveals whether the buying process is "the person on this call decides," "we'll bring a recommendation to the CEO," or "this goes to a committee in March." Each requires a different proposal length, tone, and follow-up.
Question 6: What does success look like at the end of this engagement?
The single most important question. Listen for how concretely they answer. "We'll know what to do next" is vague. "We'll have a board-ready recommendation with three options" is concrete. Push gently until you get concrete — vague answers produce vague engagements.
Question 7: What's the cost of not solving this?
The answer is the upper bound of your engagement value. If they say "we'd miss the Q4 market window," they're telling you the engagement is worth a meaningful percentage of Q4 revenue.
Question 8: Is there a budget for this?
Ask directly. Most consultants flinch from this question; the clients who flinch back are the ones who weren't going to buy anyway. The good answers fall into three buckets: a specific number, a range, or "no specific budget but we know roughly what this category costs." All three are useful; "we don't want to limit you" is the answer to worry about — it usually means there's no budget at all.
Question 9: Who else needs to weigh in on this decision?
Surfaces hidden veto holders. If your sponsor is the VP of Strategy but the CEO has final say on consulting engagements over $50K, you need to know that now. Better yet — get on the CEO's calendar before proposing.
Question 10: What's your preferred timeline?
Not "when can we start" — their preferred timeline. The gap between "we'd like to start in two weeks" and "we're hoping to have something done by EOY" tells you the engagement structure (long arc vs short sprint) and your competition (other consultants who have capacity in their timeline).
Question 11: What would make you not move forward?
The killers. Listen for: "we'd need to feel confident about [X risk]" or "we'd want references from [Y type of client]." These tell you exactly what your proposal and follow-up need to address.
Question 12: What happens after this call?
Ends the call with structure. Specify the next step (a written summary by Friday, a proposal by Tuesday, another conversation with the CTO) and confirm both parties are aligned on it. Discovery calls that end with vague "we'll be in touch" reliably go nowhere.
What to do in the 24 hours after
Send a short written recap the same day: "Here's what I heard, here's what I think the right engagement structure looks like, here's what I'd propose to send by [date]." This does two things: it confirms you actually listened, and it lets the client correct any misunderstanding before you spend hours building a proposal aimed at the wrong target.
The recap is the cheapest insurance policy in your sales process.
Why this works
Most consulting proposals lose not because the proposal was bad but because the discovery was thin. The proposal could only be as good as the input. A disciplined discovery call — even 12 questions of it — turns the proposal from a guess into a tailored response.
Ready to manage your sales pipeline, discovery notes, and proposals in one place? Start your free trial and see how ConsultBase keeps lead conversations, proposals, and engagements connected.