Freelance Discovery Call Questions: 25 to Ask Before Quoting

Most underpriced freelance projects weren't priced badly. They were scoped badly, on a call where nobody asked who signs off, what "a few revisions" means, or what happens if the client's content arrives three weeks late.

A good discovery call fixes that before you write a number down. This guide gives you 25 discovery call questions grouped by what they protect, a simple way to run the call in 30 minutes, and a light AI workflow: ChatGPT or Claude preps your agenda from the client's intake answers before the call and flags what you still don't know after it. The model drafts and checks. You ask, listen and decide.

If you already record calls and want to turn the transcript into a proposal, that next step is covered in our AI meeting-to-proposal workflow. This page is the part before it: asking the right things in the first place.

What a discovery call is for

A discovery call has three jobs, in this order:

Decide if it's a fit. Budget range, timing and type of work all have to line up with what you do.
Collect what you need to scope and price. Deliverables, boundaries, inputs from the client and how decisions get made.
Agree on the next step. Usually "I'll send a proposal by Thursday" or "this isn't a fit, here's who might help".

It is not a free strategy session. If you find yourself solving the problem live, stop and note it as something the paid project will cover.

The 25 questions, grouped by what they protect

You won't ask all 25 on every call. Pick the ones your intake form didn't already answer. The grouping matters more than the wording: each group protects a different part of your quote.

Goal and success (protects your positioning)

#	Question	Why it matters
1	What made you start looking for help now?	Reveals urgency and the real trigger
2	What does a good result look like three months after we finish?	Gives you a success measure that isn't "make it pop"
3	How will you know this project worked?	Turns vague goals into something checkable
4	What have you already tried, and what didn't work?	Avoids repeating a failed approach
5	Who is this ultimately for (their customer, their boss, a board)?	Tells you whose taste really decides

Scope and deliverables (protects you from scope creep)

#	Question	Why it matters
6	What exactly do you expect to receive at the end?	Lists deliverables in their words
7	What is definitely out of scope for this round?	Gets boundaries said out loud early
8	How many rounds of feedback do you usually need?	Sets a revision count you can write down
9	Are there pieces you'll handle in-house?	Clarifies the handoff edges
10	Is there a phase two you're already thinking about?	Separates now from later, and flags future work

Inputs and dependencies (protects your timeline)

#	Question	Why it matters
11	What will you provide, such as content, logins, brand files or data?	Lists what you're waiting on
12	Who on your side gets those to me, and how quickly?	Names a person, not a team
13	Are there tools or platforms I must work in?	Avoids surprise licence costs or learning curves
14	Any technical, legal or brand rules I should know about?	Surfaces constraints before they become rework
15	Is anything happening on your side that could pause the project?	Launches, reorganisations and holidays

Budget and money (protects your rate)

#	Question	Why it matters
16	Do you have a budget range in mind for this?	Saves you quoting blind
17	Is that range fixed, or does it depend on what's included?	Shows whether options will help
18	How do invoices usually get approved and paid at your company?	Finds payment friction early
19	Are you comfortable with a deposit before work starts?	Tests commitment and payment process

If a client won't share any budget, offer two or three ranges ("projects like this usually land in one of these bands") and watch which one they react to. That's still useful information.

Decisions and approval (protects you from endless revisions)

#	Question	Why it matters
20	Who else needs to approve the work?	Finds the hidden stakeholder
21	Will they see drafts, or only the final version?	Late surprise feedback is the biggest revision risk
22	How do you prefer to give feedback: one consolidated list, or as it comes?	Lets you ask for one list in writing

Timeline and logistics (protects your calendar)

#	Question	Why it matters
23	Is there a hard deadline, and what's driving it?	Separates real deadlines from preferences
24	How do you like to communicate, and how often?	Sets expectations about response times
25	What would make you choose one freelancer over another?	Tells you what your proposal must address

How to run the call in 30 minutes

A simple agenda keeps the call useful and stops it running long:

Time	Section	Your goal
0 to 3 min	Intro and agenda	Say what you'll cover and that you'll follow up with next steps
3 to 10 min	Goal and success	Questions 1 to 5, mostly listening
10 to 20 min	Scope, inputs, decisions	The gaps your intake form left
20 to 26 min	Budget and timeline	Ask directly; don't leave money to email
26 to 30 min	Next step	Confirm when your proposal (or a "not a fit" note) arrives

