How to run a discovery call before a client proposal

Leave with a decision, not a finished solution

Run a discovery call as a structured conversation about the client problem, desired outcome, constraints and decision process. By the end, both sides should know whether a proposal is sensible, what still needs clarification and who will do the next action. You do not need to solve the whole assignment live.

This is a pre-proposal conversation, not a kickoff meeting. Kickoff follows agreement and aligns the people delivering the work. Discovery establishes what might be worth offering in the first place. Qualification is the decision you make from that evidence, rather than another name for the meeting agenda.

Prepare from the inquiry, not a generic sales script

Read the intake answers and public information relevant to the request. Write a short hypothesis about the problem, then list what could disprove it. If someone asks for a new presentation, for example, the real gap might be inconsistent messaging rather than slide design. Ask rather than diagnose from the website alone.

Send the purpose, proposed duration and topics beforehand. Explain whether the call is complimentary and exploratory or part of a separately agreed paid diagnostic engagement. Do not surprise the client with a fee, and do not give away a substantial bespoke audit because the meeting lacks a boundary.

HoneyBook recommends an advance agenda, open-ended questions, attentive listening, a summary and explicit next steps. Use those principles without turning the call into a long introduction about your business. Take concise notes; if you want a recording or transcription service, explain it and obtain appropriate permission first. Recording is not necessary.

Use this 30-minute discovery call agenda

This is an illustrative agenda for a modest freelance service inquiry, not a universal call length. The six blocks total 30 minutes: 3 + 7 + 6 + 6 + 4 + 4. Move time between topics when needed, but preserve the closing decision. A complex assignment may require a separately scoped discovery phase.

1. Minutes 0–3: confirm introductions, the time available and the purpose. Ask whether the client wants another question covered before you begin.
2. Minutes 3–10: explore the current situation. Ask what prompted the inquiry, who experiences the problem and for a recent concrete example.
3. Minutes 10–16: clarify the desired outcome and possible outputs. Ask what has already been tried, what must stay unchanged and what a useful result would look like.
4. Minutes 16–22: examine constraints. Discuss the spending range, target date, client inputs, review capacity and who approves the engagement.
5. Minutes 22–26: reflect back what you heard. Describe the relevant part of your service, its limits and any unresolved uncertainty; invite client questions.
6. Minutes 26–30: agree whether to propose, clarify, reconnect later or stop. Assign each next action to a person with a date and explain what is not yet committed.

Ask for evidence without making the conversation an interrogation

Start with “What happened recently that made this a priority?” Then follow the answer. “People are confused” can become “Which question keeps coming up, and where?” A concrete example helps you distinguish a communication problem from a broken process or missing product capability.

Ask “What would need to change for you to call this useful?” rather than promising an improvement you cannot control. A clearer guide is a deliverable you can define; fewer support requests is an outcome influenced by other factors. Discuss both, but do not quietly guarantee the latter.

For money, try “Is there a range set aside for this work, and what does it need to cover?” If the client is unsure, explain the main scope variables rather than inventing an immediate quote. For authority, ask “How will you choose and approve a provider?” A useful contact need not be the final signer.

Leave room for the client to assess you. Explain who would do the work, relevant experience you can substantiate and when you are available. Do not request confidential examples or system credentials to make an exploratory call feel more thorough.

A fictional discovery conversation

Example: Jules is a freelance information designer speaking with Ren, the operations manager at a repair business. Ren has asked for a customer instruction booklet. The following exchange illustrates discovery, not a real client result.

Jules: “What is happening that a booklet should help with?” Ren: “Customers keep calling about what to bring to their appointments.” Jules: “Can you describe the last example?” Ren: “Two customers arrived without a required part. The appointment email does not name it clearly.”

Jules: “Would a shorter pre-appointment instruction sheet address that specific gap, or are there other instructions?” Ren: “We need one sheet for each of two repair services. A booklet might be more than we need.” Jules: “Who can confirm the technical instructions?” Ren: “Our workshop lead, but she is away next week.”

Jules: “What determines the deadline and who approves the fee?” Ren: “We hoped for the end of the month. The owner must approve spending, and the date can move.” Jules: “Then I can explore two instruction sheets, with the technical content supplied and checked by your workshop lead. I will not assume that includes rewriting your booking emails.”

The useful discovery is a narrower output and a missing input owner, not a clever closing line. Jules has not promised fewer calls, reserved a start date or accepted responsibility for technical advice. Ren still needs to confirm the buying process and review availability.

Send a recap that preserves the open questions

Copyable recap: “Thanks for speaking today. My understanding is [problem] affecting [audience]. We discussed [possible outputs], with [limits]. Your target is [date and reason], subject to [inputs or decisions]. Before I prepare a proposal, [person] will confirm [missing information] by [date]. I will then [next action] by [date]. Please correct anything I have misunderstood. Scope, price and scheduling remain subject to the proposal and agreement.”

For Jules, the immediate next action is for Ren to confirm the owner’s approval process and the workshop lead’s availability. If those details support a feasible offer, Jules prepares it. If not, the next conversation is about an alternative date, a different service or a pause, not a proposal containing hidden assumptions.

Know when not to send a proposal

Do not send a detailed proposal merely because the call was friendly. A fundamental service mismatch, unavailable capacity or an unresolved requirement that could change the whole price needs a different next step. Use the qualification record to distinguish missing information from an actual incompatibility.

Common mistakes are reading every intake answer aloud, filling silences with a pitch, offering an uncosted solution and ending with “I will be in touch.” A good close names the next decision and its owner. Only after an engagement is agreed should you move into onboarding and kickoff.