Why proposals stall and how to spot it early

A proposal that stalls was usually dead before you wrote it. The silence after you hit send isn't the problem. It's the first moment you're forced to notice the problem.

That's good news. If the stall starts upstream, you can catch it upstream.

The proposal is a symptom

In services, a proposal goes quiet for a short list of reasons. Nobody with budget authority asked for it. The problem it solves isn't the problem the buyer will defend to their boss. Or the champion who requested it can't get it onto anyone else's calendar.

None of those are pricing problems. Sellers love to blame price for a stall, since price is the one thing they can change on their own. But in deals between $50K and $500K, price is rarely why a buyer stops answering. Price is what they mention when they've already lost interest and want a polite exit.

So the question to ask about a stalled proposal isn't "what's wrong with the proposal." It's "what was wrong with the conversation that led to it."

Four signs you'll see before you send

The first sign is a one-person deal. If every call has been with the same contact, and nobody else has joined, you don't have a deal. You have a friend inside the account. Services buys are committee decisions. The economic buyer, the champion and the technical lead all need to have heard your name before paper moves. I wrote more on this in sell to the committee, not the contact.

The second sign is a request for a proposal before anyone has agreed on the problem. "Send me something and I'll take a look" sounds like progress. It's often a way to end the call. If you can't write the buyer's problem in one sentence that they've confirmed in their own words, the proposal is a guess dressed up in a format.

The third sign is a buyer who won't say what happens after the proposal lands. Ask plainly who reads it, who signs it and what meeting it goes to. A buyer with a real process will answer in ten seconds. A buyer without one will get vague, and vague is your answer.

The fourth sign is a timeline that belongs to you. If the only date in the deal is the end of your quarter, the buyer has no reason to move. Look for their date. A board meeting, a budget cycle, a system going end of life, a new leader's first 90 days. If there's no date on their side, there's no urgency on their side.

A scenario

Say you've had three good calls with a director of IT at a regional distributor. She likes your team. She asks for a proposal for a warehouse systems integration, and you send a clean one at $180K.

Two weeks of silence. Then a short note saying they're "reviewing internally."

Look back and the signs were there. All three calls were with her alone. Nobody from finance ever joined. When you asked about timing, she said "sometime this year." And the problem statement in your proposal was yours, not hers. She never said it back to you.

The proposal didn't stall. The deal never had the parts it needed to move.

What to do instead

Before you write a proposal, get three things on the record. A problem statement the buyer has confirmed in their words. The names and seats of everyone who'll read the document. And a date that matters to them, not you.

If you can't get those, don't write the proposal yet. Write a one-page summary of what you heard and send that instead. Ask the buyer to correct it. A correction tells you where your understanding is off, and it gives the champion something short to forward to the people you haven't met.

This feels slower. It isn't. A proposal that sits in an inbox for six weeks is the slowest thing in your pipeline.

Build the check into your stages

The easiest fix is to make these signs part of how you define stages. A deal doesn't move to proposal until the committee is mapped, the problem is confirmed and the buyer's date is known. If you want a starting point, see stage definitions for services sales.

Then review stalled proposals with the same lens every week. Not "when will they sign" but "which of the four signs did we miss." Patterns show up fast.

Proposals stall for reasons that are visible early. Look for them before you write, and you'll write fewer proposals that close at a higher rate.