Freelancing

How to Run a Client Discovery Call (Script + Checklist)

Updated March 27, 2026 · 13 min read

Most freelancers treat the discovery call as a formality — a quick chat before sending a proposal. That is a costly mistake. The discovery call is the single most important conversation in a client relationship. Done right, it tells you exactly what to propose, how to price it, and whether you should take the project at all.

Done wrong, you spend an hour talking about yourself, send a proposal that misses the mark, and wonder why you never hear back. Or worse: you land a client who turns out to be a nightmare because you never asked the questions that would have revealed the red flags upfront.

This guide gives you a complete framework for running discovery calls that convert — including a pre-call checklist, a word-for-word call structure, 20 questions to ask, objection-handling scripts, follow-up templates, and a list of red flags that should make you walk away. Whether you are new to freelancing or have been doing this for years, a better discovery process means better clients, higher rates, and fewer projects that go sideways. See also: how to get freelance clients and our freelance pricing guide for the full picture.

What Is a Discovery Call?

A discovery call is a structured conversation between a freelancer and a prospective client before any proposal, contract, or paid work begins. Its purpose is not to sell yourself — it is to discover whether there is a fit and, if so, what the right solution looks like.

Think of it as a diagnostic conversation. A good doctor does not prescribe medication the moment you walk in the door. They ask questions, listen carefully, probe for root causes, and only then recommend a treatment plan. A discovery call works the same way. You are gathering the information you need to prescribe the right solution at the right price.

Discovery calls typically run 30 to 60 minutes and happen before you write a proposal. They replace the old pattern of emailing back and forth trying to understand scope — one focused call is worth ten email threads. After a good discovery call, writing your proposal should feel easy because you already know exactly what the client needs.

Pre-Call Preparation Checklist

The 15 minutes you spend preparing before a discovery call are some of the most valuable time you can invest. Walking in cold wastes the client's time and yours. Walk in prepared and you look professional from the very first second.

1 Research the client's business Before the Call

Visit their website. Read their About page. Look at their products or services. Check their LinkedIn, Instagram, or any other public profiles. Your goal is to understand what they do, who their customers are, and how they position themselves in the market. You should be able to say: "I took a look at your site before this call and noticed X" — that sentence alone signals professionalism that 90% of freelancers skip.

2 Review their initial inquiry Before the Call

Re-read the email or form submission that started this conversation. Note every detail they shared: what they said they need, their timeline, any specifics about their project. Highlight anything vague or unclear that you will want to clarify on the call. Never ask a client to repeat information they already gave you in writing — it signals you did not pay attention.

3 Look at their competitors Before the Call

Spend five minutes on two or three of their main competitors. Understand the landscape they are operating in. This context helps you ask smarter questions and position your solution in terms of competitive advantage — language that resonates with business owners.

4 Prepare your question list Before the Call

Print or pull up your discovery call questions (see the full list below). Mark the five to eight questions most relevant to this specific client based on your research. Do not memorize them word for word, but know them well enough that you can ask naturally rather than reading from a script.

5 Know your availability and rates Before the Call

Before the call, know your current availability: when you can realistically start, what your capacity is for the next 30 to 60 days, and what your target rate range is for this type of project. You do not need to quote a price on the call, but you need to be ready to respond if the client asks about budget ranges or timelines without hesitation.

6 Set up your environment Before the Call

Test your video and audio if it is a video call. Have a notepad or open document ready to take notes. Close distracting tabs and silence notifications. Find a quiet spot with good lighting. If you look distracted or unprepared in the first 30 seconds, the client immediately loses confidence in you as someone who could manage their project.

20 Questions to Ask on a Discovery Call

Great discovery calls are question-driven. Your goal is to understand the client's situation deeply enough that your proposal feels inevitable — like you already knew exactly what they needed before you wrote it. These 20 questions are organized by category. You will not ask all 20 on every call; choose the ones most relevant to the project type.

Goals and Context

Question 1
"What is the main goal you are trying to achieve with this project?"
Why it matters: Gets past surface-level deliverables to the underlying business objective. A client who says "I need a website" is actually trying to get more customers, establish credibility, or something else entirely. Know the real goal.
Question 2
"Why is this a priority right now?"
Why it matters: Reveals urgency and business context. A company that just got funding moves differently than one that has been planning this for two years. Urgency also signals how much they value speed, which can justify premium rates.
Question 3
"What does success look like for you, six months after this project is complete?"
Why it matters: Forces the client to think in outcomes rather than deliverables. Their answer gives you the language to use in your proposal and the metrics by which the project will ultimately be judged.
Question 4
"What have you tried before, and why did it not work?"
Why it matters: Reveals past failures, so you do not repeat them. Also tells you whether this is a client who has tried DIY solutions, worked with other freelancers, or is doing this for the first time — each has different expectations and risk levels.

