What to Do When Prospects Ghost After a Demo

TL;DR: Silence after a demo is a record problem before it is a buyer problem, so open the deal and count what actually went out, how many calls, which ones connected, what text was sent, and what the last disposition says. Two unanswered calls and one email is not a follow-up attempt. That is a gap. Run a short dated sequence instead of an open-ended chase. Send a recap inside one business day that restates the buyer’s own words and names an owner and a date, give them a one-tap status reply a few days later, name the likely obstacle at about a week, and close the loop with a note that tells them the date you stop. Two federal rules shape that cadence. A follow-up email to a prospect who has not bought anything is a commercial electronic mail message under 16 CFR 316.3, because the transactional or relationship exemption in 316.3(c) requires a transaction the recipient already agreed to enter into, and sitting through a demo is not one. A prerecorded voicemail has to open with the name the business is registered under and state a working callback number that is not the number the dialer placed the call from, under 47 CFR 64.1200(b)(1) and (b)(2). Then write the outcome where a manager can inspect it, because a deal marked no response with no attempt history behind it teaches nobody anything.

The demo went well. Good questions, real nodding, maybe a request for pricing. Then nothing.

So you want to know what to do when prospects ghost after a demo. Start somewhere other than the inbox. The first move is not another message. It is reading what your own system says happened after that meeting, because the answer usually changes the message you send next.

Before You Call It Ghosting, Read the Demo Follow-Up Record

A deal sitting at no response is a conclusion, not a fact. Open it and count the inputs. How many calls went out, how many of those actually connected to a human, what text messages were sent, what the voicemail history looks like, and what the last call disposition says. A prospect who got three calls at the same hour on three consecutive mornings was not ghosting you. They were at a standup.

Then answer four questions about the demo itself.

• Was a specific next step agreed to? “We’ll follow up soon” is not a next step. A meeting date, a decision deadline, an internal review, or a named deliverable is.
• Did the prospect describe the decision process? Who approves the spend, what criteria matter, and whether procurement, security, legal, or finance gets involved later.
• Did the demo land on a business problem the prospect already recognized? Product interest is not urgency. Go back to why they took the meeting and what happens if they do nothing.
• Did a new objection surface? Price, implementation effort, switching risk, or team adoption often appears late and goes unsaid.

Those four answers pick your next message. A generic reminder cannot resolve a concern nobody said out loud. A short note about the thing the buyer told you mattered gives them a reason to type.

Why Prospects Go Quiet After a Demo

Several explanations come up often enough to be worth testing. Treat them as diagnostic prompts, not as a finding about any particular buyer.

• The priority moved. Something urgent landed on your contact’s desk and your project slid.
• The value was not clear enough. They liked the product without having a case they could defend internally.
• A stakeholder was missing. Your contact is interested and cannot move the decision alone.
• There is an unresolved concern. Price, effort, switching risk, or adoption can feel awkward to raise directly.
• The buying process is slower than you assumed. Budget review and procurement produce silence without ending anything.
• The next step had no owner. If nobody holds a dated action, momentum evaporates within a week.

Do not pick one and write to it as though you know. Ask a question that gives the prospect room to correct you.

A Post-Demo Follow-Up Cadence With a Date On It

There is no universal number of follow-ups that produces a reply. The useful discipline is that the sequence is finite, each touch does a different job, and the whole thing has an end date decided before you start. A structured outbound cadence is what makes that survive a busy week, because the next action fires on a schedule instead of on whether a rep remembers.

Four steps, each with a different job.

Send the Demo Recap Inside One Business Day

Restate the prospect’s goals in their language, list the open questions, name what you owe them and when, and repeat the next step with a date. Keep it scannable.

Subject line, recap and next step for the priority they named. Then the body. Thanks for walking through the current problem today. My takeaways were the goal, the decision criterion, and the open question. I will send the promised item by the date. We discussed the next step on its date. Is that still the plan?

That email is doing two jobs. It confirms you listened, and it creates a dated artifact you can point at later when the deal goes quiet.

Give the Prospect a One-Tap Status Reply

If the next step slips, send one short message with a low-effort choice. Do not attach five things or ask four new questions.

Ask whether the project is still active, and offer four options. Still evaluating. Interested, timing changed. Paused indefinitely. Not moving forward. Tell them a single number is a complete answer and you will follow their lead.

A buyer who will not write three paragraphs will often type one digit. That digit is worth more than another case study.

