How to Prepare for a Discovery Call (With the Questions to Ask)

A discovery call needs five things answered before it ends: the client's actual problem, what they've already tried, their timeline, their budget range, and any concern they haven't said out loud. Prepared questions for each of those, asked in that order, are what turn a friendly chat into a call you can write a confident proposal from. Below is the question set, a prep checklist, and a prompt that turns your rough notes from the call into a clean brief afterward.

Why preparation matters more than charisma here

A discovery call that goes well isn't the one where you talked the most — it's the one where you asked specific enough questions that the notes afterward practically write the proposal for you. Going in without a structure means the call drifts toward small talk and a vague "sounds great, I'll send something over," and afterward you're stuck guessing at half the details a proposal actually needs.

The five questions, in order

1. "What's the actual problem you're trying to solve?" Not the surface request — the reason behind it. A client asking for "a new website" might really be solving "we lost credibility with our last redesign."
2. "What have you already tried?" This surfaces what didn't work and why, so you don't propose something they've already ruled out.
3. "What's your timeline, and is there anything driving it?" A launch, an event, a trade show — a real deadline changes how you scope and price the work.
4. "What budget range are you working with?" Asked plainly, not apologetically. If they hesitate, ask what they'd expect to invest in solving this, rather than pushing for a hard number.
5. "Is there anything about this that's worrying you?" The question people skip, and the one that surfaces the unspoken concern — a bad past experience, a fear it'll drag on — that actually decides whether they hire you.

A prep checklist before you dial in

• Look at their website or recent work for five minutes — have one specific observation ready.
• Have the five questions above written down or open on screen, not just in your head.
• Have a notes doc open and ready before the call starts, not scrambled together after.
• Know your own availability and rough timeline going in, so you can answer their questions too.
• Decide in advance whether you'll quote a range on the call or say you'll follow up with pricing.

What to do with the notes afterward

Write them up within an hour, while the specifics are still sharp — the exact phrase they used for their problem, the number they mentioned for budget, the deadline they named. Turning meeting notes into action items covers the general version of this habit; for a discovery call specifically, the notes should feed straight into how to write a freelance proposal — the situation section of a strong proposal is almost always a direct echo of something said on this exact call.

If you have a relevant case study ready, this is also the moment to use it — how to write a case study for a small business covers building one from a past project, and referencing it on the call, when it matches the client's actual situation, does more than describing your process ever could.

The copy-paste prompt

Use this before the call to sharpen your questions to the specific client, and after the call to turn your notes into a clean brief.

You are a plainspoken assistant helping a freelancer or solo business owner prepare for and
follow up on a discovery call.

Before the call — context:
- Who the client is and what they've said they want, from their enquiry: [DETAILS]
- My service / specialism: [SERVICE]

Task: sharpen these five standard discovery questions to this specific client — actual
problem, what they've tried, timeline, budget range, unspoken concern — without changing
their core intent.

After the call — context:
- Raw notes from the call: [NOTES]

Task: turn the notes into a clean brief with five fields — Problem, Tried already,
Timeline, Budget, Concern — flagging clearly which of the five weren't actually covered on
the call, rather than guessing at them.

What a good set of notes looks like afterward

For a call with a small gym owner who enquired about "some marketing help," the cleaned-up brief looks like this:

Problem: Member numbers are steady but new sign-ups have dropped since a competitor opened nearby — not a general marketing need, a specific competitive one. Tried already: Ran paid ads for a month with no clear return. Timeline: Wants visible movement before the January new-year sign-up rush. Budget: £800–£1,200/month range mentioned when asked directly. Concern: Worried about paying for more ads that don't convert, given the last attempt.

Five specific answers, one of them — the concern — the client only said when directly asked. That's the line that ends up shaping the whole proposal.

FAQ

How long should a discovery call be?

Thirty minutes is usually enough for most freelance projects. Longer calls tend to drift into a free strategy session rather than the specific information you need to write a proposal.

Should I quote a price on the discovery call itself?

A range, if pushed, but not a firm number. A specific price deserves the time to think it through properly after the call, referencing what you actually heard.

What if the client can't answer the budget question?

Ask what they'd expect to invest in solving this, rather than a number outright — most people can answer a range even when they can't answer a figure.

Preparing for and following up on calls like this is one of 30 ready-made workflows in the AI Business OS — sharpen your questions before, and turn notes into a brief after, in well under a minute, in our runs.