Scope and Deliverables

Question 5
"Can you walk me through exactly what you have in mind for this project?"
Why it matters: Opens the door for the client to describe their vision in their own words. Listen for scope gaps, unrealistic expectations, or assumptions you will need to address in your proposal.
Question 6
"Are there any examples of work you love that I should be aware of?"
Why it matters: Gives you creative direction before you start. It also reveals whether the client has taste and a clear point of view, or whether they will struggle to give useful feedback later.
Question 7
"What is out of scope for this project — what are you definitely not trying to do?"
Why it matters: Defining what is out of scope is just as important as defining what is in scope. This question prevents scope creep by establishing clear boundaries from the start.
Question 8
"What assets, access, or information will I need from you to get started?"
Why it matters: Identifies potential blockers early. If the client does not have brand guidelines, logo files, or copy ready, the project will stall. Knowing this upfront lets you build client responsibilities into your timeline and contract.

Budget and Decision-Making

Question 9
"What budget range are you working with for this project?"
Why it matters: The most important question on the call. Without budget information, you could spend hours crafting a proposal for a client who cannot afford you. Ask early enough that you can end the call gracefully if there is no alignment.
Question 10
"Who else is involved in making this decision?"
Why it matters: Reveals whether you are talking to the decision-maker or a gatekeeper. If there is a committee, a boss, or a board involved, your proposal needs to be written for them too — and you need to know if a second call or meeting is required.
Question 11
"Have you worked with freelancers or agencies on projects like this before?"
Why it matters: Calibrates expectations. Clients who have worked with experienced freelancers understand the process. First-timers need more education about timelines, revision rounds, and how projects actually work.
Question 12
"If we move forward, how would you prefer to pay — deposit upfront, milestone-based, or another structure?"
Why it matters: Opens the payment discussion naturally. Their response tells you how financially sophisticated they are and whether they are comfortable with professional payment terms. Resistance here is a yellow flag.

Timeline and Process

Question 13
"Do you have a specific deadline or launch date?"
Why it matters: Hard deadlines change everything about how you scope and price a project. Urgent projects command rush fees. Vague timelines let you control the schedule rather than being driven by client pressure.
Question 14
"How quickly can you typically turn around feedback and approvals?"
Why it matters: The project timeline is only as fast as the client's feedback loop. Clients who take two weeks to respond to drafts blow up every schedule you build. This question surfaces that risk before you commit to a timeline.
Question 15
"What is your preferred communication style — email, calls, project management tools?"
Why it matters: Mismatched communication expectations cause friction. Some clients want daily updates; others want to be left alone until you deliver. Know which type you are dealing with before you start.

Relationship and Fit

Question 16
"What does your ideal working relationship with a freelancer look like?"
Why it matters: Some clients want a collaborative partner; others want someone who executes and stays out of the way. Neither is wrong, but a mismatch in working style makes even good projects miserable.
Question 17
"What are the biggest concerns or risks you have about this project?"
Why it matters: Surfaces hidden objections before they derail the proposal. If you know they are worried about budget overruns, you can address it proactively. If they are worried about quality, you can discuss your revision process.
Question 18
"How did you find me, and what made you reach out?"
Why it matters: Tells you which of your marketing channels is working and what specifically attracted this client. It also reveals how much research they did — someone who read your case studies is more qualified than someone who clicked an ad.
Question 19
"Are you talking to other freelancers or agencies for this project?"
Why it matters: Tells you whether you are the only option or one of three. If they are shopping around, you need to know what differentiates you and how your proposal should be positioned. It also affects urgency.
Question 20
"Is there anything you think I should know that we have not covered?"
Why it matters: The catch-all question that often surfaces the most important information. Clients regularly share deal-making or deal-breaking context in response to this open-ended close. Never skip it.

The Discovery Call Structure (Minute by Minute)

A great discovery call follows a clear arc: warm up, dig in, propose a direction, confirm next steps. Here is how to run the full call from the moment you join to the moment you hang up.

Minutes 1–5: Warm Up and Set the Agenda

Start with 60 seconds of light small talk — nothing forced, just a brief human connection. Then immediately set the agenda for the call so the client knows what to expect.

Script — Opening

"Great to meet you. I really appreciate you taking the time. Before we dive in, here is what I am thinking for today: I will spend most of this time asking you questions so I really understand what you are trying to achieve. Toward the end, I will share some initial thoughts, and we can talk about potential next steps. Does that work for you?"

This framing does two things: it signals that you will be asking questions (not pitching), and it positions you as someone with a process rather than someone improvising.

Minutes 5–30: Ask Questions and Listen

This is the heart of the call. Work through your prepared questions, but do not treat it as an interrogation. Let the conversation flow naturally. Follow interesting threads. When the client says something important, reflect it back: "So if I understand correctly, the real challenge is X — is that right?"