Name the Likely Obstacle About a Week After the Demo

Use what you learned before the demo. Name a possible blocker without asserting it is the blocker.

Tell them you may have missed something after the demo, then ask whether the question now is budget, timing, internal alignment, or whether the approach fits how the team works. Invite the correction if none of those is right.

This beats “did you see my email?” because it hands the buyer a short menu instead of asking them to narrate their own delay.

Close the Loop and Say When You Stop

If several purposeful attempts land on nothing, send the note that ends it. The point is not manufactured urgency. The point is an accurate pipeline.

Tell them you have not been able to confirm a next step, so you are going to assume it is not a current priority and close the loop on your side. Offer to check back in a specific month if they would rather that. Then actually stop.

Saying the date you stop is the part most reps skip, and it is the part that most often produces a reply.

Your Post-Demo Follow-Up Email Is Commercial Mail

Here is the part that catches teams out. A prospect who sat through a demo has not bought anything, and that changes what your follow-up email legally is.

Under the Federal Trade Commission’s CAN-SPAM Rule at 16 CFR 316.3(a), a message whose primary purpose is promoting a product or service is a commercial electronic mail message. The carve-out people reach for is the transactional or relationship category, and 16 CFR 316.3(c) spells out what that covers. The first item on that list is content to facilitate, complete, or confirm a commercial transaction that the recipient has previously agreed to enter into with the sender. A demo is not an agreement to enter into a transaction. Neither is a pricing request.

So the recap, the status-check nudge, the obstacle message, and the breakup note are commercial messages, and the CAN-SPAM requirements attached to commercial mail apply to all four. That is a design constraint on the cadence, not a reason to stop sending it. The practical reading is that the opt-out path has to be real and the stop request has to actually stop the sequence, including the automated parts. The specific deadlines and the life of the opt-out mechanism are covered in more detail in our breakdown of how consent differs between SMS and email campaigns.

One operational consequence is worth naming. If your sequence is automated and a prospect replies “please stop” to a rep’s personal inbox, somebody has to carry that request into the system that is doing the sending. A stop honored by one rep and ignored by the cadence is the failure mode to design against. None of this is legal advice, and these are not the only rules that may apply to a given program.

What a Post-Demo Voicemail Has to Say

Calling is still the channel with the most range for a quiet deal, because tone and follow-up questions happen live. Most of those calls reach voicemail.

If that voicemail is prerecorded rather than spoken live, including a Voicemail Drop, the Federal Communications Commission’s rule at 47 CFR 64.1200(b) sets required content. Paragraph (b)(1) requires the message to state clearly, at the beginning, the identity of the business responsible for the call, using the name the entity is registered under with its state corporation commission or comparable authority. Paragraph (b)(2) requires a clearly stated telephone number for that business during or after the message, and it specifically may not be the number of the autodialer or prerecorded message player that placed the call. It also cannot be a 900 number or any other number that costs more than ordinary transmission charges.

Read those two requirements as a script spec. Registered business name first, a working number a human answers second, the reason you are calling third. A recorded drop that opens with a first name and ends with a mobile number the prospect cannot reach misses both.

Changing channels should make replying easier, not add pressure. Do not fire the same message across email, phone, and a professional network inside an hour. Follow your organization’s communication policies, and honor a request to stop on every channel it applies to.

Bringing Other Stakeholders Into a Quiet Demo Deal

Reaching other people helps when they were already part of the evaluation or your contact invited them. It damages the relationship when it reads as going around your contact.

Ask first. Would it help to include a named role in the next conversation, or would they rather coordinate internally? That one question costs nothing and settles the matter.

If your contact stays silent, decide whether the other person has a genuine connection to the project. Keep the outreach factual, do not imply your contact endorsed it, and do not repeat anything sensitive from the demo. Say you spoke with their colleague about the general initiative, that you are checking whether it is still active, and that no action is needed if they are not involved.

Prospects Ghosting After a Demo Versus a Slow Buying Process

Not every quiet deal is being ignored. Procurement, budget cycles, a leadership change, and competing projects all stretch timelines without killing anything. Sort on evidence, not on optimism.

• Delayed but active. The buyer names a blocker, an owner, and a realistic review date.
• Nurture. The problem is still real, there is no approved timeline, and nothing happens this quarter.
• Closed or lost. The buyer declines, picks another path, or misses repeated next steps without confirming interest.

