The demo went well. The prospect asked questions, liked several features and finished with “send me the details”. Then silence. Before writing another follow-up, check what you actually agreed: another meeting, a technical check, a quote or simply a document? A well-received demonstration is not yet a buying decision.
Table of contents
Summarise the whole article in one click with AI:
Summarise with AIFollow-up should return to the points discussed, resolve what is unclear and propose a precise next step. Repeating the product presentation or asking “where do things stand?” does not move the project forward on its own.
Prepare the next step before ending the demo
Post-demo follow-up begins during the conversation. Before closing, check whether the solution addresses the stated problem, what still needs assessment and who participates in the decision. This separates interest in a feature from an active project.
Rather than asking only whether they enjoyed the presentation, ask, “What is still missing for you to assess whether this fits?” or “Who else needs to review the next step?”. Someone can like a feature without having the budget, timing or authority to buy.
You can then continue a shared commitment instead of merely reminding the person you exist. This also prevents promises of trials, discounts or implementation options your business cannot actually provide.
When to send the recap and the next follow-up
Send the recap while the context is clear and within the promised timeframe. If you committed to the next day, honour it. If a technical answer takes longer, give a realistic date rather than sending an empty email to appear responsive.
The next follow-up depends on what was agreed. A committee meeting in two weeks does not justify reminders every two days. A check needed for an imminent launch belongs in that agreed schedule. Ask what rhythm will be useful.
Recap
Restate the need and deliver promised information without repeating the entire presentation.
Unblock
Address the objection or question preventing the next decision.
Agree what happens next
Confirm a meeting, a delay or a pause instead of keeping an opportunity open without a date.
No universal interval makes follow-up effective. A precise agreement matters more than a supposedly optimal cadence. Even a negative reply is more informative than several opened emails without a decision.
Write a follow-up based on the buying question
Stay in the recap thread where possible. Use a recognisable subject such as “Following our [product] demonstration”. A mysterious subject or invented urgency wastes the context already established.
Focus on the prospect’s need, not your feature list. Mention a problem discussed, add useful information and ask one simple question. One action is enough: confirm a point, choose a time or say the project is no longer a priority.
Personalisation is more than inserting a first name. Refer to a use case, constraint or objection from the demo. If you do not know what the prospect was going to check, clarify it instead of inventing a persuasive backstory.
Four post-demo email templates
Adapt these to actual commitments. Replace the bracketed fields and remove any trial, integration or discount that is not part of your offer.
1. Recapping the demonstration
The recap also checks your understanding. The prospect should be able to correct a need or an overly ambitious next step. Do not write “as agreed” for something never discussed.
2. Following up to resolve an objection
A useful reply may acknowledge that a feature is unavailable or a condition needs assessment. An accurate answer is better than a promise that lasts only until signature.
3. Returning after an agreed internal review
Use this only when an internal review was actually mentioned. Otherwise, ask how the evaluation works rather than attributing an imaginary meeting or decision to the prospect.
4. Pausing without closing the door
A pause is not a disguised ultimatum. Do not invent an account closure, disappearing price or deadline. Stop the planned follow-ups after this email.
Adapt follow-up to the prospect’s situation
An exploratory demo is different from a demonstration involving several decision-makers before a purchase. Group prospects by what they still need to check, not just expected deal size. Choose the next action accordingly.
The prospect is still exploring
Do not manufacture urgency around a broad need. Offer a resource comparing relevant uses and ask whether a specific difficulty deserves attention. Name that difficulty in the subject rather than promising general performance.
Leave room to say the time is not right. A guide can help someone think; weekly emails do not create a budget. If a later return is agreed, record it and suspend the sequence.
Several people must approve the solution
Your contact may need to explain the project to management, users or a technical team. Provide a shareable summary: problem, use case, confirmed points and open questions. Offer help instead of simply asking the same person for another meeting.
Ask who would be useful for validation. Some businesses need a defined pilot; others need a contractual check. Make the next step explicit rather than treating everyone in the organisation as a fresh outreach list.
An existing customer is assessing another use
Review current commitments before suggesting an extension. Distinguish what is already included from what needs another buying decision. A support question should not become a pretext for selling.
Existing customers have experience a new prospect lacks. Ask what works, what is difficult and why an additional use would help. A precise scope clarification is more useful than introducing the whole company again. Give a new potential customer the necessary background without assuming familiarity.
The prospect has stopped replying
Check whether promised information was sent, the right person is receiving it and any absence or delay was mentioned. An open or unopened email does not reveal a buying decision. Tracking is not confirmation.
If nothing new justifies another message, do not pad a template. Send the pause message if appropriate, then stop. Follow-up should help evaluate a proposal, not fill a daily activity target.
Give a follow-up call a question to resolve
A call can be appropriate when it suits the person and applicable rules. Prepare the demo context, specific purpose and option to choose another time. It is not an imposed second demonstration.
If the project is postponed, ask whether a return at a specific time is wanted. If the offer is declined, record why and change the follow-up. Do not switch to LinkedIn to get around the answer.
After an unanswered call, a short email can offer a written alternative. Avoid repeated calls with identical messages. The question to resolve justifies contact, not merely a task appearing in your tool.
Record what actually happened
Note the person reached, question clarified, document awaited or next call agreed. Leaving a voicemail is not the same as having a conversation. That distinction makes reporting more useful.
Handle replies, not just outgoing emails
A sequence must account for incoming replies. An automated message should not go out while a salesperson is resolving a question. Test this before activation, including where outreach and customer follow-up belong to different teams.
“The price seems high”
Ask what is being compared: scope, expected use, available budget or another proposal. Explain what the price includes without inventing return on investment. That is more useful than an automatic post-demo discount.
If customers repeatedly misunderstand the same point, fix the presentation before more outreach. Marketing can review the offer page; sales can review its examples. Follow-up emails cannot reliably repair a misunderstanding created every time upstream.
“We still need technical approval”
Identify the question, who will check it and the information required. Agree a realistic return date. Follow up on that point. Another call cannot replace a technical answer, and sales should not confirm an unchecked feature.
“It is no longer a priority”
Ask whether contact at a specific time is wanted or whether follow-up should stop. Record an agreed delay. The absence of agreement is not permission for indefinite outreach.
The goal is not any reply at all, but the right continuation: information, a call, a meeting or a pause. Each message should match that continuation, not the next available template.
Use the CRM as project memory
Keep the need, participants, objections, promised information and next action. Another salesperson should understand the record. “Demo completed, follow up” explains neither what was understood nor what prevents a decision.
Use factual statuses: document awaited, evaluation in progress, next meeting confirmed, postponed or lost with a reason. Attending a demo does not mean being ready to buy. Marketing and sales lead follow-up needs shared definitions.
Check subscription features before automating tasks in HubSpot or another CRM. Lifecycle-stage tracking still requires you to define what a transition means. Suspend automation when a reply or context change makes the next email unsuitable.
Test outreach emails with an internal address. Check signature, personalised fields, send time and whether a reply stops the next message. Agree a review date with the tool owner. This prevents a sound plan becoming inconsistent contact in practice.
Measure demos leading to an accepted next step, time between stages, blocking reasons and closed sales across comparable cohorts. Email opens and large attendee numbers are not proof of intent to buy.
Do not reward email volume
Measure replies among prospects actually followed up, separating useful replies from automatic messages. A reply rate can include refusals; an accepted-next-step rate measures something else. Neither should reduce a salesperson’s performance to email count.
Review examples with sales and marketing: clear subjects, new information and the point at which contact stops helping. Check boundaries between acquisition, project follow-up and customer support. Once someone signs, remove them from the post-demo sequence and hand over the commitments, not just the last email.
When a priced proposal has already been sent, the questions change to conditions, objections and timing. Our templates for following up on an unanswered quote address that stage.
Web Push supports the journey, not the individual negotiation
A demo is an individual conversation. Web Push brings subscribers back to your pages. A push notification can suggest a decision-making resource or use-case explanation without disclosing confidential project information.
Our standard retargeting uses viewed pages or URL elements. It does not establish demo attendance or automatically know CRM status. When you retarget an interested audience, choose a message relevant to those pages, not a supposedly personal reminder about a sales meeting.
For example, invite visitors to an offer page to read a practical explanation. Specific objections, negotiation and agreement on the next step remain the team’s job. The channel helps people return; sales helps them decide.
Frequently asked questions about post-demo follow-up
When should the first post-demo email go out?
Honour the timing promised during the conversation and send the agreed information while the context is clear. If verification takes time, give a realistic date instead of promising an immediate answer.
What belongs in a demo recap?
The understood need, points assessed, open questions, promised documents and next action. It should let the prospect correct a point or confirm the next step without reviewing the whole presentation.
How do you follow up when someone stops replying?
Return to the context and add a clarification linked to the decision. Offer a simple action. If silence continues, pause instead of repeating identical messages.
Should we offer a discount to get a reply?
Not before understanding the blockage. A discount does not solve an unclear need or a technical question. Use a commercial condition only when it is real, authorised and relevant.
Which post-demo indicators matter?
Accepted next steps, delays, blocking reasons and opportunities progressing towards a sale. Compare cases that have had time to mature rather than relying on email opens.
Can Web Push target only demo participants?
Not by assuming automatic matching between attendees, subscribers and CRM records. Our standard retargeting uses viewed pages or URL elements. Personal meeting-related communication needs a suitable, validated setup.