Take notes on everything. Specific phrases clients use to describe their problem often become the most powerful copy in your proposal. Aim to talk no more than 30% of the time during this phase. Your job is to listen.

Pro Tip

After the client answers a question, pause for two full seconds before speaking. Most people rush to fill silence. That pause often prompts the client to add critical context they would not have shared otherwise.

Minutes 30–45: Share Initial Thoughts

Once you have gathered enough information, briefly summarize what you have heard and share an initial perspective on approach. This is not a full proposal — it is just enough to show you understood the problem and have a point of view.

Script — Summarizing and Proposing Direction

"Based on everything you have shared, it sounds like the core challenge is [X], and the outcome you are really after is [Y]. The way I would typically approach something like this is [Z]. Before I put together a formal proposal, does that direction resonate with you?"

This "does that resonate?" check is critical. If the client says no, you still have time to adjust. If they say yes, your proposal is already half-written in their mind.

Minutes 45–60: Handle Objections and Confirm Next Steps

After sharing your initial direction, objections may surface — budget concerns, timeline worries, uncertainty about process. Handle them calmly (see the objection section below). Then close the call with crystal-clear next steps.

Script — Closing the Call

"This has been really helpful. Here is what I am thinking for next steps: I will put together a detailed proposal that covers scope, timeline, and investment. I typically get those out within two business days. Once you have reviewed it, we can schedule a quick follow-up call if you have any questions. Does that timeline work for you?"

Handling Common Objections

Objections on a discovery call are not rejections — they are requests for more information or reassurance. Here is how to handle the most common ones.

"Your rates seem high."

Do not immediately discount. Instead, reframe around value: "I understand — and I want to make sure the investment makes sense for your goals. The way I price is based on the outcome we are trying to achieve, not just the hours involved. If [the outcome they described] is important to the business, the return on this investment should be clear. That said, I am happy to look at scoping options that fit your budget — what range were you working with?"

"Can you do it faster?"

Faster is always possible, but it has a cost: "I can absolutely look at a compressed timeline. Generally, rushing a project requires either additional resources on my end or a reduction in scope to maintain quality. Which matters more to you — hitting the deadline at the original scope, or delivering something lighter but on time?" Let them make the trade-off explicit.

"We need to think about it."

This is the classic soft no that might become a yes with the right follow-up: "Absolutely, I want you to feel confident in your decision. Is there anything specific you need to think through — budget, timing, something about the approach? I am happy to address any questions before you decide." Then ask: "When do you think you will have a sense of which direction you want to go?" Get a date.

"We are also looking at [cheaper freelancer / agency / internal hire]."

Acknowledge the comparison without panicking: "That makes sense — it is smart to evaluate options. The main difference in working with me is [specific differentiator: experience, process, past results, niche expertise]. I am not the cheapest option, and I do not try to be. If [outcome they care about] is the priority, here is what makes my approach particularly well-suited to that..."

The Follow-Up: What to Do After the Call

The discovery call does not end when you hang up. What you do in the next 24 hours matters just as much as the call itself.

Send a recap email within 2 hours. While the conversation is fresh, send a brief email summarizing what you discussed: what you understood their goals to be, your initial thoughts on approach, and the agreed-upon next steps. This email shows professionalism, confirms you listened, and creates a paper trail that protects both of you if scope disputes arise later.

Write your proposal within 48 hours. Momentum is everything in sales. Every day between the discovery call and your proposal is a day the client is second-guessing their decision or being contacted by a competitor. Strike while the conversation is still fresh in their mind. See our guide on freelance pricing for how to structure and price your proposal confidently.

Personalize the proposal with their words. Use the exact language the client used to describe their problem and goals. When a client sees their own words reflected in your proposal, it confirms that you heard them — which is far more persuasive than any feature list or credential you could list.

Free Tool

Create a Professional Invoice in Minutes

Once your proposal is accepted, send a polished invoice immediately. ToolKit.dev's free invoice generator takes 60 seconds and creates invoices clients actually pay.

Generate Your Invoice Free

Discovery Call Red Flags to Watch For

Not every discovery call should end in a proposal. The call is also your chance to screen out clients who will cost you more than they are worth. These are the red flags that should make you think twice — or walk away entirely.

Red Flag

They bad-mouth every previous freelancer or agency. If a client has a pattern of bad experiences, the common denominator is the client. Proceed only if you can get a detailed, specific, credible account of exactly what went wrong — not a vague "they were terrible."

Red Flag

They refuse to discuss budget at all. Some budget resistance is normal and manageable (see the objection section above). But a client who categorically refuses to share any number, range, or context around investment is almost always going to cause payment problems. Professional clients understand that budget alignment saves everyone time.

Red Flag

