A discovery call does two jobs that pull in opposite directions. You want to understand the client well enough to write a proposal that wins. You also want to find out, within thirty minutes, whether this is a project you should take at all. Freelancers who treat the call as a pitch tend to talk too much and learn too little. Freelancers who treat it as free consulting give away the answer and never hear back.
This checklist keeps the call structured. It covers what to research beforehand, a simple agenda, the questions that qualify a lead, the red flags worth noticing, and a follow-up routine that moves good leads to a proposal quickly.
TL;DR
The discovery call checklist covers pre-call research, a 30-minute agenda, questions on the problem, goals, success measures, budget, timeline, decision-makers and past attempts, a red-flag list, and a recap email sent within 24 hours. Use it for every new lead before writing a proposal. The question freelancers most often skip is who else approves the decision; ask it on every call.
What's inside
- Pre-call research — the client's website, recent news, the person you are speaking with, how they found you.
- Agenda — a simple 30-minute structure to share at the start.
- Questions — grouped into problem, goals, scope, budget, timeline, decision process and fit.
- Red flags — signals that a project may be a poor fit.
- Scoring — a quick fit score to decide whether to propose.
- Follow-up — recap email, proposal date, or a polite decline.
When to use it
Use it for every inbound lead that looks like a real project, and for referral introductions where you have not worked with the person before. It suits design, development, marketing, consulting, coaching and creative services.
Send a short client intake form before the call if you want basic facts in advance. After a good call, write the freelance proposal within two or three business days. Once the project is signed, the project kickoff agenda takes over.
Questions that qualify a lead
The problem. "What's prompting this now?" tells you urgency. A project triggered by a launch date, a new funding round or a failing current system moves faster than "we've been meaning to do this."
Success. "In six months, what would make you say this was worth it?" gives you the outcome to write the proposal around.
Budget. Ask directly and offer a range. "Projects like this usually fall between X and Y depending on scope. Where does that sit against what you had in mind?" Clients who will not engage with any number are often not ready to buy.
Decision-makers. "Who else will be involved in deciding?" A proposal that reaches a co-founder or finance lead who was never on the call often stalls. Ask whether they should join the next conversation.
Past attempts. "Have you tried to solve this before? What happened?" reveals expectations and sometimes a history of difficult working relationships.
Timeline. "Is there a date this needs to be done by, and what happens if it slips?" separates real deadlines from wishes.
Red flags worth noticing
- The client wants detailed ideas or a sample before agreeing to a paid engagement.
- Budget is far below the range and scope is not flexible.
- The decision-maker is unknown or unreachable.
- They describe several previous freelancers as incompetent.
- The deadline is unrealistic and fixed.
- They want to start tomorrow but resist a deposit.
None of these is automatically a no. Two or three together usually are.
Customize it in your COLO workspace
After a good call, you can send a COLO proposal with line items for rate, hours, tax and discount, an expiry date and comments. The client accepts or declines it in the client portal, and you can convert an accepted proposal into an invoice. See Proposals.
You can save proposal templates for your most common project types, so the post-call proposal goes out within a day or two.
Common mistakes
- Pitching instead of listening. Aim to talk less than half the time.
- Avoiding the budget question. You may write a proposal for a client who cannot afford it.
- Solving the problem on the call. Describe your approach, not the full answer.
- No recap. A same-day summary is where you start to win the work.
- Missing the real decision-maker. Ask who else decides, every time.
FAQ
Q: What is a discovery call?
A discovery call is a short first conversation with a potential client to understand their problem, goals, budget, timeline and decision process, and to decide together whether to move to a proposal.
Q: How long should a discovery call be?
Twenty to forty-five minutes is typical. Long enough to understand the problem and qualify the lead, short enough that you are not consulting for free.
Q: How do I ask about budget without being awkward?
Ask directly and early, and offer ranges. For example: projects like this usually fall between X and Y depending on scope; where does that sit against what you had in mind?
Q: Should I give a price on the discovery call?
Usually not a final price. Giving a rough range is helpful for qualification. Send a written proposal after the call, once you understand the scope. The guide on how to write a freelance proposal that wins covers the next step.
Q: What should happen after a discovery call?
Send a short recap within 24 hours with what you heard, the next step, and a date for the proposal. If it is not a fit, say so politely and, if possible, suggest someone who is.