Why deals stall at the proposal stage

A proposal going quiet feels like a failure of the proposal. It was sent, it was not answered, so presumably something about the document was wrong — the price, the length, the formatting. Occasionally that is true. Far more often the proposal is fine and it is being sent into a situation that could not have produced a decision regardless of what the document said, and the situation was created weeks earlier, in conversations that felt like they were going well.

This is why the proposal stage is the most misdiagnosed part of a pipeline. It is the first point where the buyer has to actually do something — get an approval, commit a budget, argue internally for a change — and everything that was comfortable to leave unexamined becomes load-bearing. A deal that reaches this stage with an unverified assumption does not fail visibly; it just stops moving, and silence looks the same regardless of cause. There are five common causes, they need completely different responses, and telling them apart is the whole task.

The most common cause, and the most preventable. Your contact was engaged, knowledgeable and enthusiastic, so nobody ever asked whether they could actually approve the spend. Now the proposal is in their hands and their job has quietly become selling it internally to somebody who has not spoken to you, using a document written for a reader who already understands the problem. Most people are not good at that, and many will not attempt it — the proposal simply sits, and your contact goes quiet because there is nothing they can report.

The symptom is a contact who stays friendly but stops being specific. Answers become "still with the management" or "waiting on approval" with no date attached. The response is to make the internal sale possible rather than to keep asking: offer a one-page summary written for the person who signs, in their terms — cost, what changes, what happens if nothing changes — and offer to join a short call with them. Prevention is one question during qualification, asked as process rather than status: what would you need from me to take this to whoever signs off?

This one hides well, because budget rarely gets denied outright in conversation. The buyer said the price was in the right range, or did not object when you mentioned it, and that absence of objection was recorded as confirmation. What it often meant was that the figure sounded acceptable in the abstract, in a conversation where nobody had to move money. The proposal is the point where somebody does, and the money turns out to be committed elsewhere, or to require an approval nobody has requested yet.

The tell is a buyer who engages enthusiastically with everything except the commercial section, or who asks for a version with less in it before discussing the version you sent. Neither is a rejection — they are signs of a ceiling nobody named. The productive response is to ask directly what would fit, and to make the smaller version genuinely coherent rather than a discount. A first phase that stands on its own is a real answer to a budget ceiling. A trimmed proposal that no longer does the job is worse than the original, because now the buyer is choosing between too expensive and not worth doing.

This is the least comfortable cause to consider, because it means the misunderstanding is yours. The buyer described a problem, you understood it in terms of what you sell, and the proposal solves the version of the problem you recognised rather than the one they have. It looks thorough and competent from your side, and from theirs it reads as slightly beside the point — not wrong enough to argue with, not right enough to buy.

Buyers rarely correct this, which is what makes it durable. Explaining that a supplier has misunderstood them takes effort and creates an awkward conversation, and going quiet is easier. The prevention is the recap message sent shortly after the first conversation, stating the problem as you understood it in their words and inviting correction while correction is still cheap. If a proposal has already gone quiet and you suspect this is why, the recovery is to ask directly what you got wrong, with a genuine willingness to hear that the answer is quite a lot. That question is answered surprisingly often, because it costs the buyer nothing to answer honestly.

A deal can have a real need, a real budget and a real decision-maker, and still stop, because nothing bad happens if the decision is postponed. This is the quietest cause of all: everyone involved genuinely intends to proceed, the proposal is genuinely acceptable, and the decision keeps losing to whatever is on fire that week. Postponement is not a rejection and it does not feel like one, which is why deals in this state can stay open for months while everyone remains optimistic.

The diagnostic is to ask what is driving the timing, and to notice whether the answer names something that exists independently of the buyer's intentions. A lease ending, a season starting, an audit scheduled, a contract expiring, a person joining — those are dates that arrive whether or not anyone acts. "We would like to sort this out soon" is not a date. If there is genuinely no forcing event, the honest move is to stop treating the deal as live: record what would create urgency, set a date tied to it, and reduce the effort you are spending. Optimism about a deal with no forcing event is the most expensive kind in a pipeline.

The fifth cause is the absence of somebody inside the buyer's organisation who wants this to happen and will spend their own credibility to make it happen. A champion is not the same as a decision-maker and not the same as a friendly contact. It is a person for whom the current problem is personally inconvenient, who will chase the approval, answer their colleagues' objections and revive the conversation when it lapses. Deals with one behave completely differently: they come back to life without your involvement.

The test is whether anything has ever moved without you pushing it. If every step in the deal was initiated by you, there is no champion, however warm the conversation has been. The response is to work out whose day gets easier and make that person the audience for the proposal, in language about their problem rather than the organisation's. This is also the point to be honest with yourself: a deal with no champion, no forcing event and an unconfirmed budget is not a deal at a late stage. It is an early-stage conversation with a proposal attached, and treating it as nearly closed distorts every forecast it appears in.