Interview Your Next Client: Questions to Ask Before You Say Yes

Most freelancers treat the first call as an audition. They prepare their pitch, mention past work, and hope the client says yes. But a project is a relationship that may last for weeks, and you are the one who will live inside it. The call is just as much your interview of them.

The good news is that you do not need a sixth sense for difficult clients. You need a handful of well-chosen questions and the habit of listening to how they are answered.

Why questions beat gut feeling

Gut feeling is noisy. A charming client can still be disorganised, and a gruff one can be the easiest person you work with all year. Questions give you something concrete to compare. They also show the client that you work in a structured way, which good clients appreciate and poor ones tend to resist.

Below are five areas worth covering, each with a few questions and a sense of what to listen for. No single answer is a verdict. You are looking for patterns.

Area one: what the project is for

Ask: “What should be different once this is finished?” and “How will you know it worked?”

A client with a clear answer, even a modest one, is easy to serve. You can aim at something. If the answer is vague, or changes every time you ask, expect the goal to move during the project, and expect that to cost you time.

Vagueness is not always a warning. Some clients simply have not thought it through yet. The test is what happens next: do they say “good question, let me think and come back,” or do they get irritated that you asked?

Area two: who decides

Ask: “Who else will see this before it is approved?” and “Who has the final word if opinions differ?”

Projects rarely go wrong because of the person on the call. They go wrong when a boss, a partner or a cousin appears in the last week with strong opinions. Naming everyone early lets you plan for it, for example by asking that those people join a mid-project review.

If the client says “just me,” and later turns out to answer to three other people, that tells you something about how openly they share information.

Area three: how they like to work

Ask: “How do you prefer to communicate, and how quickly do you usually reply?” and “What was the best experience you have had with someone in my role?”

The second question is gentler than it sounds, and more useful than asking about bad experiences. People describe what they value: speed, honesty, being left alone, being kept updated. You learn what to give them.

It also works as a mirror of the more obvious warning sign. A client who can talk warmly about a past collaborator is usually easier to work with than one who can only list grievances.

Area four: what happens when you disagree

Ask: “If you see something in the first draft that you do not like, how would you want to tell me?” and “How many rounds of changes do you expect?”

This is where scope gets settled. If the client expects unlimited revisions and you expect two, it is far better to find out on the call than at the third round. Whatever number you agree on, write it in your proposal.

Listen to the tone as well as the content. Someone who says “I will be direct, I would rather you hear it straight” is a different person from someone who says “oh, I will know it when I see it.”

Area five: money and timing

Many freelancers leave this for last, or avoid it. Do the opposite, and ask plainly:

• “Is there a budget range you have in mind?”
• “Who approves invoices, and how long does payment usually take on your side?”
• “Are you comfortable with a deposit before I begin?”

These questions are not rude. Professional clients are used to them, because they ask their own suppliers the same things. If a client bristles at the idea of a deposit or cannot say who pays the bill, you have learned more than any amount of friendly chat could show you.

It also pays to put the answer in writing right away. A short follow-up email with the agreed price, deposit, payment terms and the number of revision rounds protects both of you. When it is time to bill, a tool such as TickPaid lets you send an invoice with a clean link the client can open without creating an account, which removes one more excuse for a slow payment.

Reading the answers together

Imagine two prospects asking for the same website. The first says the goal is to get more bookings, names two people who sign off, accepts two rounds of changes and agrees to a deposit. The second says the goal is “a better look,” mentions that the whole team will weigh in, wants to see everything before deciding on price and thinks deposits are for risky clients.

Neither is a villain. But the first conversation gave you a map, and the second gave you a list of risks. If you take the second job anyway, you can charge for the uncertainty, tighten the contract, or ask for a paid discovery phase first.

How to say no, or not yet

If the answers worry you, you have options other than a flat refusal:

1. Offer a small, paid first step, such as a planning session, before the full project.
2. Raise your price to reflect the extra effort you expect.
3. Decline kindly, and suggest someone else if you know a good fit.

A polite “I do not think I am the right fit for this one” costs you nothing and keeps your reputation intact.

Keep your list short

You do not have to ask everything on every call. Pick one or two questions from each area, and write them on a card next to your computer. After a few calls, they will feel like a natural conversation. After a few projects, you will notice that the clients who answered well are the ones you are glad you chose.