Give the call a clear purpose
A discovery call is a working conversation, not a pitch you have to win. Its purpose is to find out what the client is trying to change, whether your work could help, and what you would need to know before proposing a sensible approach. For a designer or digital creator, that means looking beyond the first request. “We need a new website” describes a possible deliverable; it does not yet explain the problem the website should solve.
Before the call, review whatever the client has shared and note what is still unclear. Send a short agenda covering the goal, audience, scope, timing, budget, approval process, and next steps. You do not need a rigid script, but a visible structure helps keep the conversation useful. At the start, confirm how much time you have and ask what the client most wants to leave with.
Start with the outcome, then explore the request
Invite the client to explain the project in their own words before you suggest a solution. Questions such as “What prompted this project now?” and “What would be different if it went well?” can reveal the reason behind the brief. Ask who the work is for, what those people need to do or understand, and what is not working today. If the client mentions a desired result, ask how they would recognize progress without demanding a precise metric they may not have.
Listen for the difference between a goal and a preference. A client may prefer a particular style because they think it will make their business feel more credible. You can acknowledge the preference while exploring the underlying goal: “What do you want visitors to understand or trust after seeing it?” That question gives you more room to evaluate design choices later. Restate what you heard in plain language and let the client correct you.
Make constraints discussable
Constraints shape the work, so ask about them early and without treating them as obstacles the client must apologize for. Cover the target launch date and what drives it, the expected budget range, existing brand or technical requirements, available content, and any accessibility or platform needs. Ask what the client will provide and what they expect you to produce. If several deliverables are mentioned, find out which are essential and which could wait.
A useful question is, “If time or budget becomes tight, what must still be included?” It helps distinguish priorities from a wish list. Also ask about dependencies: Will someone else supply copy, product information, photography, or access to an existing system? An ambitious schedule may be workable, but only if the inputs and review time are available. You can flag a possible tension without trying to solve it on the spot: “That date may depend on having approved copy before design begins.”
Find out how decisions actually happen
A good creative proposal can stall when the people who approve it were never part of the conversation. Ask who will give feedback, who has final approval, and whether anyone else needs to review the work for brand, technical, or operational reasons. The person on the call may be your day-to-day contact without being the final decision-maker. That is normal; what matters is knowing how decisions will move through the team.
Make the review process concrete. Ask whether feedback will come through one contact or from several people, how conflicting comments will be resolved, and what the client needs in order to choose a direction. If key stakeholders are absent, suggest including them in a brief follow-up or confirming their priorities before you write a detailed proposal. This is not about bypassing your contact. It is about avoiding assumptions that could lead to repeated revisions.
Close with a shared understanding
Leave a few minutes to summarize the call: the goal, intended audience, likely deliverables, important constraints, and approval path. Separate what you know from what remains open. You might say, “I understand the priority is helping new visitors find the right service, but I still need to confirm who will supply the copy.” Give the client a chance to correct or add anything before you move on.
Agree on a specific next step, such as sending a short recap, requesting missing materials, or preparing a proposal. In your follow-up, record the decisions and open questions in language both sides can refer to later. A discovery call does not need to settle every detail. It has done its job when you can describe the problem clearly, recognize the conditions for doing the work, and explain what must happen before either side commits.
