How to turn more demos into closed won deals: a post-demo follow-up playbook

Updated 6 October 2026

A post-demo follow-up playbook is a set sequence of actions for the two weeks after a demo: a recap the same day, a champion kit on day 2, role-specific content for the wider buying group in week 1, and a shared plan from week 2 onwards. Each step has a clear recipient and a buyer signal that tells you whether the deal is moving. Most deals that stall after a good demo stall here, in the follow-up, not in the demo itself.

This guide covers what to send, who gets it and what to watch for at each stage. It doesn't cover email wording. For that, read why to stop saying “just following up” and what to say instead.

The post-demo follow-up playbook at a glance

The timings are a guide. A two-person buying group can move faster. An enterprise deal with security and procurement reviews will stretch week 2 into months. The order still holds.

Before the demo ends: agree the first step

The follow-up starts in the last ten minutes of the demo. If you leave the call with only “I’ll send something over”, every step below gets harder.

Before you hang up, agree one buyer-owned action with a name and a date. Ask who else needs to see this and what has to be true for them to move forward. We cover how to run that part of the call in how to structure a winning demo.

Same day: send the recap Pod

What to send. One link, not a chain of attachments. Put the recap in a Digital Sales Room: a branded Pod the buyer opens with no login. Include:

• the buyer’s problems, in the words they used on the call
• the recording, or a short video recap of the two or three moments that mattered
• the next step you agreed, with its owner and date
• a first draft of the Mutual Action Plan, with three to five milestones

Who gets it. The champion, plus everyone who attended. Keep it light. This is a recap, not the full evaluation pack.

Signals to watch. Did the champion open it? Did they watch the recording? Did they share the Pod with anyone who wasn’t on the call? A same-day share is one of the best early signs that your champion is already selling for you.

In trumpet, Copilot can take a call recording and draft the Mutual Action Plan with steps, owners and dates filled in, so the recap doesn’t eat your afternoon.

Day 2: arm the champion

Your champion now has to explain the deal to people who weren’t on the call. Most can’t do that well from memory. Give them material they can forward without rewriting.

What to send. Add a champion section to the same Pod:

• a one-page business case tied to the problem they described
• a short executive summary for the sponsor or economic buyer
• plain answers to the objections raised in the demo
• customer proof from a similar company, if you have it

Who gets it. The champion, so they can take it to the sponsor and the economic buyer. Don’t go around them at this stage. Ask them who needs to see it and how they want to share it.

Signals to watch. Views on the executive summary, and new viewers you haven’t met. If a senior name appears, ask the champion about their role and priorities. For more on this stage, read how to equip your champion to sell internally.

Week 1: widen the buying group

Deals rarely die in the demo. They die when finance, IT, security or procurement turn up late with questions nobody prepared for. Week 1 is when you bring them in.

What to send. Role-specific sections inside the Pod, so each person lands on what they need:

• Finance: a pricing summary and the business case
• IT and security: integration detail, the security pack and data processing documents
• End users: a short walkthrough of the workflows they’ll use every day

Who gets it. Each role, through the champion. One Pod link works for everyone, so the champion doesn’t have to forward five separate emails.

Signals to watch. Who has opened pricing, who has opened the security pack, and which buying roles are still missing. Trumpet’s AI Org Chart maps the people engaging with your Pod and flags roles that are missing, so you can see a gap before it becomes a late-stage surprise. For a full method, see how to map every stakeholder and our guide to managing stakeholders in multi-stakeholder sales.

Week 2 and beyond: run the shared plan

By week 2, the follow-up stops being a series of messages and becomes a plan both sides work through. This is where a Mutual Action Plan earns its place.

What to send.

• updates to the plan as steps are completed or dates move
• the proposal, inside the Pod, next to the business case and the plan
• security review, legal review and procurement as named steps with owners and dates
• an outline of onboarding: who from customer success is involved and what the first weeks look like

Who gets it. The whole buying group, plus procurement and legal as they join.

