A discovery call is not a performance where you prove how much technology you know. It is a joint investigation. Your job is to understand what changed, why it matters now, what has already been tried, and whether a sensible next step exists.
Arrive with context and a hypothesis
Spend fifteen minutes understanding the organization, product, customer, and recent signals. Write down what you believe the problem might be and what evidence would disprove that belief.
Use AI to summarize public information and prepare questions, but verify important facts at their source. Do not surprise the client with intrusive research or pretend a generated company summary is genuine understanding.
Preparation earns the right to ask better questions—not the right to assume the answer.
Ask for the story behind the request
Start with: what happened that made this important now? Then explore who experiences the problem, how they handle it today, what it costs, and why previous attempts did not hold.
When a client asks for a solution immediately, separate the requested artifact from the desired change. ‘We need an app’ may actually mean field staff cannot access current information, customers abandon a process, or management lacks a reliable operating view.
Qualify the conditions for success
Understand decision ownership, available budget, timing pressure, data access, technical constraints, stakeholder availability, and who must support the result after launch. Ask directly and respectfully.
Qualification protects both sides. A project without an owner, access to users, or authority to change the workflow may not be ready for implementation, regardless of the budget.
End with a decision, not vague enthusiasm
Summarize the problem in the client’s language, name what remains uncertain, and recommend one next step. That might be a proposal, a paid diagnostic, another meeting with a missing stakeholder, or a respectful no-fit.
Send a short written recap the same day. AI can structure your notes, but verify every commitment, date, and commercial statement before sending.
A useful discovery conversation
- You know why the problem matters now.
- The current workflow and cost of inaction are visible.
- The requested solution has been separated from the desired outcome.
- Decision ownership, budget, access, and timing were discussed.
- Both sides leave with one explicit next step.