Template · Discovery call script

Discovery call script — the questions that scope the project on the call

A discovery call has one job: leave with everything a scoped, priced proposal needs — the goal behind the project, what it's worth to the client, constraints, decision process, and timeline. The script below runs ~30 minutes in five movements: context, the goal behind the goal, value, practicalities, and the close (where you name a range and promise the proposal fast). If you take notes, the proposal is half-written when you hang up.

How to use it

  1. Open with their context — let them talk before you present anything.
  2. Ask the goal-behind-the-goal questions until you can restate it in one sentence.
  3. Ask the value questions — what the outcome is worth is what prices the work.
  4. Cover practicalities: timeline, decision-makers, materials, constraints.
  5. Close by naming a range, confirming next steps, and sending the proposal fast.

Movement 1 — context (5 min)

Movement 1 — context (5 min)
"Before I talk about how I work — tell me what's going on. What prompted you to reach out now?"

"What have you already tried, or who's worked on this before?"

(Listen. The word "now" in the first question does the work — timing reveals the real driver.)

Movement 2 — the goal behind the goal (8 min)

Movement 2 — the goal behind the goal (8 min)
"If this project goes perfectly — what's different for you in six months?"

"Is this connected to something bigger? A launch, a raise, a push into a new market?"

"Who else feels it if this works? Who feels it if it doesn't?"

(Stop when you can restate their goal in one sentence and they say "exactly.")

Movement 3 — the value questions most freelancers skip (7 min)

Movement 3 — the value questions most freelancers skip (7 min)
"What does a new customer / closed deal / converted trial roughly mean for you in revenue?"

"What's it costing you that this isn't solved — in money, time, or deals you're not winning?"

"If this work moved that number even a little, what would that be worth over a year?"

(These aren't nosy; they're how the price gets grounded in their math instead of your guess.)

Movement 4 — practicalities (5 min)

Movement 4 — practicalities (5 min)
"When does this need to ship — and is that date connected to anything fixed?"

"Who decides on this — is it you, or you plus others?"

"What exists already? Brand assets, content, research, an old version?"

"Anything you know you DON'T want?"

Movement 5 — the close (5 min)

Movement 5 — the close (5 min)
"This is really helpful — here's what I'm hearing: [one-sentence goal restatement]. Did I get that right?"

"Projects like this usually land between $[X] and $[Y] depending on how deep we go — does that fit the territory you had in mind?"

"Great. I'll send a proposal with two or three options by [tomorrow/date]. It'll be one page — the goal, the plan, the numbers. Anything else you'd want it to cover?"

Common questions

Should I name a price range on the discovery call?
Yes — a range, not a number. It filters mismatched budgets while there's nothing sunk, and it means the proposal never ambushes anyone. 'Between $X and $Y depending on depth' keeps every option open.
How do I ask about budget without it being awkward?
Ask about value first (what the outcome is worth), then offer your range and watch the reaction. 'What's your budget?' makes them commit first and feels adversarial; 'projects like this usually land between…' gives them something to react to.
What if I can't answer their 'how much do you charge' early in the call?
Hold it warmly: 'Depends on how deep we go — let me ask a few more questions and I'll give you a real range before we hang up, not a guess.' Then actually do that. A premature number anchors the whole deal to a guess.

Go deeper: read the full guide on the blog.