Start with the reason for the conversation
A discovery call is not a test of how quickly you can pitch your service. It is a chance to learn what the prospective client wants to change, what makes that change difficult and whether you can help. You may only need a few well-chosen questions if you leave room for the client to explain their answers.
Begin with an open invitation: “What prompted you to look for help now?” Then ask, “What would you like to be different when this work is finished?” These questions separate the immediate request from the underlying goal. A client asking for a new website, for example, might be trying to make inquiries easier to handle. That distinction matters when you decide what work to propose.
Understand what happens today
Before suggesting a solution, ask the client to walk you through the current process. “How do you handle this today?” and “Where does the process become difficult?” are more useful than assuming the problem is caused by a missing tool or service. If several people are involved, ask who does what and where work tends to wait for input or approval.
Follow broad answers with requests for examples: “Can you describe a recent instance?” or “What happened the last time you tried to address this?” An example can reveal details that a general description misses. Listen for workarounds, repeated handoffs and parts of the process that already work well. Those strengths may be worth preserving rather than replacing.
Clarify priorities and what success would look like
Clients often have several goals but limited capacity to pursue them all. Ask, “Which outcome matters most?” and “If we could improve only one part first, which would you choose?” This helps you distinguish essential work from ideas that could wait. It also gives the client a chance to correct your interpretation before you build a proposal around it.
Discuss how the client would recognize useful progress. “What would tell you this is working?” may lead to an observable result, such as fewer manual steps or clearer information for customers. Not every project needs a formal metric, but a shared description of success makes it easier to set scope and review the finished work. Avoid promising an outcome that depends on factors outside your control.
Make constraints safe to discuss
Constraints are not objections to overcome; they shape a workable project. Ask about timing, available people, existing systems and required approvals: “Is there a date driving this work?” “Who can provide feedback?” and “What must the solution work with?” If the client mentions a deadline, ask what happens if it moves. A preferred date and an immovable commitment call for different plans.
Budget can be discussed without pressing for a number the client is not ready to share. You might ask, “Have you set a spending range?” or “Would it help to compare a smaller first phase with a broader project?” Explain that the answer helps you recommend a realistic scope. Also ask what has been tried before and whether there are approaches the client wants to avoid.
Close by checking your understanding
Toward the end of the call, summarize what you heard in ordinary language: the main goal, the current difficulty, the highest priority and the key constraints. Ask, “What have I missed or misunderstood?” This gives the client a straightforward opportunity to correct the record. It may also surface an important requirement that did not fit your earlier questions.
Finally, clarify the next decision: “Who needs to review a proposal?” and “What information would help you decide?” Agree on a reasonable next step, such as sending a brief scope or arranging a follow-up with another stakeholder. If the work is not a good fit, say so rather than forcing a proposal. A useful discovery call ends with a clearer picture for both sides, even when it does not lead to a project.
