A discovery call is the short conversation before a project starts. Many freelancers treat it as an audition and spend the whole time selling. That wastes the most useful part of the call: finding out whether the project is a good fit, what it really involves, and what it is worth to the client. A good call makes the proposal easy to write and the project easier to run.
Before the call:
Aim for a call of about twenty to thirty minutes, and say so at the start. It respects their time and keeps the conversation focused.
Try something like: "I'd like to understand what you're trying to do, ask a few questions, and then we can talk about whether I'm the right fit and what the next steps would be." This tells them you will not be pitching for half an hour.
Ask open questions and let them talk. Most of the call should be the client speaking.
The budget question feels awkward, but it saves both of you time. If they will not share a number, offer a range of your own. For example: "Projects like this typically fall between $2,000 and $4,000 for me, depending on scope. Does that fit what you had in mind?"
Briefly describe your process, timeline, how you communicate, and how payment works. Mention deposits, revision rounds, and how changes are handled, so none of it surprises them later.
End with something concrete: "I'll send a proposal with two options by Thursday," or "Send me the brand files and I'll confirm the timeline." Then do exactly what you said.
Part of the call's job is screening. Watch for patterns like these:
One flag on its own is not always a deal breaker. Several together usually point to a stressful project.
If it is not a fit, say so kindly and quickly. You do not need a long explanation:
"Thanks for walking me through this. Based on the timeline and scope, I don't think I'm the right fit for this one, and I'd rather tell you now than slow you down. I hope it goes well."
If you know someone better suited, offer an introduction. Declining gracefully protects your reputation, and clients you turn down sometimes come back later with a project that fits.
The recap email also gives you a written record of what was discussed, which is useful if questions about scope come up later in the project.