Free 30-minute discovery call script for US freelancers
If you freelance or consult solo — especially for US clients — the work is rarely the hard part.
The hard part is the first call: you talk for 45 minutes, leave with “sounds interesting,” and then rewrite the same awkward follow-up email for the third time this month.
This post is the full discovery-call playbook I use before a proposal goes out. You can run it as written. If you want the copy-paste Markdown + HTML version (agenda, scripts, and checklist in one file), the free download is at the end.
Who this is for: designers, writers, developers, marketers, and agency-of-one operators who close work over Zoom, Upwork, or inbound email.
Who this is not for: agencies that need multi-seat CRM, or anyone looking for legal advice. Customise payment terms and contracts to your situation.
The goal of a discovery call (and what it is not)
A discovery call is not a free consulting session. It is a fit filter.
By minute 30 you should know:
- What “done” looks like in their words
- Whether they have budget and a decision-maker
- Whether you want the work
If any of those are unclear, you do not write a proposal yet. You ask one clarifying question — or you politely walk away.
The 30-minute agenda (read this aloud)
Use a visible timer. Stick to the blocks even when the conversation is warm.
| Minutes | Block | What you do |
|---|---|---|
| 0–2 | Open | Confirm time, agenda, and that you’ll take notes |
| 2–8 | Their world | Let them describe the problem without pitching |
| 8–18 | Seven questions | Budget, timeline, decision-makers, constraints |
| 18–24 | Fit check | Reflect back scope; name what you would / would not do |
| 24–28 | Next step | Proposal path or polite decline |
| 28–30 | Close | Confirm who does what by when |
Opening script (0–2)
“Thanks for making time. I’ve got about 30 minutes. I’d like to understand the problem, check whether I’m the right person, and leave with a clear next step — either a proposal or a no. Sound fair?”
That last line matters. It gives both of you permission to exit.
Seven questions that surface budget, timeline, and decision-makers
Ask these in order. Do not skip #4 and #5 — that is where ghosted proposals come from.
1. “What does success look like 90 days after this ships?”
You want an outcome, not a feature list. If they answer with tools (“we need a new website”), ask: “What changes for the business when that exists?”
2. “What have you already tried — and what specifically failed?”
Surfaces politics, prior freelancers, and whether they expect magic. If they’ve burned through three vendors with the same brief, price risk into the work or walk.
3. “Who else is involved in saying yes to this?”
If the answer is “just me,” great. If it is “my co-founder / marketing / procurement,” you need those people on the next call or on the proposal email. Never send a proposal into a black box.
4. “What budget range have you set aside for this?”
Say range, not number. Offer bands if they freeze:
“Most projects like this land in the $X–$Y band for me, or $Y–$Z if we include [extra]. Where does that sit relative to what you’ve planned?”
If they refuse any range and won’t share even a ceiling, treat that as a yellow flag — not a deal.
5. “What’s the real deadline — and what happens if you miss it?”
A date without a consequence is a wish. A launch, a campaign, a board meeting, a contract start — those are real. Soft “ASAP” with no external driver usually means the project will stall after your proposal.
6. “What does out of scope look like for you?”
This one saves you. Get them to name exclusions: ongoing maintenance, unlimited revisions, stock assets, stakeholder workshops, etc. You will put these in the SOW later.
7. “If we work together, what would make you regret hiring me?”
Odd question. Useful answer. You’ll hear the real fear: “going dark,” “over-promising,” “not understanding our brand.” Address that fear in the proposal’s approach section.
Disqualify / walk-away flags
End the call early (politely) if you see two or more of these:
- No budget range and no willingness to discuss one
- Decision-maker is “someone else” who will not join a call
- Success criteria keep changing mid-conversation
- They want free work samples that are basically the project
- Payment terms are “after we get paid by our client” with no deposit
- They badmouth every previous freelancer with no ownership
- Scope is “we’ll figure it out as we go” with a fixed low price
One yellow flag is a conversation. A pattern is a no.
Polite decline script
You do not owe a long apology. You owe clarity.
“Thanks for walking me through this. Based on what you need — especially [budget / timeline / decision process] — I don’t think I’m the right fit right now. I don’t want to slow you down with a proposal that won’t land. Happy to point you toward [alternative: another specialist / a simpler DIY approach] if useful.”
If the fit is close but not now:
“This looks like a strong match once [budget is confirmed / stakeholder can join / brief is narrowed]. If that clears up, I’m glad to pick this back up.”
5-minute post-call notes checklist
Before you open Slack or email, write these five lines:
- Problem in their words (one sentence)
- Success metric (what “done” means)
- Budget / timeline / decision-maker (or “unknown — do not propose yet”)
- Flags (yellow / red, with the quote)
- Next step you promised + date
If #3 is unknown, your next step is a clarifying email — not a full proposal.
From call → close (without reinventing every email)
The discovery call is step one. Most freelancers lose the deal in the admin after:
- Proposal that doesn’t mirror the call
- Fuzzy scope (no exclusions)
- Weak kickoff / onboarding
- Awkward invoice and late-pay follow-ups
If you want the full client-ops pack built for Docs / Sheets / Word / Excel (no Notion required) — proposal tiers, SOW, onboarding checklist, kickoff email pack, invoice + late-pay sequence, plus CSV trackers — that’s Client Close Kit ($39).
Free download (Markdown + HTML)
Grab the ready-to-read-aloud version here (name-your-price, $0 is fine):
Includes:
- The 30-minute agenda
- The seven questions
- Disqualify / walk-away flags
- Polite decline script
- Post-call notes checklist
Formats: Markdown + HTML. Opens in Docs, Word, or a browser. No Notion required.
Try this on your next lead
- Put the agenda in your calendar invite
- Ask all seven questions before you pitch
- Decline or clarify when flags appear
- Only write a proposal when budget, timeline, and decision-maker are clear
If this was useful, the free script is above. If you want the rest of the client-ops stack, Client Close Kit is linked too.
Questions about discovery calls, proposals, or US freelance ops — drop them in the comments.
Top comments (2)
One small post-call safeguard: make payment mechanics part of the close, not a proposal footnote. Before sending the proposal, write down the invoice trigger, due date, deposit, and exact chase cadence (for example, 3 business days before due, on the due date, then +3 and +7), and include the next step, owner, and date in the recap. That turns a friendly discovery call into a shared operating plan and makes a late nudge feel procedural rather than personal. If you want, I do a fixed £50 setup: simple chase cadence + tracker so overdue invoices get a polite nudge on schedule — happy to do it via Contra or here.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.