Try SpecBot free — turn your discovery call notes into a proposal clients accept in one click.
The quality of your proposal is determined almost entirely by the quality of your discovery call. A vague, surface-level conversation produces a vague proposal. A specific, probing conversation produces a specific, compelling proposal that clearly reflects the client’s situation.
Here’s how to run a discovery call that gives you everything you need to write a strong proposal.
Before the call: prepare, don’t just show up
The difference between a reactive and a proactive discovery call is preparation. Before the call:
Research the client’s business. Spend 10-15 minutes understanding their industry, their product or service, their competitors, and any obvious problems their current situation has. If they have a website, look at it with a critical eye. If they’re a B2B company, look at their LinkedIn. This isn’t about showing off research — it’s about asking better questions.
Prepare your core questions. Have 6-8 questions written down. You won’t always use all of them, but having them ensures you cover what you need to.
Know what information you need to write the proposal. Specifically: business goal, current situation, desired outcome, timeline, budget, and decision-making process. Structure your questions to get this information.
The four categories of discovery questions
1. Situation questions (understand where they are)
These questions establish context. You need to understand the current situation before you can propose anything.
- “Tell me about the current [website/process/system/situation]. What’s working and what isn’t?”
- “Who’s currently handling [the work you’d be doing]?”
- “What does your current [process/output/result] look like?”
- “What triggered this project — why now?”
Why this matters for your proposal: The executive summary of a strong proposal opens with the client’s current situation. Situation questions give you that content.
2. Goal questions (understand where they want to be)
These questions establish the business outcome the client is trying to achieve. This is crucial — it separates a project-focused scope from an outcome-focused scope.
- “What does success look like for this project? How would you measure it?”
- “What business goal is this project connected to?”
- “If this project goes perfectly, what changes for you in 6 months?”
- “What outcome are you most focused on?”
Why this matters for your proposal: The strongest proposals connect scope to business outcomes. Goal questions give you the language to do that.
3. Constraint questions (understand the limits)
These questions surface the constraints that will shape what you propose.
- “What’s your timeline? Is there a hard deadline?”
- “What budget range are you working with?”
- “Who are the decision-makers for this project?”
- “What’s the approval process — how does ‘yes’ happen on your end?”
- “What would make this project fail?”
- “What have you already tried that didn’t work?”
Why this matters for your proposal: Constraint questions prevent you from writing a proposal that’s impossible to approve (wrong budget, wrong timeline, missing a stakeholder). The “what would make this fail” question surfaces risk factors you can address.
4. Clarifying questions (establish scope specifics)
These questions get you the specific information needed to scope the deliverables.
For a web project: “How many pages are we talking about? Do you have content ready or does that need to be produced? What platform are you on or do you want to be on? Do you have a designer, or is that in scope?”
For a content project: “How many pieces per month? What length? What topics? Who approves content? Do you have a brand voice guide?”
For an SEO project: “What’s your current traffic? What pages are performing? What keywords are you targeting? Do you have technical issues? Who has access to analytics?”
Why this matters for your proposal: Clarifying questions produce the specific line items in your scope section. Without these, your scope will be too vague to protect you.
The questions most freelancers skip (but shouldn’t)
“What budget range are you working with?”
This question feels uncomfortable but is essential. You can frame it naturally: “Before I invest time in a proposal, it helps to know the budget range you’re working with — it lets me scope something that actually fits. What range are you thinking?”
Not knowing the budget means you might spend 3 hours writing a $9,000 proposal for a client with a $3,000 budget. Finding out the range early either saves you that time or saves you from undercharging.
“Who else is involved in the decision?”
If there’s a decision-maker who isn’t on the discovery call, you need to know. A proposal that’s perfect for the person you’re talking to can still die if it doesn’t address the concerns of the CFO or the co-founder who has final approval.
“What’s your timeline for making a decision?”
This tells you when to follow up, how urgently to move, and whether this is a real project or exploratory research.
“Have you gotten other quotes / proposals?”
This surfaces competition you might not know about and gives you useful information about how to position yourself.
Taking notes that produce a better proposal
Most freelancers take scattered notes during discovery calls. The notes that produce good proposals are organized around proposal sections:
CLIENT SITUATION:
[What's their current state? What problem are they solving?]
GOAL/OUTCOME:
[What does success look like? What metric are they trying to move?]
SCOPE SPECIFICS:
[Deliverables, quantities, platform, integrations, content, etc.]
TIMELINE:
[Start date, milestones, hard deadline if any]
BUDGET:
[Range discussed, or infer from project type if not discussed]
DECISION PROCESS:
[Who signs off? What's the timeline? Any other proposals?]
THEIR WORDS:
[Exact phrases the client used that you should mirror in the proposal]The “their words” section is underrated. Clients respond to seeing their own language reflected back. When they said “we need to stop losing customers at checkout,” your proposal should reference losing customers at checkout — not “reduce cart abandonment rate.”
After the call: write the proposal immediately
The window between the discovery call and when you should send the proposal is 24-48 hours. The longer you wait, the colder the lead gets — and the harder it is to write a specific proposal because you’ll start forgetting the details.
Write or review the proposal while the call is fresh. Your notes should be specific enough that you can produce the first draft quickly. If they’re not, that’s a signal that your discovery conversation needs to go deeper next time.
Continuous improvement
After each discovery call, ask yourself:
- Did I have the information I needed to write the proposal?
- Were there questions I wish I’d asked?
- Were there scope details I had to guess at?
Add the questions you wish you’d asked to your standard question list. Over time, your discovery conversations become more efficient because you’ve already mapped every information gap that slows proposal writing down.
Start free on SpecBot — SpecBot turns your offers into proposals clients accept in one click, with a signed PDF for both sides. Free is 3 proposals a month with every feature; Pro is unlimited proposals at €12/month, or €9/month billed yearly. Write them in the web app, by voice, or inside ChatGPT and Claude.