The sales deck leave-behind and follow-up email

The meeting went well and the buyer says, “Can you send us the deck?” It’s a good sign, but it’s also a trap. The deck that worked in the room relied on you to explain it. Sent on its own, it will be read by people who weren’t there, often days later, with no one to fill the gaps. What you send needs to work without you.

That means two things: a leave-behind version of the deck, and a follow-up email that tells the reader what to do with it.

Why the presented deck doesn’t travel

A good presented deck is sparse on purpose. Short headlines, one image or number per slide, very little text. You supply the story out loud. When someone opens that file later, they see a headline like “Same-day orders” and a chart with no explanation. They have to guess what it means and why it matters.

The people who read the sent version are also different. They are often the approvers: a finance head, a managing director, a procurement team. They missed the conversation and they have their own questions. The leave-behind is your only chance to answer them.

Building the leave-behind version

Start from a copy of the presented deck, not a blank file. Keep the same order and story, then make these changes.

Rewrite every headline as a full sentence

“Current process” becomes “Orders are re-keyed twice, which takes about 40 hours a month”. A reader who only skims the headlines should still get the whole argument. Label estimates as estimates.

Add a short line of explanation where needed

One or two sentences under a chart or screenshot, saying what to notice. Not paragraphs. If a slide needs more than that, it probably needs to be two slides.

Open with a summary slide

Put a one-slide summary after the title: the buyer’s problem, what you propose, the expected result and the next step. Some readers will only look at this slide, so make it complete.

Remove anything that only made sense live

Jokes, rhetorical questions, “let me show you” slides and live demo placeholders. Replace a demo with two or three annotated screenshots of the steps you showed.

Reflect what was said in the meeting

If the buyer raised a concern, add a slide that answers it. If they corrected one of your assumptions, fix it. The sent deck should show the meeting happened.

Keep the detail in the appendix

Security information, implementation timelines and detailed pricing can follow the closing slide, clearly titled so a reader can find the part they need.

The leave-behind usually ends up a few slides longer than the presented version. That’s expected. There’s more on sizing each version in how long a sales deck should be.

Writing the follow-up email

The email does a job the deck can’t: it tells the reader why they are receiving it and what you’d like them to do. Keep it short enough to read on a phone.

A structure that works:

1. A one-line thank you that names the meeting. “Thanks for your time on Tuesday with Priya and the operations team.”
2. Two or three things you heard. The problems the buyer described, in their words. This is the part approvers read most closely.
3. What’s attached and how to use it. “The attached deck covers the proposal in full. Slide 2 is a one-page summary if you only have a minute.”
4. The agreed next step, with a date. “As agreed, we’ll set up a technical review with your IT lead next week. Does Thursday at 3 pm work?”
5. One open question, if there is one. Something you still need to know, such as who else should be involved.

Send it the same day if you can. Momentum fades quickly, and a follow-up that arrives a week later has to rebuild interest the meeting created.

Send a file people can open

Practical details matter more than they seem. Send a PDF unless the buyer asked for an editable file, so the layout looks the way you intended on any device. Name it clearly, for example “Acme Distribution: order processing proposal, October 2026”, rather than “Deck_v7_final”. If the file is large, share a link instead of an attachment so it doesn’t bounce.

If you are also sending a formal proposal, keep the two separate and make the email clear about which is which. The difference between the two is covered in sales proposal vs sales deck.

Keep both versions in step

Once you have a presented version and a leave-behind version, they can drift. A price changes in one but not the other, or a new slide is added to the presented deck and forgotten in the sent one. Keep one master file and produce both versions from it for each deal, and check the numbers match before anything goes out. If several people produce these versions, agree one shared master so every copy stays consistent.

A leave-behind that explains itself, sent with a clear email, keeps the deal moving in the rooms you’re not in. Often those are the rooms where the decision gets made.