# Tell-Show-Tell Demo Framework Guide

> A teaching guide to the classic 3-beat sequencing method: Tell, Show, Tell: applied per feature, so every moment in your demo lands as a business outcome instead of a click-through.

Free framework for sales reps. Topic: [Demos & Product Storytelling](https://www.peerlab.ai/library/topic/demos-product-storytelling/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/tell-show-tell-demo-framework-guide/

## How to use it

Before each feature you demo, write and rehearse the Tell #1 and Tell #2 lines using the buyer's own words, and treat every feature block as its own complete Tell-Show-Tell loop rather than one long walkthrough.

## What's inside

- Definition of the 3 beats: Tell #1 (set-up), Show (walkthrough), Tell #2 (landing)
- Why it works: primacy/recency and cognitive load during live software demos
- The micro-loop rule: apply the pattern to every feature block, not once for the whole demo
- Sample word-for-word script line for each beat
- Do's and don'ts table (6 pairs)
- A full 3-feature sample script
- Notes on nesting Tell-Show-Tell inside a Before-After-Bridge macro-narrative
- Practice worksheet: convert a buyer's discovery quote into a Tell #1 and Tell #2 line

## What it is
Tell-Show-Tell is a 3-beat sequence borrowed from classic instructional design and applied to software demos:

1. **Tell #1 (Set-up):** state the business outcome *before* you touch the product
2. **Show:** do the walkthrough, narrated in the buyer's language
3. **Tell #2 (Landing):** restate the outcome using the buyer's own metrics, then bridge to the next thing

The rule that makes this different from an ordinary demo: **you never just "show."** Every feature block is wrapped in a Tell before and a Tell after.

## Why it works
- **Primacy/recency:** people remember the first and last thing they hear about a topic far better than the middle. If your only "telling" is the show itself, the buyer's takeaway is whatever visual stuck, not the outcome you wanted them to remember.
- **Cognitive load:** live software demos are visually busy. Buyers are parsing UI, not listening for the point. Tell #1 gives them the point *before* the load starts; Tell #2 repeats it once the load is over.
- **Meeting recall:** most demos have 2+ attendees, and the person who has to report back to a boss who wasn't on the call needs a clean, quotable sentence, Tell #2 is that sentence.

## The 3 beats, in detail

### Tell #1: Set-up
State the outcome in one sentence, in the buyer's own vocabulary, *before* you click anything. Do not describe the feature yet.
> "Here's how you stop losing deals to slow follow-up."

### Show: Walkthrough
Narrate what you're doing and why, tying every click back to the outcome you just named. Keep this to under 90 seconds per feature block: if it's running longer, you're demoing the feature, not the outcome.
> "So when the call ends, this fires automatically: no rep has to remember to log it, draft the note, or set the follow-up."

### Tell #2: Landing
Restate the outcome, now with a number or the buyer's own words, and bridge forward.
> "That's the 48-hour follow-up gap you told me about, closed to zero. Next, let's look at what happens when a deal goes quiet for a week."

## The micro-loop rule
Apply Tell-Show-Tell to **every feature block**, not once across the whole meeting. A 30-minute demo showing 5 capabilities should have 5 complete Tell-Show-Tell loops, each 3-5 minutes, not one long Show sandwiched between an opening Tell and a closing Tell.

## Do's and don'ts

| Do | Don't |
|---|---|
| State the outcome before clicking anything | Open a screen and start narrating what it does |
| Use the buyer's numbers/words in Tell #2 | Use the same generic Tell #2 line for every feature |
| Keep each Show under 90 seconds | Let a Show run 5+ minutes uninterrupted |
| Bridge Tell #2 into the next feature | End a feature block with silence or "okay, next..." |
| Wrap every feature, even small ones | Skip Tell-Show-Tell for "minor" features and only use it for the big one |
| Match Tell #2 language to what the buyer will repeat to their boss | Use internal product jargon in Tell #2 |

## Sample 3-feature script

**Feature 1: Auto-logging**
- Tell #1: "First, how you get every call logged without a rep lifting a finger."
- Show: *(demonstrate auto-capture and CRM sync, ~60 sec)*
- Tell #2: "So the manual logging that was eating an hour a day per rep, gone. That's back to selling time."

**Feature 2: Deal-risk flagging**
- Tell #1: "Second, how you catch a deal going quiet before it's too late to save."
- Show: *(demonstrate the risk flag triggering on no-activity, ~75 sec)*
- Tell #2: "That's the exact scenario you described with the Northwind account last quarter, this would have flagged it three weeks earlier."

**Feature 3: Manager rollup**
- Tell #1: "Third, how your manager sees pipeline health without asking for a status update."
- Show: *(demonstrate the manager dashboard, ~60 sec)*
- Tell #2: "No more Friday status-update Slack messages, it's already visible."

## Nesting inside Before-After-Bridge
Tell-Show-Tell is the *micro* pattern for each feature; Before-After-Bridge (see the companion template) is the *macro* pattern for the whole meeting. Use BAB to frame the meeting's opening and close, and use Tell-Show-Tell inside the Bridge act for each individual feature you demonstrate. They're not competing frameworks, one nests inside the other.

## Practice worksheet
Take 3 direct quotes from your last discovery call and convert each into a Tell #1 / Tell #2 pair.

| Buyer's discovery quote | Tell #1 (before the Show) | Tell #2 (after the Show) |
|---|---|---|
| | | |
| | | |
| | | |