Decide what the call needs to accomplish
A first call does not need to end with a sale. For a freelancer or small team, a more useful goal is to learn what the potential client needs, decide whether your service could help and agree on a sensible next step. That might be a proposal, a follow-up conversation or an honest conclusion that the work is not a fit.
Before the call, write down what you need to know to make that decision. Consider the problem the client is trying to solve, why it matters now, who will be involved and what a successful outcome would look like. Keep this list short enough to guide a conversation rather than turn it into an interview. It can also help to decide what you will say if the project falls outside your skills or capacity.
Review what you know, then note your assumptions
Read the message that led to the call and review any materials the client has shared. If they have a public website or service description, use it to understand what they offer and how they describe their customers. You do not need to investigate every detail. A brief review helps you avoid asking questions whose answers are already available and gives you a starting point for more specific discussion.
Separate facts from guesses in your notes. For example, a client may say they want a new booking page, but it would be an assumption to conclude that their main problem is the page’s design. Perhaps visitors struggle to choose a service, or perhaps the team has difficulty handling requests after they arrive. Prepare a question that tests your assumption: “What happens today when someone tries to book?” This keeps your preparation useful without letting it narrow the conversation too early.
Prepare questions that reveal the work behind the request
Start with open questions about the situation rather than a long list of features. You might ask, “What prompted you to look for help?” or “What have you tried so far?” Then explore the people affected, the constraints and the result the client hopes to see. If they describe a broad objective such as “more inquiries,” ask what a useful inquiry looks like to them. Their answer may change the kind of work you would recommend.
Make room for practical details without making the call feel like a form. Ask about timing, decision-makers, available materials and any requirements that could shape the project. Budget can also be discussed respectfully: a range, if the client is comfortable sharing one, can help you assess possible approaches. If they do not have an answer yet, note the uncertainty instead of pressing for a number. You can follow up once the scope is clearer.
Be ready to explain your approach without overpitching
Prepare a brief explanation of the services most relevant to the inquiry. Describe the kinds of problems you work on, what a typical engagement involves and what you would need from a client to begin. One relevant example of your process may be more helpful than a tour of every service you offer. If the project has important unknowns, explain how you would investigate them before committing to a detailed solution.
Listen for signs that the request and your capabilities do not match. A client may need a faster turnaround than your team can provide, or they may expect a deliverable you do not offer. You can still make the call valuable by naming the mismatch clearly and suggesting what kind of help they should seek, without promising an introduction you cannot make. Being specific about your limits helps both sides avoid wasted work.
Close with a clear, manageable next step
Leave a few minutes to summarize what you heard. State the client’s goal in your own words, mention any major constraints and ask whether you have understood correctly. This gives the client a chance to correct a mistaken assumption before you build a proposal around it. If a key detail remains unanswered, identify who will find it and how it will affect the next step.
Agree on what happens after the call and who is responsible. For example, you might send a short summary and a proposal outline, while the client shares existing materials or confirms who approves the project. Avoid promising a price or delivery plan before you understand the scope well enough to support it. A useful first call ends with both parties knowing what they learned, what remains uncertain and whether continuing the conversation makes sense.
