Skip to content
SoloWOS
Start your free trial

Winning clients

Discovery call questions for freelancers (and what each answer tells you)

By SoloWOS teamPublished

IN SHORT

Good discovery call questions find out what the client wants to achieve, their budget range, the deadline, who approves the work and how they'll judge success. Ask the factual ones (service, budget range, start date) in the booking form, so a 30-minute call can cover goals, risks and fit. Send a recap with next steps the same day.

Prices and limits as of .

Key takeaways

  • Group questions by the decision they help you make: fit, budget, timeline, decision-maker and success.
  • Move factual questions into the booking form; spend the call on goals and risks.
  • Listen for warning signs: no budget range, "we need it yesterday", a decision-maker who isn't on the call, or no way to measure success.
  • A 30-minute call can follow a fixed agenda: 5 minutes context, 15 minutes goals and scope, 5 minutes budget and timing, 5 minutes next steps.
  • Send the recap and the proposal date within 24 hours, while the call is fresh.

A discovery call decides two things: whether you want the project, and what to put in the proposal. The questions below are for that first call. Questions for after the client signs live in the client onboarding checklist; this post belongs to the winning clients hub.

The 20 questions, grouped by decision

Discovery questions with what to listen for
DecisionQuestionGood signWarning sign
Fit1. What made you look for help now?A specific trigger (launch, funding, a hire leaving)"Just exploring" with no trigger
Fit2. What have you tried already?They tried something and can say why it fell shortThree freelancers in a year, all "terrible"
Fit3. What does the finished project look like to you?A concrete picture you can turn into deliverables"You're the expert, surprise me"
Fit4. Who else are you talking to?An honest answerRefuses to say and pushes for a price
Fit5. What's not part of this project?Clear edges"Everything, really"
Budget6. What range have you set aside for this?A range, even a wide one"We don't have a budget" for a business project
Budget7. How did you arrive at that number?Based on quotes, past spend or expected returnA guess they won't move from
Budget8. Is that the total, or are there other costs (ads, printing, licenses)?They've thought about the whole costSurprise at any extra cost
Timeline9. When do you need it live, and why that date?A date tied to an event"ASAP" with no reason
Timeline10. When could you start giving feedback and content?A named person and datesContent "will come later"
Timeline11. Any dates when you're unavailable?Holidays and launches flagged up frontNo idea
Decision12. Who else needs to approve this?A short list, ideally on the callA committee you'll never meet
Decision13. How do you usually make a decision like this?A clear process and date"We'll see"
Decision14. What would make you choose one freelancer over another?Criteria you can address in the proposalOnly price
Success15. How will you know this project worked?A number or an observable resultNo answer
Success16. What would make it a failure?Specific fears you can plan aroundUnrealistic expectations
Success17. What happens if you don't do this project?A real cost of waitingNothing much (low urgency)
Working style18. How do you prefer to communicate, and how often?A channel and a rhythm"Always available"
Working style19. Who will be my day-to-day contact?One named personSeveral people with mixed authority
Next step20. If my proposal fits, what would stop you from starting on [date]?"Nothing" or a fixable blockerA blocker they hadn't mentioned

Put the factual questions in the booking form

Service, budget range, deadline, company and website take people 60 seconds to type and you 10 minutes to ask. Ask them before the call, on an inquiry form with 8 to 10 fields, and spend the call on questions 1, 3, 12, 15 and 17, which only work in conversation. Label required questions with the word "required" in the label itself; the W3C's form guidance notes that an asterisk alone is often not announced by screen readers (W3C WAI), and WCAG 2.2 success criterion 3.3.2 asks for a label or instructions on every field, required or optional (W3C). Don't rely on color alone to mark required fields, either (W3C Easy Checks).

Pre-call questions for the booking form
1. What do you need help with? (required, choose one): [your services]
2. Company and website
3. Budget range (choose one): Under $[your minimum] / $[min] to $[mid] / $[mid] to $[high] / $[high]+ / Not sure yet
4. When do you need it done? (date)
5. In two or three sentences, what should this project achieve? (required)
6. Who else will be involved in the decision?

