Most freelancers wing discovery calls. Open with "tell me about the project," respond to whatever the client says, hang up 40 minutes later with notes that don't match what they actually need.
The proposal that comes out of a winged discovery is generic. It quotes too high, too low, or for the wrong scope. Win rate suffers. Margin suffers.
Here's the structured 45-minute format that experienced freelancers use. Print it, keep it on your second monitor, follow it.
Before the call
3 hours before:
- Read everything they sent (their initial email, any docs, their website)
- Write down 5 specific questions based on what they said + what's missing
- Open a notes doc with the structure below pre-filled
5 minutes before:
- Test mic / camera
- Close email, Slack, every distraction
- Open the structured notes doc
- Have a glass of water
1 minute before:
- Re-read your 5 questions out loud (yes, out loud)
- Take three breaths
- Click join
The 45-minute script
Minutes 0-3: Set the frame
"Thanks for making time. Quick agenda: I want to spend the first 25 minutes really understanding what you're trying to accomplish and why now. Then 15 minutes on what working together would look like — process, timeline, ballpark range. Last 5 minutes we'll align on next steps. Sound good?"
Why this works: You've taken control of the call without being aggressive. The client knows what's coming, which lowers their anxiety. You've signaled you're here to listen first — which immediately distinguishes you from the freelancers who pitched at them yesterday.
Minutes 3-15: Context (the part everyone skips)
These three questions, in this order:
1. "What's happening in the business right now that made you start looking for help on this?"
This is the only question that matters. It surfaces the real trigger — usually a deadline, a competitor, an internal pressure, a missed number. The trigger tells you the urgency, the stakes, and the political situation.
Listen for:
- Specific numbers ("we're losing 30% of trial users" → measurable)
- Names ("our CEO asked for this" → power dynamics)
- Dates ("by end of Q2" → real deadline vs. wishful)
2. "What does success look like 3 months after this ships?"
Most clients lead with deliverables ("I want a website"). They BUY outcomes ("more booked calls"). This question forces them to translate one into the other.
If they can't answer it, they're not actually ready to buy — they're researching. That's fine, but you'll proposal differently for "researching" vs. "ready to commit."
3. "Who else is involved in deciding to move forward?"
You need to know the decision structure before you write the proposal. If there's a CFO, your proposal needs a budget justification section. If there's a CMO who's skeptical, you need a risk-mitigation section. Without this question, you proposal blind.
If they say "just me," follow up: "Will anyone else need to sign off on the spending?" Because the answer is almost never actually just them.
Minutes 15-25: Scope reconnaissance
Now you can ask about the actual project — but with one rule: listen for what they DON'T mention. What they leave out is more important than what they include.
4. "Walk me through what you imagine this looking like when it's done."
Open-ended on purpose. Let them paint the picture. Take notes on:
- Concrete features they mention
- Vague phrases ("user-friendly," "modern," "scalable") — flag these for follow-up
- What they don't mention (mobile? content? hosting? SEO? maintenance?)
5. "What are the must-haves vs. nice-to-haves?"
Forces prioritization. You'll discover that the "must-have" is often a 2-day feature, and the "nice-to-have" is the 3-week monster the project will turn into if you don't catch it now.
6. "What's already decided vs. still open?"
Examples:
- Tech stack? (decided / open)
- Hosting? (decided / open)
- Content / copy source? (decided / open)
- Domain? (already owned / need to buy)
- Brand / design system? (exists / needs creating)
Each "still open" item is either a discovery gap (you need to know before proposing) or a signal that they want you to decide for them (which is more work but also more authority).
7. "What's the budget range you've planned for this?"
Ask it directly. Stop apologizing for asking about money.
If they say "we don't have a budget" → translate to "they have a budget but won't share it." Respond with: "Most projects in this category land between $X and $Y depending on scope. Where in that range were you thinking?"
If they share a number → great. Now you know which tier of proposal to write.
If their number is way too low → don't argue on the call. Note it. Address it in the proposal with a tier they can afford and a tier that does what they actually need.
Minutes 25-40: Process + timeline
Switch from learning mode to teaching mode. Briefly walk them through how you work.
8. "Here's how I typically structure a project like this..." (2-3 minutes)
Quick overview: discovery → design/architecture → build → review → launch → warranty period. Specific phases for THIS type of project.
9. "What's your timeline thinking?"
Listen for:
- "ASAP" → unrealistic, you'll need to manage expectations
- Specific date → real, plan around it
- "Whenever you can" → low urgency, won't close fast
- "By Q3" → check what Q3 means to them (start of, end of, mid?)
10. "Have you worked with a freelancer/agency on something like this before?"
If yes: "What worked? What didn't?" — this is gold for your proposal positioning.
If no: brief mention of how you handle the things first-timers usually find confusing (revisions, communication, payment schedule).
Minutes 40-43: Ballpark + alignment
11. "Based on what you've shared, projects in this shape typically run $X to $Y over Z weeks. Does that fit roughly with what you had in mind?"
You're not committing to a specific number. You're calibrating before you spend 2 hours writing a proposal.
If their reaction is "Y is way too high" → either the scope they described is bigger than their budget, or they're price-shopping. Address it now: "Got it. To hit a budget closer to your range, we'd typically scope this as [smaller version]. Does that map to what you actually need, or were you thinking the full version?"
If their reaction is "that fits" → you have permission to write the proposal at that level.
Minutes 43-45: Lock the next step
Never end with "I'll get you a proposal."
End with:
"Great. I'll have a proposal in your inbox by [specific day, max 3 days out]. It'll have 2-3 options at different scopes so you can pick what fits. After you read it, want to schedule a 15-minute follow-up to walk through it together — Tuesday or Wednesday next week?"
Three things this does:
- Specific delivery date — creates a small commitment loop
- 2-3 options — primes them for tiered pricing, removes "yes/no" pressure
- Pre-scheduled follow-up — proposals sent without a follow-up call sit in inboxes for weeks
Get the follow-up on the calendar before you hang up.
What to listen for (the meta layer)
Through the whole call, three signals matter more than any specific answer:
1. Decisiveness vs. exploration. Are they asking you to help them decide ("should we do A or B?") or asking you to confirm a decision they've already made ("we're doing A — can you build it?")? Decisive clients close fast and pay well. Exploring clients can become great projects — but require longer sales cycles and educational proposals.
2. Outcome-focused vs. feature-focused. "We need to increase conversion by 20%" is outcome-focused. "We need a homepage redesign" is feature-focused. Outcome-focused clients trust your judgment on HOW. Feature-focused clients want exactly what they described, even if it's wrong. Different proposal styles.
3. Deadline reality. A real deadline has a real reason behind it (event, fiscal quarter, contract date, competitor launch). A fake deadline ("ASAP") has no anchor. Real deadlines are buying signals. Fake deadlines are noise.
Common discovery call mistakes
1. Pitching too early. You're 8 minutes into the call and already explaining your process. Stop. They didn't ask. Listen until minute 25.
2. Quoting on the call. "We could do that for around $8K" → now you've anchored a number before you've thought through the scope. The proposal version of yourself will resent the call version of yourself.
3. Asking the brief questions. The discovery call isn't where you fill in the brief. You're collecting CONTEXT to write a proposal. The brief comes after they sign the proposal.
4. Skipping the budget question. "I'll just send a proposal at the right level" — no, you'll send a proposal at the wrong level because you didn't ask. Ask. Always.
5. Ending without a follow-up scheduled. The proposal that closes is the one that has a 15-minute follow-up call already on the calendar before it lands in their inbox.
Use the call to write the brief
Take notes structured the way the brief is structured — overview, scope, exclusions, deliverables, timeline, budget. By the end of the call you have ~70% of the brief already drafted. The proposal pulls from it. The brief itself gets sent after they sign.
Or paste the call notes (or your discovery questions list, or even the client's initial email) into Briefance and get the brief structure populated automatically. Then you customize.