Why buyers do not decide after a proposal: 7 reasons

You sent the proposal. A few days later, you asked whether the buyer had seen it. Then you asked whether they had decided. There is no answer, so you consider changing the document format, offering a discount or preparing another version.

Silence alone does not reveal the cause. Email can be an effective way to deliver a proposal. A repeat order for standard products may need no more than a clear message with the price and terms. In a more complex sale, check whether the buyer has what they need for the decision in front of them.

The seven situations below help you decide what to investigate before another reminder. They do not prove why your buyer is stuck. Each sign points to a question worth asking.

1. The proposal arrived before there was a defined buying decision

The sign. After receiving the proposal, the buyer asks again how different types of solution compare, or requests a price for a completely different scope. They may still be researching while you have already presented a final choice.

What to ask. “Are you comparing possible approaches, or selecting a supplier for an agreed scope?” Those are different tasks requiring different information.

What to do. If the scope is unclear, agree on the question to resolve before a final proposal. That may call for a comparison of two approaches, a demonstration using a sample of the buyer's data, or an indicative budget range with explicit assumptions. Do not make an early estimate look like a confirmed project price.

2. Your contact has a document but lacks material for the internal discussion

The sign. You hear “I sent it to my manager”, but do not know what the manager will assess. Your contact cannot explain what answer their colleagues need.

What to ask. “What questions will remain for someone who was not in our conversation?” Rather than asking the contact to chase colleagues, help them prepare for the discussion.

What to do. Provide a short summary they can forward: the situation being addressed, the reason for this scope, the total investment and what still needs checking. A technical colleague may first need a compatibility answer, while finance needs to understand recurring costs. Do not assume one generic presentation answers both.

3. The buyer sees options but cannot identify your recommendation

The sign. You offered several alternatives and the buyer asks you to explain them again. Or they select the cheapest despite a condition you discussed that it does not meet.

What to ask. “Which of the criteria we discussed will matter most in the choice?” If the criteria conflict, the buyer may need to choose a priority before comparing totals.

What to do. State the recommendation and its basis. For example: “We recommend the second configuration because it accommodates the operating condition you specified. The first would be suitable if that condition were removed.” If every option is suitable, explain the real trade-off rather than constructing an artificially weak alternative.

4. A broad work description hides different expectations

The sign. The buyer asks whether “implementation” includes cleaning up data, or whether “delivery” includes moving the equipment into position and commissioning it. You see additional work; they assumed it was part of the offer.

What to ask. “What will count as completed work, and what will your team prepare before it starts?” This reveals a responsibility gap as well as a pricing question.

What to do. Clarify the outcome, boundaries and dependencies of that part of the proposal. If new information changes the price, explain which assumption changed. A further discount alone will not reconcile two different understandings of scope.

5. The buyer cannot compare your offer fairly with an alternative

The sign. The only feedback is “another supplier is cheaper”, but you do not know whether the quantities, services and periods are equivalent.

What to ask. “Can we check which scope and terms differ?” The buyer does not have to disclose a competitor's confidential proposal. You can discuss comparison criteria without seeing the document.

What to do. Explain your price using the same decision-relevant fields: required configuration, preparation, commissioning, recurring fees and exclusions. If your offer costs more because it includes extra scope, establish whether the buyer needs it. The lower-priced supplier may be the right choice. A higher price or more attractive presentation does not establish higher value on its own.

6. Nobody has agreed how the proposal will be evaluated

The sign. Both sides agree the proposal “looks right”, but it is unclear who approves it, what is missing and when another conversation will be useful.

What to ask. “What specific question needs to be resolved before you can make the next decision?” “We need to discuss it” is a starting point: find out what needs discussing and with whom.

What to do. Agree on one meaningful action: a technical check, scope review, budget discussion or postponement until a defined condition is met. Learning that the buyer currently lacks priority or resources is useful too. Do not invent a deadline simply to give the follow-up a sense of urgency.

7. Nobody can identify the current version

The sign. One colleague is reviewing an old attachment, another has the revised total from an email, and you are working with a third configuration. “Have you decided yet?” is premature.

What to ask. “Which version are you evaluating, and does everyone involved have the same terms?”

What to do. Identify one clear current version. Add a short change summary: what changed, what remained, and whether the total or timing changed. If you share a continuously updated link, still communicate material changes separately. Before approval, make clear which scope and terms are being approved.

Replace “did you see it?” with a specific unresolved question

When you know the outstanding question, a follow-up can help even if the buyer is not ready to purchase. For example:

PRACTICAL EXAMPLE

We have not yet confirmed whether your team will handle commissioning or whether we should include it. That affects the scope being compared. Are you reviewing this with a technical colleague? If the project has been postponed, please let us know what would make it useful to revisit.

Adapt this to a real unresolved question. Do not claim something was discussed when it was not.

Check whether the issue repeats across your process

Silence in one opportunity does not establish that email, pricing or the entire proposal approach is failing. When reviewing several proposals, record their stage, scope clarity, known decision obstacle, next agreed action and actual outcome separately. “Reason unknown” is more accurate than an invented “too expensive”.

When comparing teams or order sizes, account for different decision periods and proposals still under evaluation. A small group or one lost order is not a sound basis for abandoning a whole customer segment.

Email, PDFs, proposal links and a CRM can all belong in a well-managed process. Choose the format around the buyer's task and your management needs. Resolve the uncertainty blocking the decision first, then assess which tool helps you do it.