Demo storytelling: Andy Raskin's strategic narrative for product demos
Why most product demos fail and how to structure one that lands
Most product demos fail in the first 90 seconds — the rep opens with 'so let me show you our platform' and the prospect's executive sponsor is already mentally reviewing whether to stay on the call. The demos that land follow Andy Raskin's strategic-narrative framework, adapted from screenwriting and political-speech structure: name a shift in the world, name the stakes of that shift, name the protagonist (the customer), name the obstacle, then show the product as the resolution. This page covers the framework, applies it to a B2B SaaS demo, names the structural mistakes that turn demos into feature tours, and shows how to compress the framework into a 5-minute opener for low-attention demo blocks.
Andy Raskin's strategic-narrative framework, briefly
Five elements, applied in order. (1) Name a shift in the world — what's changed externally that makes the status quo no longer work. (2) Name the stakes — what happens to organizations that don't adapt to the shift. (3) Name the promised land — what the new world looks like for organizations that do adapt. (4) Name the obstacles — what's hard about getting there. (5) Show the product as the resolution — how your product specifically solves the obstacles. The framework's power: it positions your product as inevitable rather than optional. The customer's executive sponsor has already agreed (in the first 60 seconds) that the world has shifted and the status quo is dying; everything that follows is about which path forward to take, not whether one is needed.
Applying the framework to a B2B SaaS demo
Worked example for a sales-coaching product: (1) Shift — 'AI is changing what good sales coaching looks like; the manager-listens-to-call-recordings model worked at 10-rep teams but breaks at 50-rep scale.' (2) Stakes — 'sales orgs that don't adapt will see top performers leave for competitors with better real-time coaching, and their B-players will plateau because nobody has the bandwidth to coach them weekly.' (3) Promised land — 'the orgs that figure this out have B-players hitting top-quartile performance because the AI catches coaching moments at scale.' (4) Obstacles — 'most AI sales tools are post-call analytics; they tell you what should have been said AFTER the deal slipped.' (5) Resolution — 'HearQA is the in-call coaching layer; it surfaces the framework recall while the customer is mid-sentence.' That entire opener takes 90 seconds and earns the rest of the demo time.
The structural mistakes that turn demos into feature tours
Three patterns kill demos. (1) Opening with the product instead of the world — 'let me show you our platform' has zero stakes; the prospect's attention drains immediately. (2) Feature-by-feature walkthrough without anchoring back to the obstacle — every feature shown should solve a named problem the customer has already agreed exists. (3) No protagonist — 'this is what we do' rather than 'here's what your team's day looks like with this.' The customer should be the hero of the story; your product is the wise-mentor archetype that hands them the tool. Rewatch any 10 sales demos at random and you'll see all three patterns; the demos that close at higher rates have the strategic-narrative structure even when the rep doesn't know they're using it.
The 5-minute compressed version for short-attention demos
Some demo blocks are 5 minutes inside a larger 30-minute call (executive briefings, conference booth conversations, last-minute add-ons to longer agendas). The compressed structure: (1) 30 seconds — shift in one sentence. (2) 30 seconds — stakes in one sentence. (3) 60 seconds — the customer's day-in-the-life with vs without your product (the protagonist's story). (4) 2 minutes — show ONE feature that solves the central obstacle, not a tour of three. (5) 60 seconds — close with the specific next step (next demo, pricing conversation, technical deep-dive — match to the prospect's stage). The compression forces decisions — you can only show one feature, so you pick the highest-stakes one. Most reps doing 5-minute demos try to compress a 30-minute tour; the right move is to skip the tour entirely and lead with the strategic narrative compressed.
How to research the strategic narrative for each prospect
The strategic narrative isn't a template you fill in once and reuse; it's a research output per prospect. For each demo, before the call: (1) Identify the prospect's industry-specific shift — what's changing in their world that the executive sponsor is already worried about. Earnings transcripts, industry reports, the CEO's recent LinkedIn posts surface this. (2) Identify the prospect's specific stakes — what's the cost to them if they don't adapt. Their public roadmap, recent layoffs, recent reorgs surface this. (3) Identify the prospect's specific protagonist — who's the team that benefits from your product. Org-chart research from LinkedIn surfaces this. The 30-60 minutes of research before each demo is the difference between a strategic narrative that lands and a generic one that doesn't.
Checklist
- ☐Open with the world's shift, not your product — the executive sponsor's attention is anchored to whether the world is changing, not whether you have a product
- ☐Name the stakes before showing the product — without stakes, the product feels optional rather than inevitable
- ☐Make the customer the protagonist — every feature you show should anchor back to 'your team's day looks like this' rather than 'our platform does this'
- ☐Cut the feature tour — show ONE feature that solves the central obstacle, not three that solve adjacent ones
- ☐Research the prospect's specific shift, stakes, and protagonist before each demo — the strategic narrative is per-prospect, not template-based
- ☐Compress to 5 minutes when needed by skipping the tour entirely, not by speeding through it — better to do the strategic narrative well in 5 min than the feature tour poorly in 5 min
- ☐Practice the compressed and full versions before high-stakes demos (board-level briefings, conference booths, executive escalations)
How HearQA Helps
- Upload Andy Raskin's strategic-narrative framework writeup, your prospect's company brief, their executive's recent earnings transcripts and LinkedIn posts, your competitive teardown, your product's specific feature-to-obstacle mapping into the document library — HearQA grounds every demo prompt in the prospect-specific narrative you researched
- Practice → Mock Interview lets you rehearse the strategic-narrative opener with the AI playing the prospect's executive sponsor pushing back on the shift premise — by the third session, the opener feels natural rather than scripted
- Live AI surfaces the strategic-narrative beats during the demo — when you start to drift into a feature tour, HearQA prompts the next narrative beat (stakes, protagonist, obstacle, resolution) instead of the next feature
- Per-call session summary auto-captures which narrative beats landed (where the executive sponsor leaned in) and which didn't (where they checked out) — useful for cross-demo pattern recognition on what works for YOUR prospect base
FAQ
Doesn't this only work for category-creating products?
It works better for category-creating products (because the shift in the world IS the product's existence), but it works for any product where the prospect's status quo is suboptimal. For mature-category products (CRM, accounting, marketing automation) the shift might be 'AI integration' or 'remote-first work patterns' rather than the product's existence — but the strategic-narrative structure (shift → stakes → protagonist → obstacle → resolution) still produces a more attention-holding demo than a feature tour. Andy Raskin's original case studies include Salesforce, Yammer, and other mature-category products applying the framework.
What if the prospect's executive sponsor doesn't believe the shift premise?
Then you've identified a deal-killer in the first 90 seconds — which is valuable. Either restructure the demo around a shift the sponsor does believe in (often easier said than done; the work is in the pre-demo research), or recognize the prospect isn't ICP-aligned and route to a more qualified opportunity. The strategic narrative works as a qualification tool: prospects who can't agree with your shift premise either need different pre-demo nurture or aren't a near-term opportunity.
How long should each section of the framework be in a 30-minute demo?
Approximate ratios: shift + stakes 5 min, promised land + protagonist's day 5 min, obstacles 5 min, product-as-resolution 12 min, next-step close 3 min. The product-as-resolution gets the most time because that's where you actually demonstrate (rather than narrate). The 13 minutes of narrative before the product earns the 12 minutes of product the customer is willing to attend to. Most reps invert this — 25 minutes of product, 5 minutes of narrative — and the demo lands worse despite spending more time on the 'real' content.
Where can I find good examples of strategic-narrative demos in action?
Andy Raskin's own writing on Medium / Substack has 20+ case studies with named companies (Salesforce, Yammer, Stripe Atlas's launch narrative). Andreessen Horowitz published a longer-form piece with B2B SaaS examples. Watch Marc Benioff's keynotes for the canonical 'shift in the world' opening style; watch Stripe's Sessions product talks for the framework applied at smaller-scale demos. Combining all three calibrates you across deal sizes and industry contexts.
How do I avoid sounding pretentious with the strategic-narrative framing?
Two ways. (1) Speak in your own voice — Raskin's framework is structural, not stylistic. The shift can be named in the prospect's industry vocabulary ('account-based marketing won; spray-and-pray didn't') rather than abstract storytelling language. (2) Earn the framing with research — generic 'the world is changing' lands as pretentious; specific 'last quarter your CEO told earnings analysts that pipeline coverage was a top-three concern' lands as informed. The pretentious-vs-informed boundary is whether you've done the prospect-specific research work; without it, any narrative framing reads as boilerplate.