The discovery call script that filters out bad-fit clients

Most discovery calls are demonstrations. The agency talks about its process, the prospect nods, and everyone leaves with a warm feeling and no information. Then someone spends a day writing a proposal for a project that was never going to happen.

A discovery call has one job: work out whether this is worth a proposal. Scope and price come second. If you run the call properly, a fair share of the time the honest answer is no — and finding that out in 45 minutes rather than after a week of writing is the entire return on doing it well.

The shape of the call

Forty-five minutes, in this order. The order matters — budget before scope, because scope you can't afford is a fantasy you'll both waste time on.

Minutes	Section	What you're trying to learn
5	Frame	Set expectations, get permission to ask directly
10	The problem	What's actually broken, and for whom
10	Decision and money	Who signs, what's approved, by when
10	History and constraints	What they've tried, who else is bidding
5	Their questions	What they're worried about
5	Close	Agree a specific next step

That's 45 minutes. Talk for less than a third of it.

Open by naming what the call is for

Say this in the first two minutes and the rest of the call gets easier:

Before we start — I'm going to ask some direct questions about budget, timing and who makes the decision. Not to be awkward, but because I'd rather tell you in the next half hour if we're not the right fit than send you a proposal that wastes both our time. Is that alright?

Nobody says no to that. What you've bought is permission to ask about money without it feeling like a sales move, and a reason to walk away later that you've already announced.

The problem, not the request

Clients arrive with a solution already chosen. "We need a new website." "We need to be doing more on LinkedIn." Your job is to get one level underneath it, because that's where the actual project is.

• What made you start looking at this now, rather than six months ago?
• Walk me through what happens today. Where does it break?
• Who inside the business is most affected by this? What do they say about it?
• If we do nothing for another year, what does that cost you?
• How will you know this worked? What number or outcome changes?

The last one is the sharpest. A client who can answer it — "we want to go from four qualified leads a month to twelve" — is a client who will recognise success. A client who can't will judge the work on whether they personally like it, which is a project you cannot win.

Bad answers to listen for: "we just feel like it's time", "the board wants to see something new", "we'll know it when we see it". None of these are disqualifying alone. All three together mean the success criteria will be invented after you deliver.

Decision and money, before scope

This is the section people skip. Don't.

• Who else needs to say yes to this before it starts?
• Have they been part of the conversation so far, or will they see it for the first time in the proposal?
• Has a budget been approved for this, or are you still working out what it should be?
• What range were you expecting? I'll tell you straight away whether we're in it.
• What's driving the timing — is there a date this has to be done by?

On budget, if they deflect with "what do you normally charge", give a real range and watch the reaction:

Projects like this usually land between [X] and [Y], depending mostly on [the one variable that actually moves the price]. Does that sound like the right neighbourhood, or is it a long way off?

You are not negotiating. You are checking whether to continue. A prospect who flinches at your floor has told you something useful and free.

Bad answers to listen for: "we don't really have a budget, surprise us", "I'd need to check with the owner, he's not really involved yet", "we want to see proposals first and then decide what we can spend". The last one usually means you're being used to build a business case, and you'll be the reference price for whoever they hire.

History and competition

• Have you done a project like this before? How did it go?
• Are you working with anyone else on this at the moment, or have you recently?
• Why did that end?
• Who else are you speaking to about this?
• What would make you pick someone else?

The "why did that end" answer is the most informative sentence in the whole call. Listen for whether they describe a shared failure or a villain. A client who says "we didn't give them enough access and it stalled" is telling you they've learned something. A client whose last three suppliers were all incompetent is telling you about their fourth.

Asking who else is bidding sounds cheeky and almost always gets answered. If they name a much larger firm, you know what you're being compared against. If they name nobody and can't say what would make them choose differently, the decision may not be as close as they're implying.

The disqualifying combination

No single answer should end a call. Patterns should. Walk away — politely, and say why — when you see three or more of these together:

• The decision-maker hasn't been in any conversation
• No budget approved, and no range they'll confirm
• Success can't be described in any concrete terms
• The deadline is fixed and already unrealistic
• They've been through two or more suppliers on the same problem
• They want a detailed proposal before a scoping conversation
• Every question about money gets redirected to your competitors' pricing

Saying no here is cheap. Saying no in month three of delivery is not.

Close with a specific next step

Never end on "I'll put something together and send it across." End with the smallest concrete commitment you can get:

Here's what I'd suggest. I'll write this up as a short proposal — four pages, not forty — and send it by [day]. Can we get 30 minutes in the diary now to go through it, with [decision-maker] on the call? If they can't make it, I'd honestly rather wait until they can.

Booking the review call before you write the proposal does two things. It tests whether the interest is real, and it means your document gets discussed rather than forwarded and forgotten.

If they won't book it, that's your answer about how likely this is to close — and it's worth knowing before you spend a day writing.

This week

Take your next three discovery calls and add just the money-and-decision block: who else says yes, is there an approved budget, what range were they expecting. Five minutes, three questions.

Then write down, after each call, the one sentence you'd need to be true for this project to be worth a proposal. If you can't write that sentence, don't write the proposal.