Individual Template Free

Before-After-Bridge Demo Narrative Template

A fill-in-the-blanks narrative template that structures your demo as a 3-act story — Before, After, Bridge — so buyers remember the story, not just the screen you shared.

What's inside

The Before-After-Bridge structure defined and why contrast drives memory and urgency
Discovery-to-template mapping worksheet (which discovery questions feed each act)
Act 1 BEFORE fields: affected role, day-in-the-life pain, quantified cost, emotional cost, breaking-point story
Act 2 AFTER fields: future day-in-the-life, quantified outcome, feeling statement, new possibility unlocked
Act 3 BRIDGE table: capability, demo moment, proof point (3 rows)
Full word-for-word script skeleton with act transition lines
A fully worked example using a reporting/analytics SaaS scenario
Pacing guide: minutes-per-act for a 30-minute and a 45-minute demo

Why this works

Buyers don't remember features. They remember contrast. Before-After-Bridge (BAB) gives your demo a spine: you establish the cost of today (Before), paint the specific future state (After), then show the mechanism that gets them there (Bridge) — which is where your product walkthrough lives. The screen-share is evidence for the story, not the story itself.

Before creates urgency ("this is what staying the same costs you")
After creates pull ("this is what changes for you specifically")
Bridge creates belief ("here's exactly how, and proof it's real")

How to use this template

Fill in Act 1 and Act 2 using the buyer's own words and numbers from discovery — not generic pain points.
Fill in Act 3 by picking the 3 capabilities that most directly close the gap between Act 1 and Act 2. Resist the urge to list more than 3 — this is a narrative, not a feature inventory.
Write the transition lines out in full and rehearse them until they're not read off a page.
Deliver Before and After in the first 3-4 minutes, before you touch the product.

Discovery inputs you need before filling this in

A direct quote from the buyer describing their current process
A number: time, cost, error rate, headcount, or revenue tied to the current pain
Who specifically is affected (role/title, not "the team")
What the buyer said "good" looks like, in their own words
Any story of a specific bad day/incident caused by the current state

ACT 1 — BEFORE (current state)

Field	Your notes
Who is affected (role/title)
Their day-in-the-life today (2-3 sentences, specific)
Quantified cost of the status quo (hours/week, $ / error rate / cycle time)
Emotional cost (frustration, risk, credibility on the line)
The "breaking point" story — a specific incident that shows the pain concretely

Script skeleton:

"Before we get into the product, I want to make sure I've got this right from our conversation. Today, [ROLE] is [DAY-IN-THE-LIFE PAIN]. That's costing you roughly [QUANTIFIED COST] — and it showed up concretely when [BREAKING POINT STORY]. Is that a fair summary?"

(Wait for confirmation or correction before moving on — this is a checkpoint, not a monologue.)

ACT 2 — AFTER (future state)

Field	Your notes
Their day-in-the-life after (2-3 sentences, specific, mirrors the Before scene)
Quantified outcome (mirror the same unit as the Before cost)
Feeling statement — how it feels to [ROLE] when this is solved
New possibility unlocked (what becomes possible now that wasn't before)

Script skeleton:

"Here's what I want [ROLE] to be doing 90 days from now instead: [AFTER DAY-IN-THE-LIFE]. That takes you from [BEFORE NUMBER] to [AFTER NUMBER]. More importantly, it means [FEELING STATEMENT] — and it opens the door to [NEW POSSIBILITY]. What I'm going to show you next is exactly how we get from where you are today to that."

ACT 3 — BRIDGE (the mechanism — this is your demo)

Capability (max 3)	Demo moment (what you'll click/show)	Proof point (customer story, data, benchmark)
1.
2.
3.

Transition line into the Bridge:

"There are three things that make that possible. Let me show you each one, and how [SIMILAR CUSTOMER] used it to get there."

Transition line out of the Bridge (landing the story):

"So that's the full path: you start at [BEFORE], these three things get you to [AFTER], and [PROOF POINT] shows it's not theoretical — it's already happened for a team like yours."

Worked example (reporting/analytics SaaS)

Before: "Today, your RevOps analyst, Priya, spends every Friday afternoon manually pulling numbers from four spreadsheets into a deck for Monday's leadership review — about 6 hours a week, 300 hours a year. Two months ago that manual process meant a stale number made it into the board deck, and it took a follow-up week to walk it back."

After: "Ninety days from now, Priya opens one dashboard Friday morning, it's already current, and she spends that afternoon on the analysis that used to get cut for lack of time. That's 300 hours back a year, and — more importantly — no more stale numbers in front of the board."

Bridge: | Capability | Demo moment | Proof point | |---|---|---| | Live data sync across sources | Show the 4 spreadsheets replaced by one connected view, refreshing in real time | "[Customer] cut their Friday close from 6 hours to 40 minutes" | | Automated variance flagging | Show a number auto-flagged when it moves outside a threshold | "Caught a $40K billing error before it hit the board deck" | | One-click leadership export | Show the dashboard exporting to a board-ready deck | "[Customer]'s ops team stopped rebuilding the same deck by hand every month" |

Delivery pacing

Demo length	Before	After	Bridge (your demo)	Close
30 min	2 min	2 min	22 min	4 min
45 min	3 min	3 min	33 min	6 min

Don't let Before/After run long — they're the frame, not the picture. If you're past 5 minutes combined, you're re-doing discovery, not setting up a story.

How to use it

Fill in the Before, After, and Bridge fields using your actual discovery notes before every demo, rehearse the transition lines out loud, and deliver Before/After in the opening minutes so the rest of your walkthrough lands as the answer to a story instead of a feature tour.