A six-act story framework for B2B demos. Not borrowed from storytelling theory. Built from direct observation of what actually makes deals close — across hundreds of demos, dozens of teams, and 25 years in the room.
The rep talks. The prospect listens. Features get demonstrated. The call ends with "I'll follow up" — which is code for "I have no idea if this landed."
And then the deal goes quiet. Not because the product is wrong. Not because the price is too high. Because the story didn't land.
The Narrative Spine fixes this by giving reps a deliberate structure for how deals actually get won — not a script to read from, but a framework for building a story that creates genuine urgency in the room.
Every great demo follows this arc. Usually without the rep even knowing it. The Narrative Spine makes it deliberate — and trainable.
The core principles
The Hook is your opening. And most reps waste it.
The typical demo opens like this: "Thanks for your time today — let me tell you a bit about us." And in that moment, you've already lost. The prospect is checking email. You're presenting to a room that's already somewhere else.
The Hook has one job: earn the next 60 minutes in the first two minutes. Not with a clever line. Not with a company overview. With something specific to this buyer's world that makes them think — how did they know that?
"I was looking at the recent consolidation happening in mid-market HR tech, and the pattern I keep seeing is that the companies who stall on headcount decisions in Q3 are the same ones scrambling in Q1. I want to show you something that changes that dynamic."
"Thanks for your time today. Before I get started, let me share a quick overview of our company and what we do..."
Write your Hook last. Build the rest of your story first — then come back and craft an opening that earns it. The best hooks reference something real about this specific buyer's situation that you learned in discovery.
Before you show anything — before you open the product, before you talk about features — the buyer needs to feel understood.
The World As It Is is where you name their reality back to them. Not the generic version. Not the version that applies to every company in their industry. The specific, painful, sometimes embarrassing version. The thing that's happening in their world right now that they haven't told their boss about yet.
When you get this right the prospect stops multitasking. They put the phone down. They say — yes, that's exactly it.
"Right now your ops team is manually reconciling data from three systems every Monday morning. It takes about four hours, it's error-prone, and the numbers your CRO sees on Tuesday are already 48 hours old."
"Many companies struggle with data visibility and operational inefficiency across their revenue teams."
If you can't describe their problem without using your product name, you don't understand their problem yet. Go back to discovery. This act lives or dies on the specificity of what you know about this buyer's actual situation.
Here's where most demos lose their urgency.
You've named the problem. The prospect agrees it's a problem. And then — nothing. No momentum. No reason to act now. The deal stalls not because they don't believe you, but because doing nothing feels safer than making a decision.
The Stakes is where you change that. This act has one job: make the cost of inaction feel real. Not vague. Not hypothetical. Specific, named, and connected to something the buyer actually cares about — time, money, competitive position, or their own credibility.
"Every month this isn't solved, your ramp time stays at six months while your Series B targets assume three. That's not a technology gap — that's a board conversation you're going to have to have in Q2."
"If you don't address this, you'll fall behind your competitors and miss your growth targets."
Make it personal. The best stakes land when the buyer can see the consequence affecting them specifically — not their company in the abstract, but them, in their role, in their next board meeting or performance review.
This is the pivot — from problem to possibility. And it's the act most reps skip entirely.
Most demos go straight from the problem to the product. Here's the pain, here's the software. But the buyer hasn't been shown the destination yet. They don't know what they're buying toward. They're evaluating features without a picture of the outcome those features are supposed to create.
The Shift paints that picture. Before you open the product, describe the world after the problem is solved. Specifically. Vividly. In terms the buyer can see themselves in.
"By the end of Q1 your Monday morning reconciliation is gone. Your ops team gets those four hours back. Your CRO sees live numbers, not 48-hour-old data. And the board conversation you were dreading becomes the one you're looking forward to."
"Imagine a world where your data is always accurate and your team is more productive."
The shift should feel achievable, not aspirational. Ground it in a specific outcome — not a better future in general, but this specific thing getting measurably better for this specific buyer. If it sounds like a tagline, rewrite it.
Now — and only now — you've earned the right to show the product.
The Proof is where you demonstrate that the Shift you just described is real, achievable, and something you can deliver. Not with a feature walkthrough. With specific evidence that a buyer like this one has already made it to the other side.
This is where the demo lives. But the demo should feel like proof of the shift — not a tour of the product. One demo moment. One customer story. Not the full feature set.
"Acme Corp — similar size to you, similar ops setup — went from a 4-hour Monday process to 20 minutes in their first 30 days. Here's the one thing in the product that made that possible..."
"Let me walk you through our platform. So here's the dashboard, and over here you can see all of our integrations, and if we click into this section you'll see the reporting..."
Before every demo, identify the single outcome your demo needs to prove. One outcome. Build everything you show around proving that one thing. If a feature doesn't support it — don't show it. Demo discipline is a skill.
The final act. And the one most commonly thrown away in the last 30 seconds of a call.
A great demo with no clear next step is a missed opportunity. All the urgency you built, all the credibility you earned, all the momentum you created — it evaporates the moment you say "I'll follow up with something this week."
The Next Step has one job: confirm a specific action before you hang up. Not vague interest. Not "let's stay in touch." A named next step with a time, a date, and if possible a calendar invite sent before the call ends.
"Let's put 30 minutes in the calendar now for the technical deep dive with your engineering lead — does Thursday work? I'll send the invite before we hang up."
"Great — I'll send something over and we can reconnect when you've had a chance to review it."
The best next step feels like the obvious thing to do next — not a commitment, not a pressure point. If you've built genuine urgency in Acts Two and Three and shown a compelling Shift in Acts Four and Five, the next step should feel natural. You're not closing. You're continuing a conversation that clearly has somewhere to go.
The Demo Atelier app guides you through all six acts for every important demo — with AI scoring, voice input, and an AI buyer who tests your story before you walk into the room.
Free to start · No credit card required · Pro from $19/month