Why Prospects Go Quiet After a Good Discovery Call

The call went well. They talked more than you did. They described the problem in their own words, agreed with your read on it, asked what the next step was. You sent the proposal that evening.

Then nothing. A week of nothing. You follow up and get a warm, apologetic reply about timing. You follow up again and get silence.

The standard explanations are that you didn't create enough urgency, or your follow-up sequence was weak, or the price scared them. Occasionally that's it. Far more often something less flattering and more fixable is true: the deal was never going to close on the timeline you had in your head, and what you're reading as silence is the deal proceeding at its actual pace.

That's a different problem, and it has a different fix.

They weren't the person who signs

The most common version of this is that you had a genuinely good conversation with someone who cannot buy.

Not someone unqualified — someone real, with the problem, who wants it solved. They just aren't the one who releases the money. They're the Head of Operations and it goes through procurement. They're the founder but their partner has to agree. They're the marketing lead with a budget that needs sign-off above a threshold your price happens to exceed.

You will rarely be told this directly, because the person you're talking to often doesn't experience themselves as lacking authority. They intend to make it happen. From their side that's sincere. From yours it means your proposal is now sitting in a conversation you aren't in, being explained by someone who is not as good at explaining it as you are, to someone who never met you.

Every additional approver does two things: it multiplies the elapsed time, and it adds one more place where the deal can stop without anyone ever saying no. Nobody rejects you. It just doesn't come back.

So the question to answer on the first call isn't "are you interested." It's: is there anyone else who has to agree before this can happen? Asked plainly, most people answer honestly, and the answer tells you what you're actually looking at.

If the answer is yes, you have two options and they're both fine. Re-scope toward the person who can sign alone, or accept that this is a multi-approver sale and build for it — which mostly means giving your champion a one-page case they can forward without you in the room, written for the approver rather than for the user. Those are different documents. The user cares whether it works. The approver cares what it costs and what happens if it doesn't.

You never checked whether they could pay

The second version is simpler and slightly more embarrassing: you didn't know their budget, and you still don't.

Most people selling in the $2,000–$25,000 range describe their buyer in qualitative terms. "Established coaches." "Mid-market." "Six-figure businesses." "Founders who are serious about growth." These feel like qualification. None of them is a number, and you cannot disqualify anyone against a range you haven't defined.

The consequence isn't just wasted calls, though it's that too. It's that without a figure you have no way to tell the difference between this person can't afford it and this person isn't convinced yet — and those two require opposite responses. One is a disqualification and you should thank them and move on. The other is an objection and you should answer it. Treated identically, you spend weeks on the first and lose the second.

Write the figure down. Not "mid-market" but the actual revenue or budget band that can carry your price without it being a difficult decision. Then ask about it on the first call, early, before you've invested an hour in describing the solution.

This feels adversarial the first few times. It isn't — it's the most respectful thing you can do to someone who genuinely can't afford you, and it's a strong signal to someone who can.

Your forecast was wrong, so normal looked like silence

This is the one that changes how the other two feel, and it's the least discussed.

Say you're selling a $15,000 engagement to a mid-market company where a buying committee with procurement sign-off makes the decision. And say your pipeline assumes a one-week sales cycle, because that's roughly how long it took the last few times you sold something to a solo founder.

Those two facts cannot both be right. Group approvals do not close in a week. Procurement alone rarely moves that fast. So the one-week expectation is wrong — and everything downstream of it is wrong with it.

Here's what that does to you in practice. On day eight, a deal that is progressing entirely normally reads as dead. You mark it lost, or you start following up with an urgency the buyer can hear, which reads as desperation and makes you cheaper. Meanwhile the actual decision is happening at its own pace in a room you're not in, and it might well have closed if you hadn't spent day fourteen sending a message that undermined your position.

The tell is a mismatch between how the purchase is structured and how fast you think it happens. If more than one person has to agree and your forecast is under two weeks, one of those two numbers is fiction. Usually the forecast.

Fixing it costs nothing and changes your behaviour immediately. Re-forecast to the pace the approval structure actually implies, and day eight stops being a crisis. You stop sending the follow-ups that hurt you. Your pipeline stops lying to you about how many deals you have.

What to do differently on the next call

Three questions, asked early, before you've explained anything:

Who else has to agree before this happens? Not "are you the decision maker," which invites a yes. The indirect phrasing gets you the truth.

What's the budget range this would come from? Then compare it to your price and say so out loud if it doesn't clear.

How do purchases like this normally get approved here, and how long does that usually take? They will often tell you your sales cycle for you, and it will be longer than your spreadsheet says.

None of these is a closing technique. They're disqualification tools, and the value is in the calls you don't take afterward. If you're getting a lot of good conversations that don't convert, the volume of good conversations is not the achievement it feels like.

When it really is the offer

Everything above assumes the offer itself is sound and the problem is who you're selling it to. That's often true. It isn't always.

If you fix the authority question, define the budget band, re-forecast the cycle honestly — and deals still stall — then the buyer wasn't the constraint. At that point the thing to examine is whether your promise is specific enough to be compared against its price, and whether there's enough evidence behind it to justify a five-figure commitment from someone who just met you. Those are different faults with different fixes, and I've walked through all seven of them, including this one, in Why Your High-Ticket Offer Isn't Selling.

The order matters, though. Buyer readiness is worth checking first for an unglamorous reason: it's the cheapest of the seven to fix. Redefining who you sell to costs an afternoon. Building proof assets and rewriting your outcome promise take weeks. Start with the afternoon.

One honest caveat

Checking this on paper tells you whether your buyer definition is coherent — whether the authority, the budget, and the timeline you've written down can all be true at once. It doesn't tell you whether that buyer exists in the numbers you need, or whether they want what you're selling badly enough to prioritise it this quarter.

That's a narrower claim than predicting your close rate. But incoherence between those three is extremely common, it's invisible while you're inside it, and it produces exactly the symptom this post is about.

If you'd rather have this checked against your actual offer, OfferIntegrity scores buyer readiness alongside six other structural checks, flags contradictions like the committee-versus-one-week mismatch directly, and gives you the fixes in order of what they cost you. $39, one-time.