Signals to watch. Are buyer-owned steps being completed on time? Is the proposal being revisited, and by whom? Has anyone visited in the last ten days?

In trumpet’s own data, deals with an active Mutual Action Plan are linked to double the win rate. That is a correlation, not proof of cause, and we explain it further in our guide to Mutual Action Plan software. Inside a Pod, plans have buyer and seller steps, owners, due dates and automated reminders, so you aren’t chasing every task by hand. If you want a head start, use ready-to-use Mutual Action Plan Templates.

Which buyer signals to watch, and what to do next

Signals tell you where to look. They don’t tell you what the buyer is thinking. A buyer who keeps opening pricing might be building a budget case or comparing you with someone else. A buyer who hasn’t visited for a week might be on holiday. Use signals to decide who to talk to and what to talk about, then check with a person.

Trumpet sends real-time alerts in Slack or email when a buyer opens, views or acts in a Pod, and every viewer gets an Engagement Score. Across the whole pipeline, the Nerve Centre shows who is engaged, who has gone quiet and which deals are slipping, so managers can spot risk without inspecting every deal.

When a deal goes quiet

Silence after a demo is normal. Silence for ten days, with no Pod visits and no plan steps completed, is a signal.

1. Check the plan. Find the last buyer-owned step and when it was due. The gap is usually there.
2. Check the buying group. Has a new person joined, or has your champion stopped engaging? A quiet champion with active colleagues means something different from a quiet account.
3. Send something new. A relevant resource, a recap of their timeline or an answer to an open question. Never a bare chase.
4. Reset the plan if you need to. Agree new dates with the champion rather than letting old ones slide silently.

For the wording of that message, read our guide to better follow-up lines. For the wider problem of buyers losing interest, see how to prevent buyer disengagement.

How to tell if the playbook is working

Track a few process measures alongside your pipeline numbers:

• recap Pod sent on the day of the demo
• Mutual Action Plan shared and accepted within the first week
• number of buying roles engaged by the end of week 1
• economic buyer identified, and engaged or with a clear route to them
• demo to proposal, and demo to closed won, by rep and segment

If deals move through CRM stages but the Pod shows no buyer activity, the seller is running the process alone. That deal needs a closer look before it goes into a committed forecast.

After signature: carry on into onboarding

The follow-up doesn’t end at signature. In trumpet, the Pod carries on after the deal closes and the Mutual Action Plan becomes the onboarding plan. Customer success inherits the stakeholder history, the agreed outcomes and the plan, rather than a CRM summary and a handover call. The customer keeps working in the same space they used to buy. See how to build a better onboarding process with Digital Sales Rooms.

You can try this playbook on trumpet’s Free plan, with 10 Pods and unlimited users. See pricing for the paid plans.

Frequently asked questions

How soon should you follow up after a sales demo?

Send a recap the same day, ideally within a few hours, while the conversation is still fresh for the buyer. Include the next step you agreed on the call, so the follow-up continues the demo rather than starting a new conversation.

What should a post-demo follow-up include?

It should include a recap of the buyer’s problems, the recording, the agreed next step and a short Mutual Action Plan, all in one link. Add role-specific content for finance, IT and security during the first week.

Who should get the post-demo follow-up?

The champion and everyone who attended get the same-day recap, and the wider buying group gets role-specific content in week 1. Bring finance, IT, security and procurement in through the champion, not around them.

How many times should you follow up after a demo?

Follow up whenever you have something new and useful to send, not on a fixed count. The playbook gives you four natural points (same day, day 2, week 1 and week 2) and the shared plan carries it from there.

What should you do if a buyer goes quiet after a demo?

Check the Mutual Action Plan for the last buyer-owned step, check who in the buying group is still engaging, then send something new and useful. If the dates have slipped, agree new ones with your champion.

What buyer signals matter most after a demo?

The strongest signals are the Pod being shared with new people, pricing or security documents being opened, and plan steps being completed on time. Ten days with no visits is the clearest warning sign.