Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo ads on medical, legal or end-of-life pagesCopy or print any set and take it with you
03 · Professional & Academic

Questions to Ask Client on First Meeting

For consultants, freelancers, agencies and advisers running a first discovery meeting: questions that establish what triggered the search, who actually decides, what the budget and deadline really are, and what done looks like.

20 questions · each with a note on why · conversation guide

The questions

Open any question for the note

  1. Before we start, what would make this a good use of your hour?

    Why ask it

    Sets an agenda you can be measured against, and it catches the mismatch early: they may have come expecting a proposal while you planned to listen. It also often reveals a decision they need to make this week.

  2. How did you come to be looking for someone now?

    Why ask it

    The trigger matters more than the need. A board demand, a resignation, an audit finding and a failed vendor each imply a different budget, timeline and level of internal support for whoever comes next.

  3. Walk me through how this works today, step by step.

    Why ask it

    Summaries of a process almost always omit the manual workaround somebody is quietly doing. Asking for the steps rather than the overview is how you find it, and it is usually where the real problem lives.

  4. What have you already tried, and what stopped it?

    Why ask it

    Ask what stopped rather than what failed. Initiatives here usually die from a change of sponsor, a budget freeze or a reorganization, and the same thing may well be waiting for you.

  5. Who else is affected by this, and who has not been asked yet?

    Why ask it

    The person missing from the discovery meeting is frequently the one who blocks adoption later. Get their name now and ask to speak with them before you write anything.

  6. What does the decision to hire someone look like inside your organization?

    Why ask it

    You want the sequence and the names: who recommends, who signs, who can veto, and whether procurement is involved. Vagueness here is the most reliable predictor of a deal that quietly stalls.

  7. What budget has been set aside for this, and who set it?

    Why ask it

    Who set it is more informative than the number. A figure invented in the meeting behaves very differently from an approved line in a plan, and only one of them survives a slow quarter.

  8. What is the deadline, and what is driving it?

    Why ask it

    Dates with nothing behind them move. Dates tied to an audit, a contract expiry, a season or a launch do not, and those are the only ones worth building a schedule around.

  9. What does done look like, concretely enough that we could both check it?

    Why ask it

    Push until you get something observable: a number, a report that gets produced, a process that runs without a particular person. Clients who cannot answer will end up judging the work on feeling.

  10. What would you need to see in the first month to feel good about this?

    Why ask it

    Gives you an early milestone that buys goodwill for the harder middle stretch. It also exposes expectations about speed that you may not be able to meet, while you can still say so.

  11. Which part do you think will go wrong?

    Why ask it

    Most clients have one specific fear, usually about their own team's capacity or a system nobody wants to touch. Naming it in the first meeting is worth far more than reassuring them.

  12. Who has done this well in your view, and what did you like about it?

    Why ask it

    Gets you their reference model, which is often something you would not have guessed and sometimes something you cannot replicate. Better to find out now than in a review.

  13. What did a previous provider do that annoyed you?

    Why ask it

    A cheap way to learn their working preferences without asking about working preferences. Answers usually concern response times, jargon, or being sold a senior team and given a junior one.

  14. How do you want to be updated, how often, and who else should see it?

    Why ask it

    The distribution list matters as much as the cadence, since it tells you who is watching without being in the room. Agree the format now and you avoid a monthly argument later.

  15. What would you consider outside the scope of this?

    Why ask it

    Getting the exclusions said out loud in the first meeting saves the argument in month three. Silence here usually means they assume rather more is included than you do.

  16. What happens if you do nothing for another six months?

    Why ask it

    Sometimes the honest answer is not much, and it is better to know that before you write a proposal. Consequences with dates attached are what separate an interesting conversation from a project.

  17. Who will own this once I am gone?

    Why ask it

    A named internal owner is the difference between work that lasts and work that reverts within a quarter. If nobody can be named, price handover and training in rather than hoping.

  18. How will you judge whether hiring me was a good decision?

    Why ask it

    The criteria they will be judged on are not always the ones in the brief. This surfaces the political outcome, such as making a case to the board, that sits alongside the practical one.

  19. What have I not asked that I should have?

    Why ask it

    Regularly produces the constraint nobody mentioned: a pending acquisition, a system already chosen, a colleague who will resist. People will volunteer it when asked and not before.

  20. Is there any reason this might not go ahead?

    Why ask it

    An uncomfortable closer that saves weeks of pursuit. Hiring freezes, an unfinished reorganization and an incumbent who is already favored tend to come out when the question is asked plainly.

Running a First Client Meeting

Practical guidance for the conversation itself

How to Run It

Say how the meeting will go in the first thirty seconds

Tell them you will ask questions for most of the time, that you will not present anything today, and when they will hear from you. Clients who expected a pitch relax, and you stop losing the first ten minutes to a mismatch.

Ask for the last time it happened, not the general case

"How do approvals usually work" gets you a policy. "Who signed off the last thing this size, and how long did it take" gets you the truth, including the step nobody documents.

Write down their words, not your paraphrase

The exact phrase a client uses for their problem should appear in your proposal. Reworded into your own vocabulary, it reads as though you were describing a different company.

Do not solve it in the room

The temptation to demonstrate value by proposing an approach in minute twenty is strong, and it usually ends the discovery. You will get a worse brief, and you will have given away the thinking for free.

Ask about money and decision rights out loud

Both feel rude and both are normal in a commercial conversation. Skipping them is why proposals sit unanswered for six weeks, and clients almost never mind being asked directly.

What to Notice

  • Whether they can name a budget owner. No name usually means the project is at the exploratory stage, whatever the urgency in the room suggests.
  • Whether the person in front of you is the one with the problem or the one who has been asked to look into it. The second needs help building an internal case, which is different work.
  • Whether the deadline has a cause. Ask twice if the first answer is that leadership wants it soon.
  • Whether they speak about their own team with respect. How they describe the last provider and their own staff predicts how they will describe you.
  • Whether anything has already been decided, such as a platform, a partner or an approach. Discovering a locked-in choice after you propose an alternative wastes both parties' time.
  • Whether they answer questions about consequences of inaction. Hesitation there is the clearest signal that this may not become a paid project.

Common Pitfalls

Talking more than the client

If you have spoken for more than a third of a discovery meeting, you have run a pitch. Track it roughly, since almost everyone overestimates how much listening they did.

Accepting the stated problem as the problem

Clients arrive with a solution already framed as a need, such as wanting a new system when the issue is that two teams do not speak. Ask about the process before you accept the diagnosis.

Leaving without a next step and a date

Ending on a promise to send something over is how first meetings evaporate. Agree what you will send, when, and what they will do with it, before anybody stands up.

Discounting before you have scoped

A price mentioned in the first meeting becomes the anchor for everything afterwards, and it is usually wrong in one direction or the other. Give a range with the conditions attached, or nothing at all.