Freelance Client Calls: How to Handle Them in English

For freelancers, the "interview" usually shows up as a short call with a potential client, on Zoom, Google Meet, or a freelance platform's built-in call. It might last 20 or 30 minutes, but it decides whether the project lands with you.

It's quite different from a job interview. Clients rarely ask "what are your weaknesses?" They arrive with a problem, and they want to know whether you can solve it without drama. This guide walks through how to run that kind of call in English, step by step.

How a client call differs from a job interview

Job interview	Freelance client call
The interviewer leads	You help lead the conversation
The focus is you	The focus is the client's problem
The outcome is a job offer	The outcome is a proposal or contract
Pay comes up late	Price and deadline often come up in the first call

So you need to ask more questions than you would in a job interview. Clients who feel heard tend to trust you more. Many clients are also non-technical, which means your explanations need to stay simple.

The first five minutes: open, then listen

Start with a short greeting, then hand the floor to the client. You don't need a long introduction about yourself at the start.

Hi, thanks for your time today. I read your project post. Could you tell me more about what you need?

While they talk, jot down key words. Then play back what you heard in a few short sentences. It's simple, but it's often the moment a client thinks, "this person gets it."

So you run an online store. Orders come in through WhatsApp. You want them all in one dashboard. Is that right?

If you miss part of what they said, ask politely. Phrases for when you don't understand the question has options that sound natural.

Discovery questions that uncover the real need

These five questions cover most of what you need before you can make an offer:

1. Goal: "What problem are you trying to solve?"
2. Users: "Who will use this every day?"
3. Deadline: "When do you need the first version?"
4. Budget: "Do you have a budget range in mind?"
5. Success: "How will you know the project worked?"

A few follow-ups that often help:

Do you already have a design, or should I suggest one?

Is there an existing system I need to connect to?

Who will maintain this after I finish?

The budget question can feel awkward. But asking it politely saves time on both sides. Serious clients usually have a range in mind.

Showing work that actually matches

Only after you understand the need should you talk about yourself. Pick the one or two projects that are closest to their problem, not your entire portfolio, and connect them directly.

I built something similar last year. It was an order dashboard for a small bakery. Orders came from a web form into one list. The owner updated the status from her phone.

If you haven't done this exact kind of project, don't invent one. Clients can ask for links or screenshots. Be honest and bridge to the closest real experience:

I haven't used the WhatsApp API before. But I've worked with other messaging APIs, like Telegram. I'd start with a small test in the first week.

For structuring a project story, see how to explain your projects in English.

Talking about scope, deadline, and price

This is the part that makes freelancers nervous. The rule of thumb: don't give a final price before the scope is clear. If the client pushes, offer a range and explain what moves it.

I'd like to send you a written proposal first. It will list features, timeline, and price.

A first version like this is usually around [your range]. The final price depends on the number of integrations.

Replace [your range] with numbers you actually use. Don't cut your price in the middle of the call just because you're nervous.

To stop the scope from growing, separate "first version" from "later":

Let's keep the first version small. Just the dashboard and order status. Reports can come in phase two.

If they ask for something outside your skills, say so:

Mobile apps aren't my strength. I can build the web dashboard. For the mobile app, I'd suggest a specialist.

An answer like that tends to increase trust. The client sees you don't say yes to everything.

When the client asks for a discount or free work

Asking for a discount is normal, not an attack. Instead of simply dropping your price, offer to reduce the scope. That keeps the value of your work intact.

I understand. To lower the price, we could drop the reports page. Or we could split the work into two phases.

If a client wants a large "free sample," you can decline politely and offer something smaller:

I can't do a full sample for free. But I can show you a similar project I built. We could also start with a small paid task.

The goal isn't to win an argument. It's to land on a deal that's fair for both sides.

After the call: send a written recap

A lot of freelance misunderstandings start with a call nobody wrote down. Within 24 hours, send a short recap. It also shows that you're organized and reliable.

A template:

Hi [name], thanks for the call today. Here's what I understood:

• Goal: one dashboard for all orders.
• First version: order list and status updates.
• Deadline: first version in four weeks. Next step: I'll send a proposal by Friday. Let me know if I missed anything.

It's very close to a follow-up email after a job interview. More on that in closing the interview and the follow-up email.

Common mistakes and a pre-call checklist

Mistakes that come up again and again:

• Pitching yourself right away before hearing the client's problem.
• Saying yes to everything to win the project, then drowning in work.
• Naming a price too early, before you know the scope.
• Too much jargon with a non-technical client.
• No written recap, so each side remembers the call differently.
• Claiming experience you don't have. One request for a portfolio link can expose it.

Before the call:

• Reread the project post and mark anything unclear.
• Prepare your five discovery questions.
• Pick one or two real, matching projects, with links ready.
• Decide your price range and your minimum.
• Have your recap template ready.

For clients in a different time zone, there are more tips in interviewing for remote jobs abroad.

Summary

A freelance client call is a needs discussion, not a one-way Q&A. Listen first, dig into the need with good questions, show your most relevant work, hold the final price until the scope is clear, and always send a written recap.

Repartee works on client calls over Zoom or Meet too: you see a transcript and an Indonesian translation, plus a short answer script drawn from the projects in your own profile.