How to run a freelance discovery call that produces a useful brief
Use a freelance discovery call to clarify goals, scope, stakeholders and constraints before deciding whether to prepare a proposal.
A discovery call should help both sides decide whether there is a suitable project. You do not need to impress the client by solving the entire problem on the call. You need to listen carefully, identify missing information and turn an initial request into a brief that can be priced and delivered responsibly.
Start with the business reason
Ask what prompted the project and what needs to be different after it is complete. A request for a new website might really concern unclear services, outdated information or a difficult enquiry process. Ask how the client will judge a satisfactory result. Keep listening until the objective is concrete enough to distinguish essential work from preferences.
Identify constraints and dependencies
Discuss the deadline, existing materials, budget range and required systems or formats. Ask who can provide source information and who approves the work. Understand whether other suppliers are involved. A project can be a good skills match but still unworkable if essential inputs will arrive after the deadline or approval responsibility is unclear.
Explore scope without giving away a full solution
Ask enough questions to identify deliverables and risks. Share relevant examples of your approach, but do not turn a short call into an unpaid detailed strategy engagement. If substantial research is necessary before accurate scoping, propose a defined discovery phase with its own deliverable. Explain why the research is needed and what decision it will support.
Close with a written summary
Recap the objective, likely scope, unresolved questions and agreed next step. Tell the client when they can expect your follow-up. Send a concise summary that they can correct before you prepare a proposal. If the project is outside your capability or availability, say so early instead of accepting it and hoping to work out the difficult parts later.
Practical example
Useful closing question: “Before I estimate this, can we confirm that the initial deliverable is the ten-page report, that your team supplies approved data, and that one person will consolidate feedback?” A clear recap tests shared understanding.
Illustrative example. Adapt it to your own experience and circumstances.Your action checklist
- Ask why the project is needed.
- Define success without guarantees.
- Check inputs, approvals and timing.
- Record unresolved scope questions.
- Send a summary before estimating.
Send it to someone planning their next step.
Published by Inter-viewed. This guide offers general professional advice; examples are illustrative. Read our editorial approach or suggest a correction.