Discovery Call Questions: What to Ask Before You Send a Quote

A potential client writes: "We need a new website. What would that cost?" You could reply with a number. But without knowing what they need, any number is a guess, and guesses either lose the project or win it at the wrong price.

A discovery call closes that gap. In 30 minutes you find out what the client really needs, whether you are a good fit and what to put in your proposal. Here are the questions that matter and how to structure the call.

Discovery call vs kickoff meeting

The two are easy to mix up, but they happen at different moments and have different goals:

This article covers the discovery call. For the meeting after the signature, see our kickoff meeting agenda.

Before the call

• Look the client up. Website, LinkedIn, recent news. Five minutes are enough, and it saves you basic questions.
• Send a short agenda, or at least one line: "I'd like to understand your goals, the scope and the timeline, so I can send you a proposal that fits."
• Keep it short. 30 minutes is plenty. Longer calls before a contract tend to turn into free consulting.
• Ask whether you may record. It lets you listen instead of taking notes, and you can go back to the client's exact words when you write the proposal. Our guide on recording client calls legally explains how to ask.

A 30-minute structure

Let the client talk for most of the call. A good rule: they speak 70% of the time, you 30%. Your job is to ask and listen, not to pitch.

The questions

You don't need all of them. Pick the ones that fit and follow up on whatever sounds important.

The problem

• What made you start looking for help now?
• What happens if nothing changes?
• What have you tried so far, and what didn't work?

The goal

• What should be different when this project is done?
• How will you know it worked?
• Who benefits most from the result?

Scope

• What do you see as part of the project, and what is definitely not?
• Do you have content, assets or access ready, or does that need to be created?
• Are other people or agencies involved?

Budget

• Do you have a budget in mind for this project?
• How did you arrive at that number?

Timeline

• Is there a fixed date the project depends on, like a launch, a trade fair or a funding round?
• When would you like to start?

Decision

• Who else is involved in the decision?
• How do you usually choose between proposals?
• What would make you say no?

How to ask about budget

Many freelancers skip the budget question because it feels awkward. It shouldn't. Without it, you write a proposal into the dark. Ask it plainly and explain why:

"Do you have a budget range in mind? It helps me suggest the right scope, so I don't send you something far too big or too small."

If the client doesn't want to name a number, offer ranges:

"Projects like this usually land somewhere between €3,000 and €8,000, depending on the scope. Where would you like to be in that range?"

The answer tells you a lot. If the client was thinking €800, it is better to find out now than after you spent four hours on a proposal. To know your own ranges, start from your hourly rate and your time estimates.

Red flags

Some answers suggest that a project will be harder than it looks:

• "We just need something quick." Usually it is not quick, and the expectations are not small.
• No budget, no range, no idea. The client may not be ready to buy.
• The decision maker is unreachable. You will meet them for the first time when they reject the work.
• Three previous freelancers "didn't work out". Ask what happened. Sometimes it really was the freelancers.
• Pressure to start before a contract. A good client is happy to sign first.

One red flag is not a reason to walk away. Several are a reason to price carefully, scope tightly or say no politely.

Next steps at the end of the call

Never end a discovery call without a clear next step. Summarize what you heard and say what happens now:

"So the goal is a new booking flow before the Christmas season, with your existing brand, and you'd like to stay under €6,000. I'll send you a proposal by Thursday with two options. Does that sound right?"

The client can correct anything you misunderstood, and you both know when to expect the proposal.

After the call

1. Send a short thank-you the same day, with the date for the proposal.
2. Reread your notes or the summary of the recording. Mark the client's exact phrases about goals and problems; they belong in your proposal.
3. Estimate the work before you name a price. Ranges beat gut feelings.
4. Write the scope precisely, including what is out of scope. It is your first line of defense against scope creep.
5. Send the proposal on time. Speed signals how you will work on the project.

Checklist

• Client researched before the call
• Short agenda sent, call kept to 30 minutes
• Consent to record asked
• Problem, goal, scope, budget, timeline and decision covered
• Red flags noted
• Summary and next step agreed at the end of the call
• Proposal sent by the promised date

Write the proposal from the client's own words

Winnie records your discovery calls in the browser and writes the transcript and a summary with the goals, decisions and open points. When you sit down to write the proposal, the client's words are right there, filed under the new client. See how the meeting protocol works.