12 questions to ask a client before you take the project

Every job post is missing something. The useful skill is not spotting that — it is knowing which three questions turn the gap into information, asking them before you have invested a morning in a proposal, and reading the answers for what they reveal about how the project will actually run.

How to ask them

Ask before writing the proposal, not after. The answers change what you quote, and sometimes whether you quote at all — which means asking afterwards has you doing the work in the wrong order.

Send three or four, not twelve. A dozen questions reads as an interrogation and gets a one-line reply to the first and silence on the rest. Pick the ones that address whatever this particular post is vaguest about; the list below is a menu, not a script.

And ask them plainly. Softening a question until it can be answered with "yes, roughly" wastes the question.

Questions about the work

1. What does done look like?

The single most valuable question in the list. You are asking the client to state a completion condition, which forces them to convert a wish into a specification.

Good answer: a list, or a description precise enough that you could both agree afterwards whether it happened. Bad answer: a restatement of the goal — "done is when it's working well." That client has not finished thinking, and the thinking will happen during your project.

2. What already exists?

Briefs describe destinations and omit starting points. Existing code, an existing brand, a half-finished attempt by the last freelancer, a vendor you will inherit — integrating with reality is routinely more work than building fresh.

Follow it with: has anyone worked on this before me, and what happened? The answer to the second half is often the most informative sentence in the whole conversation.

3. What is explicitly not included?

Inverting the question gets past the assumption problem. Clients list what they want and silently assume the rest. Asking what is out of scope makes them think about the boundary rather than the centre, and boundaries are where projects go wrong.

4. What happens if we discover this is bigger than we thought?

You are asking about the change process before you need it. A client who says "we'd talk about it" has no process; a client who says "we'd re-scope and you'd re-quote" has done this before. Either way, you have raised the topic while it is still hypothetical, which is the only easy time to raise it.

Questions about money

5. What range were you working with?

Not "what is your budget" — a range is easier to answer honestly and harder to dodge. If the reply is "what would you charge?", quote from effort and watch the reaction, because the reaction is the information. Divide whatever number appears by your honest hour estimate before you feel anything about it; the pricing guide covers why that division matters more than the number itself.

6. What are your payment terms, and can we work to milestones?

Cheap to state, and revealing when they have not been considered. On anything longer than a week or two, milestones with a deposit are the difference between a cash-flow risk and a normal engagement.

7. Is payment tied to my delivery, or to something else?

Ask directly when the post mentions launches, funding rounds, or their own client's approval. There is one acceptable answer, and a client who hesitates on this one has told you what you needed to know.

8. Would a paid discovery phase work?

The question to ask when the scope is too vague to fix a price on. It gives the client budget certainty on the part where certainty is possible, and it is a filter: someone who will not pay for a day of scoping is telling you what they think your time is worth. More on when this is the right structure in fixed price vs hourly.

Questions about people and process

9. Who signs off?

"The team will review" multiplies revision rounds by the number of opinions, none of whom read the brief you agreed. You want a name.

10. How many rounds of revisions are we planning for?

Ask it as a planning question rather than a limit, and you will usually get a number rather than an argument. Then put the number in the contract. Without it, "done" is whenever the client stops having ideas.

11. What does this need to achieve for you?

The one question that is not defensive. It surfaces the actual objective behind the deliverable, which sometimes reveals a cheaper or better way to get there — and a client who watches you do that thinking is a client who comes back.

12. What's driving the deadline?

Real deadlines have causes: a launch, a conference, a contract date. Manufactured urgency has none, and it usually persists into the project as a permanent state of emergency. A cause is reassuring. A pause is not.

Reading the answers

The content of the answers matters. How they arrive matters more.

Speed and specificity are the signal. A client who replies within a day with concrete answers to four pointed questions is demonstrating exactly the behaviour that makes a project profitable — they are decisive, they have thought about it, and they will be like this when you need an approval in week three.

Vague answers to specific questions are the clearest warning you will get, and they are worth more than any single red flag, because you produced the test yourself. A client who cannot say what done looks like will not be able to say it in six weeks either, and by then you will have built something.

Treating questions as friction is the other signal worth taking seriously. Experienced clients expect scoping questions and read them as competence. Someone who bristles is showing you how they will respond when you raise a problem mid-project.

None of this makes a client bad. It makes them expensive, which is a different thing and one you can price — see the risk premium in the pricing guide, or the red flags guide for what to look for before you even ask.

Opportunity Radar reads a job post and lists the unknowns it found, including the questions worth asking about them. The free plan covers ten posts a month.