Take notes in the client's words for goals and deliverables. Those phrases are the best raw material for your proposal later, because the client will recognise them.

The AI prep workflow (before the call)

If clients fill in an intake form, let ChatGPT or Claude turn their answers into a tailored agenda. Paste only what you need; leave out personal contact details.

Here are a prospective client's intake form answers.
Turn them into a 30-minute discovery call agenda using these sections:
goal and success, scope, inputs, budget, decisions, timeline.
For each section, list only the questions their answers DON'T already
cover, worded naturally (max 3 per section).
Flag anything in their answers that sounds vague or risky for scope,
such as "a few pages", "quick", "simple" or "ongoing".
Don't guess budget numbers or invent details about their business.

Intake answers:
"""
[paste]
"""

Read the result before the call and cut anything you wouldn't actually say. The flagged vague phrases are the most useful part: "a few pages" and "some light edits" are exactly the words to dig into live.

The AI gap check (after the call)

Straight after the call, paste your notes (or a transcript summary, if you recorded with the client's consent) and ask what's still missing before you can quote.

Below are my notes from a freelance discovery call.
Check them against this list: deliverables, out-of-scope items,
revision rounds, client inputs and who provides them, approvers,
budget range, payment terms, deadline and what drives it.
For each item, say "covered" with the quote from my notes, or "missing".
Then draft a short, friendly follow-up email asking ONLY about the
missing items (under 120 words). Don't fill gaps with assumptions.

Notes:
"""
[paste]
"""

Two things to watch. First, check every "covered" against your notes, because models sometimes mark an item covered when it was only hinted at. Second, rewrite the follow-up email's opening yourself and send it from your own inbox. If a meeting notes tool is doing the capture, our AI meeting notes tools for small teams guide compares the options, including consent and export features.

Red flags worth noticing

None of these mean "walk away" on their own, but they should change your quote or your terms:

No one can name the final approver. Expect late feedback; limit revision rounds in writing.
"We'll know it when we see it." Ask for two or three examples they like and write those into the brief.
Hard deadline, missing inputs. Make the timeline depend on inputs arriving by a set date.
Budget question dodged twice. Send ranged options instead of one big number.
They want free samples or spec work. Offer a small paid first phase instead.

When one of these turns up mid-project anyway, the scripts in handling scope creep with AI help you turn it into a change order rather than unpaid work.

From call to proposal

Once the gap check comes back clean, you have everything a proposal needs. Our freelance project proposal template has a section for each of the groups above, so the answers drop straight in. Before you price, run the free 40-point freelance scope checklist: its scope, inputs and money sections line up with the questions on this page and catch anything the call missed.

What not to hand to AI

The call itself. Rapport and follow-up questions are your job.
Pricing. The model can tell you what's missing, not what the work is worth.
Fit decisions. Whether to take a client depends on your capacity and judgement.
Client data you don't need. Strip names, emails and anything confidential before pasting; our Claude for client work guide covers redaction habits that also apply to ChatGPT.

FAQ

How long should a freelance discovery call be? Thirty minutes is enough for most small and mid-sized projects if the client filled in an intake form first. Longer calls tend to drift into free consulting.

Should I ask about budget on the first call? Yes. Asking directly is normal and saves both sides time. If they won't share a number, offer ranges and see which one they react to.

Is it okay to record a discovery call? Only with the client's clear consent, asked at the start. Many clients are fine with it if you explain it's for accurate notes, and some will say no; respect that and take written notes instead.

Do I need a discovery call for every project? Not for small, well-defined jobs where the intake form answers everything. For anything with multiple deliverables, approvers or a fixed deadline, a short call usually pays for itself in avoided rework.

Bottom line

Good discovery questions are mostly about boundaries: what's in, what's out, who decides, what you're waiting on and what it's worth. Use ChatGPT or Claude to prep the agenda and spot gaps afterwards, then make the scope and price decisions yourself.

When you're ready to write it up, our $9 Freelancer Proposal Autopilot Kit turns your call notes into a proposal with clear terms, and the free scope checklist is a quick final check before you hit send.