Make the smallest budget range end at your minimum project price. People who pick it are telling you something useful before you spend 30 minutes on a call; you can send them a resource or a smaller offer instead.

How to ask about budget without making it awkward

Budget is the question freelancers skip most and regret most. Ask it as a range, after the client has described the goal, and give them an anchor from your own work: "Projects like this usually run between $4,000 and $9,000 depending on the number of pages. Where does that sit with what you planned?" That wording tells them your range before they commit to a number, and it turns a yes-or-no into a conversation about scope. If they answer far below the range, say so on the call and offer a smaller version. Finding out after you've written a proposal costs you an evening.

What to write down during the call

  • The goal in the client's own words; you'll quote it at the top of the proposal.
  • Every deliverable they mention, and every one they say they don't need.
  • The deadline and the reason behind it.
  • Names: who approves, who sends content, who pays the invoices.
  • Anything that worried them about past freelancers; address it in the proposal's terms.
  • The exact next step and its date, agreed before you hang up.

A 30-minute discovery call agenda

  1. Minutes 0 to 5: thank them, confirm what you read in the form, and say how the call will go.
  2. Minutes 5 to 20: goals and scope (questions 1, 2, 3, 5, 15, 16). Take notes in their words.
  3. Minutes 20 to 25: budget, timeline and decision (questions 6, 9, 12, 13). If the budget is below your range, say so now.
  4. Minutes 25 to 30: next steps. Tell them when the proposal arrives and what it will include. Ask question 20.

Follow-up email after the call

Recap email
Subject: Recap of our call and next steps

Hi [name],

Thanks for the call today. Here's what I understood:
- Goal: [their goal, in their words]
- Must have: [2 or 3 items]
- Deadline: [date], because [reason]
- Budget range: [range]
- Decision: [who approves] by [date]

I'll send a proposal by [day] with [one or three] options. If I got anything wrong, just reply and I'll adjust it.

[your name]

When to walk away

  • The budget is well under your minimum and the scope can't shrink to fit it.
  • The person deciding won't join a call or read a proposal.
  • They want spec work (a free sample) before deciding.
  • There's no way to tell whether the project worked, and they expect you to guarantee results anyway.

Run discovery calls in SoloWOS

Each meeting type in Scheduling can ask its own extra questions at booking time, marked required or optional, and can email the client a reminder 24 hours before. To sort people first, build client intake forms with conditional questions and routing: for example, budgets under $1,000 go to a 15-minute intro call and larger ones to a 45-minute discovery call, with their name and email already filled in on the booking page clients can schedule from. The booking moves the contact to In conversation in your pipeline. Solo includes 300 bookings and 1,000 form responses a month. For the questions in a form you can copy, see the client intake form template.

Questions

How long should a discovery call be?

30 minutes covers most freelance projects when the factual questions are answered in the booking form first. Use 15 minutes for small, well-defined jobs and 45 to 60 minutes for projects over several weeks or with more than one decision-maker on the call.

Should I charge for discovery calls?

A short fit call is usually free. A longer session where you diagnose problems and suggest a plan is consulting, and many freelancers charge for it and credit the fee against the project. In SoloWOS a meeting type can take the full price or a deposit by card at booking.

Should I give a price on the first call?

Give a range if they ask, based on similar projects, and say the proposal will fix the number. Quoting a single figure live, before you've thought about scope, tends to anchor the client on a price you'll regret.

What if the client won't share a budget?

Offer ranges: "Projects like this usually land between $3,000 and $8,000. Where in that range are you thinking?" Most people will pick one. If they still won't, send an estimate with two options and see which they respond to.

Sources

Facts checked against these sources on October 18, 2026. Rules and amounts change, so confirm them at the source before you file or sign.

  1. W3C WAI: Form instructions tutorial
  2. W3C: Understanding WCAG 2.2 Success Criterion 3.3.2, Labels or Instructions
  3. W3C WAI: Easy Checks, required fields

Last reviewed:

SoloWOS tools mentioned here

Run your client work from one account

14 days free, no card needed · Then Basic for $2/month.

Start your free trial