They want you to start immediately before anything is signed. "We will sort out the contract later" is how you end up doing free work. No exceptions. The contract and deposit come before any billable work begins, period. See our advice on finding and vetting freelance clients for more on this.

Red Flag

The scope is wildly unclear and they resist defining it. Some vagueness at the discovery stage is fine — that is partly what you are there to clarify. But a client who cannot or will not give you any clear parameters for what success looks like is setting you up for an endless project with no finish line.

Red Flag

They ask you to work "on spec" or for equity. Work on speculation (you build it, and if they like it, they pay you) is almost never worth it. Equity deals for freelance service work almost never materialize. If a client cannot pay you for your time, they are not a real client.

Red Flag

Every decision requires committee approval from people not on the call. Multiple stakeholders are not automatically a problem, but if approval requires six people none of whom you have met, and none of whom will be in your feedback loop, you are going to be trapped in revision purgatory. Map the decision-making structure clearly before you commit.

When to Say No (And How to Do It)

Saying no to a project is one of the most powerful things a freelancer can do. Every bad client you take is a client who takes time away from good ones. Your time, energy, and reputation are finite resources — spend them wisely.

Say no when the budget is genuinely too low for the work required and the client will not budge. Say no when multiple red flags appeared on the discovery call. Say no when the project is outside your area of expertise and the client expects you to pretend otherwise. Say no when your gut tells you this person will be difficult to work with.

How to decline gracefully:

Script — Declining a Project

"Thank you so much for the time on our call — I genuinely enjoyed learning about what you are building. After reflecting on it, I do not think I am the right fit for this particular project at this time. [Brief reason: budget alignment / project type / capacity / other.] I want to make sure you find someone who can give this the attention it deserves. Best of luck — and feel free to reach out on future projects."

You do not owe an extended explanation. Keep it brief, warm, and final. Do not leave the door open in a way that invites negotiation if you have already decided.

Remember

A discovery call you end without a deal is not a failure. It is due diligence. The freelancers who build sustainable, high-quality practices are the ones who are selective — not the ones who say yes to everything and spend their time managing difficult clients at low rates.

Recommended Resource

Client Proposal Toolkit — $11

Turn your discovery call notes into a winning proposal. Includes proposal templates, pricing frameworks, objection-handling scripts, and follow-up email sequences — everything you need to close more projects at better rates.

Get the Proposal Toolkit →

Frequently Asked Questions

What is a client discovery call?
A client discovery call is a structured conversation between a freelancer and a potential client before any proposal or contract is written. Its purpose is to understand the client's goals, challenges, timeline, and budget so you can determine whether the project is a good fit and, if so, propose the right solution at the right price. Discovery calls are not sales pitches — they are diagnostic conversations. The best ones involve you asking most of the questions while the client does most of the talking.
How long should a client discovery call be?
Most client discovery calls run 30 to 60 minutes. For small or straightforward projects, 30 minutes is enough to understand the scope, confirm budget alignment, and agree on next steps. For complex projects — rebrands, long-term retainers, multi-phase builds — plan for 60 minutes. Avoid going longer than 60 minutes in the first call. If you need more information, schedule a follow-up. Respecting a prospective client's time makes a strong first impression.
Should I charge for a discovery call?
For standard 30-minute discovery calls, most freelancers do not charge. It is considered part of the normal sales process. However, if a client requests a longer strategy session (60+ minutes) or asks you to prepare research, a detailed brief, or a presentation before you have been hired, it is reasonable to charge a discovery fee — typically $150 to $500 depending on your rates. Frame it as a "paid strategy session" that gets credited toward the project if they hire you. This also filters out time-wasters who are not serious.
What are the biggest mistakes freelancers make on discovery calls?
The most common mistakes are: talking too much instead of listening, jumping straight to solutions before fully understanding the problem, failing to ask about budget and decision-making authority, not asking about timeline and urgency, giving a price quote on the call before you have thought it through, and failing to confirm clear next steps before hanging up. Discovery calls are about information gathering, not impressing the client with your knowledge. Ask more, talk less.
How do I handle a client who refuses to share their budget?
Budget resistance is common. Most clients worry that sharing a number will cause you to inflate your price to match it. Try reframing the question: "I ask about budget not to max it out, but to make sure I recommend the right scope. A $3,000 project looks very different from a $15,000 one." If they still refuse, offer three tiers: "I work on projects in the $5k, $10k, and $20k+ range depending on scope — does any of those ranges sound like where you are thinking?" This usually gets a response. If a client truly refuses to engage on budget at all, that is a yellow flag worth noting.

Ready to Send an Invoice After Your Next Winning Call?

You ran a great discovery call. The client said yes. Now send a professional invoice in 60 seconds — for free.

Create a Free Invoice Now

Or grab the Complete Freelancer Toolkit ($24) for contracts, proposals, invoice templates, and more.