How long should a discovery call be?

20–45 minutes for most freelance engagements. Keep it under 30 minutes for smaller projects (under $5K). Allow 45–60 minutes for complex or high-value projects where you need to understand stakeholders, technical requirements, or internal processes. Always set an end time upfront and honor it—respecting their time is part of the professional impression you're making.

Should I charge for a discovery call?

Generally, no—not for standard projects. Discovery calls are part of your sales process, not billable work. The exception: if the 'discovery' requires significant research, audits, or documentation before you can scope the project, that work can be packaged as a paid discovery engagement (sometimes called a 'paid discovery sprint') with its own deliverable. For straightforward projects, a free 30-minute call is standard.

What questions should I ask on a discovery call?

Eight essential questions: (1) What does success look like for this project? (2) What's your timeline and why? (3) Who else is involved in the decision? (4) What's your budget range? (5) What have you tried before, and what happened? (6) What's the cost of not solving this? (7) How do you prefer to communicate during a project? (8) What's your decision-making process from here? These eight questions uncover most of what you need to write a winning proposal.

What Is a Client Discovery Call? (And How to Run One)

Q: What is a client discovery call?

A client discovery call is a structured conversation between a freelancer or service provider and a potential client, held before writing a proposal. Its purpose is to understand the client's situation, goals, constraints, and decision-making process so the proposal can be written specifically to their needs. A good discovery call takes 20–45 minutes and typically results in a proposal that closes at a significantly higher rate than one sent without this conversation.

A freelancer who sends a proposal without a discovery call is guessing. A freelancer who runs a strong discovery call first is writing a proposal the client already wants to sign. Here’s what discovery calls are, why they work, and how to run one in 30 minutes or less.

The word “discovery” is borrowed from consulting and enterprise sales, but the concept applies to every freelance engagement—from a $500 logo project to a $50,000 software build. Before you can propose a solution, you need to understand the problem. That’s what discovery is.

What is a discovery call?

A discovery call is a structured conversation held between you and a prospective client before you write a proposal or quote. It’s not a pitch—it’s a diagnostic.

The goals:

Understand the client’s actual problem (which often differs from their stated request)
Learn their definition of success
Identify constraints: timeline, budget, stakeholders, technical limitations
Determine how they make decisions and who else is involved
Build enough rapport that your proposal feels personal, not generic

A strong discovery call turns a vague “I need a website” into a specific “I need a 5-page site that converts more trial signups, built in 6 weeks, budget around $8K, decision is mine but I’ll check with my CTO.” That’s a proposal you can write in an hour and close in a week.

Why discovery calls matter before sending proposals

Proposals written without discovery calls fail for predictable reasons:

They address the wrong problem. The client asked for X but needed Y. Your proposal solves X brilliantly. They hire someone who understood Y.

They miss the real constraint. The timeline you proposed is impossible because of an internal deadline you didn’t know about. The price structure doesn’t work because of how they process invoices.

They feel generic. The client can tell you sent similar proposals to five other people. Your competitor’s proposal, written after a call, uses their exact language and references the specific concern they mentioned. Guess which one wins.

They under-scope or over-scope. Without a call, you’re estimating based on limited information. Proposals that land wrong on scope almost never close.

The purpose of a discovery call is not to sell. It’s to understand. Freelancers who turn the discovery call into a pitch usually leave without enough information to write a good proposal—and the client leaves feeling like they were sold to, not heard.

How to structure a discovery call

A 30-minute discovery call has three phases.

Phase 1: Context (5 minutes)

Set the agenda and establish that this is a two-way conversation.

“Thanks for making time. I have about 8 questions I want to get through in the next 25–30 minutes. Most of them are about your situation and goals—my job right now is to understand your problem well enough to know whether and how I can help. Sound good?”

This frames you as a professional, not a vendor trying to pitch.

Phase 2: The 8 questions (20 minutes)