“Next quarter” is not an active opportunity. Ask what has to change, who revisits the decision, and when a check-in would actually be useful. If you cannot get those three, it is nurture.

Record the Demo Outcome Where a Manager Can Inspect It

Pipeline stage should reflect what the buyer confirmed, not how hard a rep worked. That only holds if the record is written while it is fresh.

• Record the last meaningful buyer interaction, with its date.
• Write the unresolved blocker as what the buyer said, not as your theory about them.
• Set a dated task only when there is a real reason to reconnect.
• Move long-horizon deals to nurture by your team’s definition, not by feel.
• Close opportunities when they hit your stated inactivity criteria.

The reason this matters is the diagnosis at the top of this article. You cannot tell a real follow-up failure from a lazy close-out unless the attempts are in the system, which is why it helps when the platform logs call outcomes straight into the CRM record instead of depending on a rep to type them after a hard call. Now a manager can look at ten closed-lost demos and see whether the pattern is a weak recap, no second channel, or three attempts crammed into two days.

Stop Prospects From Ghosting Before the Demo Ends

The cheapest fix happens before anyone leaves the meeting. Hold back several minutes instead of filling the whole hour with product.

• Restate the business problem in the prospect’s words and get agreement.
• Ask what could stop this from moving forward.
• Name the decision-makers, the reviewers, and the likely blockers.
• Confirm the decision criteria and the expected timeline.
• Ask whether budget is allocated or still needs approval.
• Agree the next action, the owner, and the date.
• Book the next meeting while everyone is still on the call.
• Ask what should happen if priorities shift.

One question does more work than the rest. If we do not hear from each other by this date, what should I assume? It sets a mutual exit without demanding a commitment the buyer is not ready to make, and it gives your close-the-loop email something to point back to.

Questions About Prospects Ghosting After a Demo

How many times should I follow up after a demo?

Use a finite sequence of purposeful contacts rather than an open-ended series of reminders. The right number depends on deal size, what was promised in the demo, the prospect’s stated preference, and your own policies. Stop when the buyer declines, asks for no further contact, or your closure criteria are met.

Should I offer a discount to get a prospect to respond?

Not before you know price is the actual obstacle. An unprompted discount moves the conversation off the business case and solves nothing when the real issue is timing, authority, implementation, or priority. It also teaches the buyer that waiting lowers your number.

Should I keep sending case studies after a demo?

Send one only when it answers a question the buyer actually raised. A relevant example helps someone assess risk. Unrelated attachments create work and make the follow-up feel automated, which is the opposite of what a quiet deal needs.

What is the best call to action when a prospect has gone quiet?

Ask for one decision. Confirm the next meeting, name the blocker, pick a status, or give you permission to close the loop. The less the buyer has to compose, the more likely you get something back.

When a prospect ghosts after a demo, the job is not to chase. Read the record, run a short sequence that ends on a date you chose, write down what actually happened, and let the pipeline tell the truth. The deal either comes back or it leaves cleanly, and both of those beat a stage that has not moved in six weeks.

Sources

• 16 CFR 316.3, Primary purpose, CAN-SPAM Rule, Federal Trade Commission, from the Government Publishing Office, for the rule that a message promoting a product or service is a commercial electronic mail message, and for the paragraph (c) definition limiting transactional or relationship content to a transaction the recipient has previously agreed to enter into. https://www.govinfo.gov/content/pkg/CFR-2024-title16-vol1/xml/CFR-2024-title16-vol1-sec316-3.xml Reviewed November 1, 2026.
• 47 CFR 64.1200(b), Federal Communications Commission, from the Government Publishing Office, for the requirement that an artificial or prerecorded voice message state the registered business identity at the beginning and state a business telephone number other than that of the autodialer or prerecorded message player that placed the call. https://www.govinfo.gov/content/pkg/CFR-2024-title47-vol3/xml/CFR-2024-title47-vol3-sec64-1200.xml Reviewed November 1, 2026.
• 15 USC 7704(a)(3) and (a)(4), CAN-SPAM Act, from the Government Publishing Office, for the record that a commercial electronic mail message must carry an opt-out mechanism that stays usable for at least 30 days, and that transmission must stop within 10 business days of an opt-out request. https://www.govinfo.gov/content/pkg/USCODE-2023-title15/html/USCODE-2023-title15-chap103-sec7704.htm Reviewed November 1, 2026.

Sources verified by the Kixie Research Team on November 1, 2026.