The questions to ask in a B2B discovery call
Seven questions in a deliberate order, the follow-ups that go with each one, and a way to tell when you have actually got an answer.
A discovery call can feel successful and still leave you with nothing. You liked each other, they talked freely, you agreed to send something over. Then you open the document to write it and find you cannot state what they actually need.
That is not a rapport problem. It is a sequencing problem. Below is the order we use, the questions that go with each stage, and the test for whether an answer has really landed.
What a discovery call is for
A discovery call has one job: to understand the business well enough to know whether you can help, and with what.
It is not a pitch with questions in front of it, and it is not an interrogation. Interrogation collects qualifying facts about the buyer. Discovery builds a picture of how the work currently happens, so that anything you propose later attaches to something real.
One question governs the whole call:
Do we understand the business yet?
If not, keep asking. If so, stop and say back what you heard.
The order matters more than the list
There are a hundred lists of discovery questions available. The list is the easy part. Sequence is what goes wrong.
Ask about business impact before you know frequency and you get a guess. "It costs us a fortune" means one thing at twice a week and something else at twice a year. Ask what a better future looks like before you know what they use today and you get a wish list rather than a description of a gap.
The seven stages run: workflow, pain, frequency, business impact, current solution, decision process, desired future state. Each is only properly answerable once the one before it has landed.
These are the questions from our own recruitment question set, so the wording assumes a recruitment agency. The sequence travels further than the wording does. In a different service business, keep the order and change the nouns.
1. Workflow
Can you walk me through how a vacancy moves from intake to placement today?
Everything else is a property of the workflow. You cannot locate pain, count frequency, or price impact until you know what the process is.
Follow up with: Where does the work change hands? and Which parts happen in email, spreadsheets, or your CRM?
"We use a CRM" is not a step. "The consultant writes the spec in a doc, pastes it into the CRM, then emails the client for sign-off" is a step. Get at least one of those, in their words, before moving on.
2. Pain
Where does that process slow down, repeat, or create admin burden?
This is the question people expect, which is exactly why it works better second. You are pointing at a process you have just heard described, rather than asking a stranger to volunteer their problems.
Follow up with: What causes the delay? and Who feels that pain most often?
You want a problem tied to a specific part of the process, not a general grumble about being busy.
3. Frequency
How often does that happen in a normal week or month?
Frequency turns a complaint into something measurable. It also separates the irritation they mentioned first from the problem worth solving.
Follow up with: Is that steady or does it spike? and How many roles or candidates does it affect?
A frequency, a volume, or an honest "I do not know" all count. The third is a real answer. Record it as an unknown rather than quietly substituting an estimate of your own.
4. Business impact
What happens commercially or operationally when that issue occurs?
This decides whether anything follows. A problem that happens weekly and costs nothing visible is not a project. One that happens monthly and delays a placement is.
Follow up with: Does it affect fill rate, response time, compliance, or revenue? and What is the visible cost?
Either you can state the consequence, or you have established that nobody has worked it out. "We have never measured it" is worth knowing, and worth saying back to them.
5. Current solution
What tools, spreadsheets, inboxes, or workarounds handle this today?
Ask what exists before you discuss what could. The workaround usually tells you more about the real requirement than the complaint did. And if you propose something that duplicates a tool they already pay for, the call is over and you will not be told why.
Follow up with: What works well about the current setup? and Where does it force manual re-entry?
Ask what works, not only what does not. The parts they defend are the parts any change has to survive.
6. Decision process
Who would need to be involved if this process changed?
Deliberately late. Asked early it sounds like qualification and people go guarded. Asked after they have described a real problem, it is a practical question about their own organisation.
Follow up with: Who owns the workflow? and Who would approve a change?
Either you understand who is involved, or you have established that they do not know yet. Both are useful.
7. Desired future state
What would a better version of this workflow look like?
Last, because by now they are improving something concrete rather than imagining a product.
Follow up with: What should be easier for consultants? and What should clients or candidates experience differently?
Repeat their outcome back in their words. If you catch yourself translating it into your own service description, you have stopped listening.
Qualification is a separate job
Understanding the business and qualifying the opportunity are different tasks, and mixing them degrades both. Once discovery has landed, three questions are fair:
- Who else would need to be on board if this moved forward?
- Is there a budget already set aside for this kind of thing, or would it need a case made?
- What is the timeline, is this a this-quarter problem or a someday problem?
All three ask about how they decide, not about whether they like you.
Record what you did not learn
The most useful thing on your pad after a discovery call is often the list of what you still do not know. Three habits protect that list.
Unknown is a valid state. A stage you did not reach is not one you can reconstruct from memory next week. Mark it unanswered and leave it visible.
Contradictions stay contradictions. If the founder says intake takes ten minutes and the consultant says an hour, you have not learned that it takes half an hour. You have learned there is a disagreement, which is often the more interesting finding. Averaging it away produces a confident summary that is wrong.
What they said is not what you concluded. "They said the CRM is fine" and "I think the CRM is the problem" are different kinds of note, and only one of them is evidence.
A template that holds the shape:
What they said:
Contradictions or things that did not add up:
What I concluded (mine, not theirs):
Still unanswered:
Next step agreed:
Follow-up date:
Three things not to do
- Do not promise a timeline you have not costed.
- Do not claim to know their business better than they do.
- Do not oversell. If it is not a fit, say so.
The last is the hardest and the most valuable. A call that ends in an honest "this is not for you" costs you an hour. A project that should never have started costs a great deal more, and it is your reputation that settles the bill.
Why we built Scout this way
Scout is our business-development product for founder-led B2B service firms, and its Discovery Coach is this method rather than a feature bolted beside it. It holds the seven areas, shows which are still unanswered, and keeps what you were told separate from what you concluded.
It does not join, listen to, or transcribe your calls. You run the conversation. Scout is in early access, which is precisely why the questions above are published in full rather than kept behind it.
A note on evidence. These are the questions we built into our own product. They have not been tested through a completed external validation study, no recruitment agency has confirmed they are the best available, and we make no claim that they improve conversion. They are offered as a considered starting order, and the order is the part we would defend.
From LOATY Forge
Scout puts this thinking into a founder-led workflow.
Scout helps founder-led B2B service businesses find suitable prospects, prepare thoughtful outreach, and follow up consistently, while the founder makes every consequential decision.