CHAPTERS
- 4:35 – 8:03
Andy’s origin story: a brutal VC review leads to screenwriting and better pitches
Andy shares how an early startup pitch was panned by a VC, pushing him to learn storytelling from screenwriting books. He explains how restructuring the pitch—without changing the product—suddenly generated investor interest and a term sheet.
- •Started as a coder building a Windows-era app prototype
- •A VC rated the plan “1 (Worst)” and called it “not a compelling story”
- •Discovery of screenwriting books reframed pitching as storytelling
- •Rewriting the pitch’s structure increased traction without changing the product
- •Early seed of his later consulting work on narrative
- 8:03 – 8:55
What a strategic narrative is (and why it’s a CEO-level north star)
Andy defines a strategic narrative as the single story a CEO uses to align marketing, sales, product, fundraising, and recruiting. The goal is to create a shared strategic frame that scales beyond the founders’ presence in every conversation.
- •A strategic narrative is one core story used across the company
- •Functions as a strategic north star for roadmap and go-to-market
- •Designed to align teams and audiences around “why now”
- •Not just a sales deck technique—permeates all channels
- •CEO-led storytelling becomes leverage as the company grows
- 8:55 – 10:34
Why “problem–solution” pitching fails: the ‘arrogant doctor’ vs. old game → new game
Andy contrasts the standard business-school pitch (“you have pain, I have treatment”) with a story that begins with a shift in the world. Strategic narrative starts by defining an old game and a new game—creating a movement rather than a feature comparison.
- •Traditional pitch structure encourages bragging and defensiveness
- •Effective stories begin with a shift in the character’s/world’s reality
- •Andy frames this as moving from an ‘old game’ to a ‘new game’
- •The goal is movement framing, not problem framing
- •Salesforce is introduced as the archetype of this shift-led pitch
- 10:34 – 12:19
Salesforce as the archetype: how the ‘old way’ pitch would have sounded
Using Salesforce, Andy illustrates what most companies would do: position against incumbents via features and implementation speed. Instead, Benioff reframed the market: on-prem software is the old game; cloud is the new game—and incumbents are stuck in the past.
- •Old approach: ‘we’re easier/faster/better than Siebel’ comparisons
- •Benioff led with a paradigm shift: ‘software is over; welcome to the cloud’
- •Competitors were positioned as part of the old game
- •The pitch becomes ‘are you in the new game or not?’
- •Movement framing reduces feature-level head-to-head battles
- 12:19 – 15:31
More strategic narrative examples: Zuora’s subscription economy and Gong’s ‘reality’ story
Andy shares additional examples that follow the same structure: Zuora popularizing the ‘subscription economy’ and Gong shifting sales from opinions to reality. He explains how these narratives elevate the product from a tool to leadership-level transformation.
- •Zuora: transactions → subscriptions; winners already adopting the model
- •Gong: ‘goodbye opinions, hello reality’ as the rallying shift
- •Before narrative: Gong was pitched as call recording + insights vs. alternatives
- •After narrative: Gong became a sales-leadership platform, not sales ops tooling
- •A strong narrative acts as a growth multiplier beyond basic product-market fit
- 15:31 – 19:42
How one blog post changed Andy’s career—and why writing online works
Andy describes how his post dissecting Zuora’s deck went viral and unlocked global inbound demand for his work. He and Lenny discuss how writing online often looks like ‘one post boom,’ but usually comes after many iterations and steady traction building.
- •The Zuora post hit ~2M views and drove worldwide consulting inquiries
- •The post is really about the underlying story, not slide design
- •Andy’s prior journalism background shaped his approach
- •Platforms like Medium/LinkedIn removed editorial gatekeeping
- •Virality usually follows dozens of earlier posts and compounding learning
- 19:42 – 20:57
Framework step 1: name the old game vs. new game (and avoid bullet-list ‘change’ slides)
Andy explains that simply stating ‘the world is changing’ isn’t enough—the shift must be named with concise, memorable language. The compact naming sacrifices completeness, but creates clarity and repeatability for a movement narrative.
- •Common failure mode: long ‘used to be / now is’ bullet lists
- •Winning shifts are named simply (software/cloud; transactions/subscriptions)
- •Concise naming makes the shift memorable and shareable
- •Overstatement is acceptable if the frame resonates
- •The naming creates an ideological movement rather than a feature pitch
- 20:57 – 23:29
Framework step 2: name the stakes—make the future split between loss and upside
The narrative must make consequences feel urgent, like a movie. Andy shows how to raise stakes by pointing to winners already playing the new game and making the cost of staying in the old game feel existential (figuratively ‘kill the aunt and uncle’).
- •Use winners to prove the new game is already real
- •Make stakes feel ‘life and death’ rather than incremental improvement
- •Star Wars example: Luke refuses the call until stakes become existential
- •Emotion = the future is not ‘fine’; it’s polarized into bad vs. great outcomes
- •Stakes framing creates urgency and reduces budget/timing deferrals
- 23:29 – 24:57
Framework step 3: name the objective of the new game (the rallying cry)
Andy introduces the ‘object of the new game’ as a crisp mission-like statement that rallies buyers and teams. He recommends expressing it as a simple phrase (or even as a question) that feels aspirational and action-oriented.
- •Objective distills high-level shift into a concrete rallying cry
- •Examples: ‘turn customers into subscribers’; Airbnb ‘belong anywhere/live there’
- •Acts like a buyer mission statement and company mission
- •Often works well as a question to bring the buyer along
- •Aim for aspirational clarity, not highfalutin jargon
- 24:57 – 26:58
Framework steps 4–5: define obstacles, then show how you help overcome them
Once the objective is clear, the narrative introduces obstacles that make winning difficult—recasting ‘problems you solve’ as barriers to a new desired future. Only after stakes and obstacles are established should the product appear as the ‘magic gifts’ enabling success.
- •Obstacles explain why the new goal state is hard to achieve
- •Reframes standard ‘problems’ into narrative antagonists
- •Creates emotional meaning for product capabilities and use cases
- •Product becomes the enabling mechanism, not the opening argument
- •Sets up success stories and proof as resolution elements
- 26:58 – 31:41
Why this isn’t just ‘be a better storyteller’: hero’s journey parallels and the ‘one story’ focus
Andy acknowledges inspiration from the hero’s journey but avoids making it theoretical or abstract. His focus is not storytelling as a general skill, but crafting one company-defining story that turns the buyer into the protagonist facing a changed world.
- •Hero’s journey can be too theoretical to execute day-to-day
- •Andy focuses on the structure of one strategic story
- •The buyer becomes the main character navigating a changed world
- •Narrative invites: ‘you must change—will you come with us?’
- •Story structure matters more than performer-style storytelling skill
- 31:41 – 36:13
Full walkthrough example: 360Learning’s shift from ‘collaborative learning’ to ‘upskill from within’
Andy and Lenny walk through a complete application of the framework using 360Learning. The company moved from a flat category-like descriptor to a shift narrative: top-down training is the old game; internal experts becoming educators is the new game.
- •Old positioning (‘collaborative learning’) sounded like a generic category
- •New shift: top-down learning → ‘upskill from within’
- •Used winner examples (e.g., Google internal experts) to raise stakes
- •Objective framed around turning internal experts into learning champions
- •Obstacles include enabling non-experts to create courses while preserving governance
- 36:13 – 40:35
What changes after adopting strategic narrative: sales, marketing content, and product prioritization
Andy describes the practical impacts CEOs report after adopting the approach: fewer feature-level debates, clearer differentiation, and more resonant sales conversations. The narrative also becomes a filter for product decisions and a content engine for marketing.
- •Moves from pitching features to pitching a movement
- •Product becomes ‘prop’ supporting the story’s promised future
- •Marketing shifts to thought leadership about the trend, not self-promotion
- •Creates a prioritization bar for roadmap vs. random feature requests
- •Reduces ‘how are you different?’ objections by owning the framing
- 40:35 – 44:16
Movement vs. category: why naming a category isn’t the hard part
Andy clarifies he’s not anti-category creation, but warns leaders over-index on the category label. He argues that the story gives meaning to the category; without narrative, category words are empty and fail to differentiate.
- •Play Bigger frames categories as narratives, but teams fixate on names
- •A category label alone won’t create differentiation
- •Gong’s term mattered less than the ‘opinions → reality’ story behind it
- •Movement can stay constant even as category labels shift (e.g., HubSpot inbound)
- •Focus on story first; if it becomes a category later, that’s a bonus
- 44:16 – 57:40
Fit, warning signs, and getting started: when to invest, how to test, and why templates fail
Andy explains where strategic narrative works best (B2B, enterprise, complex products) and when it’s less relevant (many consumer comparisons). He shares triggers that signal the narrative is broken, suggests a lean testing approach in real sales calls, and explains why he avoids rigid templates; he also covers the painful ‘second session’ and why CEO involvement is essential.
- •Best fit: B2B enterprise tech with complex, fast-changing products
- •Common triggers: scaling beyond founder-led brute force; expansion to new product units; pivots
- •Start by drafting the structure and testing qualitatively in sales calls (‘Are you seeing this too?’)
- •Avoid copy/paste templates—principles over prescribed slide counts
- •Second session pain: presenting a ‘shitty first draft’ after discarding many ideas; CEO must lead for true cross-functional air cover
- 57:40 – 1:02:48
Lightning round + where to find Andy
In the closing section, Andy shares favorite books, a show recommendation, and one simple deck improvement: make slide titles the takeaway. He also points listeners to LinkedIn, his site, and his podcast ‘The Bigger Narrative,’ and invites feedback from anyone who tries the framework.
- •Book picks include ‘Story’ (Robert McKee) and ‘Out of Sheer Rage’ (Jeff Dyer)
- •Favorite show: Station Eleven
- •Favorite product: Fitbit (considering Apple Watch)
- •Deck tip: slide titles should be takeaways, not labels
- •Contact: LinkedIn, andyraskin.com, and ‘The Bigger Narrative’ podcast
