They asked for pricing. Then the conversation stopped.

Picture a demo that ends with a request for pricing. The seller sends it, sees no reply and starts rewriting a follow-up. The question beneath the email is uncomfortable: did the price end the conversation, or was the conversation never as far along as it seemed?

In a May 2026 Reddit discussion, a cybersecurity account executive described prospects going quiet after customized demos and pricing emails. The thread offered competing explanations. None could establish the reason for every silent buyer.

Before writing another message, read the buyer’s original request. Were they gathering a budget estimate or preparing to choose a supplier? Build the follow-up around that purpose and leave room for the purpose to have changed.

Make the pricing usable when you send it

Before worrying about the follow-up, check the original message. Can the buyer see what the price includes, what it depends on and which questions remain open?

For a services proposal, assumptions about scope or customer responsibilities may materially affect the amount. For software, the relevant unit might be a seat, a usage measure or an agreed package. Explain the real basis of your offer without inventing a simple fixed price where none exists.

Do not require another meeting merely to reveal information you can responsibly provide in writing. If a discussion would clarify the quote, offer one and explain what it would resolve.

Recover the decision the buyer was making

Reopen your notes. Did the buyer ask for a rough budget range, a formal quote for procurement or a proposal they intended to evaluate with colleagues?

Those requests imply different next steps. A person collecting budget information may have no immediate project. Someone comparing suppliers may need a clear scope difference. A champion seeking approval may need a buyer-owned business case alongside the commercial document.

If you never established the purpose, admit the gap. Do not convert the request for a price into evidence that purchase approval was close.

Send a follow-up that can be answered

Here is an illustrative message for a buyer who said they needed a budget range for an internal discussion:

You mentioned using the estimate for your planning conversation. The range I sent assumes the current scope, including the two integrations we discussed. Is there a missing detail that would help your team assess it, or has the timing changed?

Use that wording only if those details are true. A different history needs a different message.

The note gives the buyer an easy correction. It also offers help with the decision rather than asking them to explain why they have not replied.

Investigate without inventing a diagnosis

Several explanations may fit the same silence:

Possibility	Useful check
The scope is unclear	Ask which assumption needs clarification.
The buyer is waiting for someone else	Refer to the process they described, if they described one.
Timing has changed	Offer a simple way to confirm a later review point.
The offer is unsuitable	Invite an honest correction without arguing with it.
The person does not want more contact	Respect the stated preference and your suppression rules.

These are possibilities to test, not explanations to put into the CRM as facts. An email being opened, where that information is available, does not answer them.

Agree on a next step before there is a gap

For future conversations, ask how the buyer expects to use the pricing and whether a follow-up would be useful. If they agree to a review date, record what is being reviewed and who needs to be involved.

Do not manufacture urgency with a deadline that has no commercial basis. Equally, do not promise an indefinite price commitment if your offer has a real validity period. State the actual terms plainly.

When several unanswered contacts have provided no new information, follow your team’s stopping rule. A short closure message can leave room for a later conversation without demanding one now.

Review the pattern across actual opportunities

Keep the buyer’s stated purpose, what you sent, whether a next step was agreed and the eventual outcome. Review completed cases as well as stalled ones. You may discover a recurring explanation, or you may find several different problems that all looked like ghosting.

RevQ describes drafting proposals and follow-ups from conversation context. A useful evaluation would check whether the draft preserves the purpose of the pricing request and the unresolved assumptions. It cannot know why a buyer is silent unless the evidence says so.

If the buyer replies that the project has moved to next year, record that change and agree whether further contact would help. A clear pause is a usable answer, even when it is not the answer the seller hoped for.

About this article: AI-assisted writing and editing, informed by the linked public discussion. Illustrative examples are labelled; they are not customer case studies. Read our editorial approach.

Updated October 3, 2026