Make Discovery Calls Useful Before You Write a Proposal

A discovery call should leave both sides with a clearer understanding of the problem. It should not feel like a presentation interrupted by a few qualifying questions. The customer brings knowledge of the situation. You bring experience with the type of work being considered. The conversation is useful when those perspectives come together without either party pretending to know more than they do. A proposal should follow that understanding, rather than become a substitute for it.

Prepare by identifying what you already know and what you are assuming. Review the inquiry and any relevant information the prospect has shared. Write down a small number of questions that would materially affect your recommendation. Avoid collecting information simply because a form has a field for it. If you cannot explain how an answer changes the scope, timing, or approach, it may not belong in the first conversation. Keep space for questions you cannot anticipate.

Begin with the customer's account of the situation. Ask what prompted the conversation and what they want to be different. Let them describe the issue before offering your interpretation. Follow concrete details: when the problem appears, who encounters it, what happens next, and what has already been attempted. An abstract complaint such as “communication is poor” becomes more useful when the customer describes a specific missed handoff and its consequences. That example gives both sides something to examine.

Separate symptoms from possible causes. A delay may arise from missing information, unclear responsibility, unrealistic expectations, or several connected issues. You do not need to diagnose everything during the call. You do need to avoid committing to a remedy before understanding the situation well enough. State a hypothesis as a hypothesis. Explain what evidence would support it and what additional work might be needed. A careful question can be more valuable than an immediate answer.

Explore the conditions around a decision. Ask who needs to participate, what resources are available, and whether another initiative affects the schedule. Discuss how the customer would recognize a useful outcome. A deadline deserves context: is it tied to an event, an internal commitment, or simply a preference? These questions help establish a realistic engagement. They also reveal when the person on the call needs help bringing other participants into the conversation before a proposal can be meaningful.

Before closing, summarize the situation in plain language. Describe the problem as you understand it, the consequences the customer identified, and the questions that remain open. Invite corrections. Then explain the next step and why it is appropriate. That step might be a proposal, a technical review, a second conversation with another stakeholder, or a decision not to proceed. Avoid treating a calendar invitation as progress unless it advances a specific question or decision.

Afterward, review your own questions. Notice which answers changed your understanding and which questions consumed time without helping either side make a clearer decision about the work.

Send a concise written recap that preserves the substance of the discussion. Include agreed facts, open questions, and responsibilities for the next action. Do not quietly convert tentative comments into commitments. If a proposal follows, make its assumptions visible so the customer can see how the recommendation was developed. A good discovery process does not guarantee a sale. It gives you a sound basis for deciding what to offer and gives the customer a clearer basis for evaluating it.