These questions are designed to surface the information you actually need to write a winning proposal. Take notes—the exact words the client uses will appear in your proposal.

Phase 3: Wrap-up and next steps (5 minutes)

Summarize what you heard, confirm next steps, and set a specific timeline for when they’ll receive the proposal.

“Based on what you’ve shared, here’s my understanding of the situation: [brief recap]. I’ll have a proposal to you by [specific date]. If anything comes up before then, reply to this email.”

The 8 discovery questions (and why each one works)

1. “What does success look like for this project?”

This is the most important question you’ll ask. It moves the conversation from outputs (what you’ll deliver) to outcomes (what they actually want). “A website” is an output. “30% more leads from organic search within 90 days” is an outcome.

When they answer, ask a follow-up: “How will you measure that?” This surfaces whether they have a real metric or a vague hope.

2. “What’s your timeline—and what’s driving it?”

The “and what’s driving it?” is the important part. Arbitrary timelines are negotiable. Event-driven timelines (product launch, conference, fiscal year end) are not. Knowing the driver tells you how firm the constraint is.

3. “Who else is involved in the decision?”

This prevents the painful situation where you spend a week on a proposal, present it to your contact, and then hear “I need to run it by [someone you’ve never spoken to].” If there are other stakeholders, you want to know now. You might ask to include them in the proposal presentation or at least tailor your proposal to their concerns.

4. “What’s your budget range for this?”

Ask it directly. Clients who avoid the question often have a real number in mind—they’re just waiting to see if you’ll go lower. Knowing the range tells you whether your solution fits, and prevents you from writing a $20K proposal for a client with an $8K ceiling.

If they say “we don’t have a budget yet,” try: “What have you spent on similar work in the past?” or “What’s the maximum you’d feel comfortable with if the result was exactly right?“

5. “What have you tried before, and what happened?”

This question is gold. It tells you what not to repeat, what already failed, and often reveals the real pain behind the stated problem. A client who says “we tried hiring an in-house designer and it didn’t work” is telling you something important about what they’re afraid of.

6. “What’s the cost of not solving this?”

This question surfaces urgency and helps both of you understand what’s at stake. If they say “not much, it would be nice to have,” you know this is a low-priority project for them—which affects timeline and how seriously they’ll engage. If they say “we’re losing about $30K a month in revenue to this problem,” you know this is a high-priority situation with budget to match.

7. “How do you prefer to communicate during a project?”

Do they want weekly written updates or quick Slack messages? Are they hands-on or hands-off? Do they read long emails or prefer bullet points? This sets expectations and helps you build a working relationship from day one instead of figuring it out mid-project.

8. “What’s your decision-making process from here?”

This closes the loop on the sales process. “I’ll review a few proposals and make a decision by end of month” tells you your timeline. “I’ll talk to my partner and let you know” tells you there’s another stakeholder. “We’re ready to move as soon as the proposal looks right” tells you to move fast.

Moving from discovery to proposal

End every discovery call with a concrete commitment:

“Based on what you’ve shared, I’m confident I can help with [specific thing]. I’ll have a proposal to you by [specific date]. It’ll cover [brief outline of what you’ll include]. Any questions before I put that together?”

Then send the proposal within 24 hours. Discovery call momentum is real—the longer you wait, the cooler the enthusiasm gets.

In the proposal, use the client’s exact words wherever possible. If they said “we’re hemorrhaging customers after the free trial,” use that phrase. If they said “my CEO is breathing down my neck about conversion rates,” reference it. Proposals that mirror the client’s own language back to them close at dramatically higher rates.

When to skip the discovery call

Not every engagement needs a 30-minute call. You might skip it when:

The project is very small (under $500) and scope is unambiguous
It’s a repeat client and you know their situation well
The client has sent you a detailed brief that answers most of your questions
You’re responding to an RFP with fixed specs

Even in these cases, a quick 10-minute call to confirm a few details is usually worth it. The investment of 10–30 minutes almost always results in a better proposal.