You've had this meeting. It goes well. Everyone nods. Then it dies quietly in a Slack channel you'll never see, because the person who liked you had to re-explain your company to four colleagues and couldn't quite do it.
That's not a pitch problem. That's a story problem.
Gartner found buying groups for complex B2B purchases now run to six or ten people. You will meet maybe two of them. The other eight get your company secondhand, filtered through a champion who is busy and doing their best.
The question this chapter answers: what does your champion say when you're not in the room?
The five-beat narrative
This is Andy Raskin's structure, from his breakdown of Zuora's sales deck. It's the clearest version of this thinking anyone has published and it holds up.
- Name the shift. Something undeniable that's changing in the world. Not your product. A change your buyer already feels but hasn't named.
- Show there'll be winners and losers. The shift creates urgency only if adapting is not optional.
- Paint the Promised Land. What life looks like on the other side. Raskin is strict here: the Promised Land is not your product, it's what becomes possible because of it.
- Position your capabilities as the way in. Now, and only now, your features. Each framed as a way past an obstacle.
- Prove you can deliver. Evidence that people have made this journey with you.
The order matters more than the content. Most decks start at beat four and wonder why nobody's paying attention.
Opening slide: "We're an AI-powered platform for finance teams. Founded 2023. Backed by [VCs]."
Starts with you. The listener has no reason to care yet.
And on the Promised Land: "You'll have the most advanced close-management platform available." That's your product with an adjective attached.
Opening slide: "Finance teams are being asked to close faster every year with the same headcount. Most are still doing it by hand."
Starts with their world. Now the product has somewhere to land.
And on the Promised Land: "Your team closes in three days and nobody works a weekend to do it." That's a life. A champion can repeat it.
One story, three uses
Here's what most companies have: a homepage, a sales deck, and a pitch deck, each written separately, each saying something slightly different.
Here's what they should have: one story, told three ways.
The customer version emphasises the problem. The investor version emphasises the size of the shift. The team version emphasises why it matters. Same spine. Different weighting.
Building it separately is how you end up as a company that sounds like three companies.
Do this over two sessions
Session one, find the shift. Look at your customer interviews. What has changed in their world in the last three years that made your product necessary? If you can't name it, you probably don't have a story, you have a feature list. Write the shift as one sentence, in language a customer would use.
Then test it. Koto's Carolyn Rush has a good bar for this: a great idea reveals a hidden truth that's core to the category, felt by customers, but somehow left unsaid. If your shift is something every competitor also says, keep digging.
Session two, write the other four beats. One slide's worth of thinking each. Keep the Promised Land free of product language. If your own product name appears before beat four, move it.
Then read it aloud to someone outside the company. Ask them to repeat it back a day later. What survives is your story. What doesn't was decoration.
Finally, map it three ways. Mark which beats get more weight for customers, for investors, for new hires. Don't rewrite. Just reweight.
Teardown
Zuora
Zuora didn't open by describing billing software.
They named a shift and gave it a name: the subscription economy. Buyers were moving from owning things to subscribing to them, and that changed what companies needed underneath. Then they showed the winners and losers of that shift. Then a Promised Land defined by what winning looks like, not by their platform.
By the time the product appeared, the audience had already agreed with three things. The product was just the obvious consequence.
Worth noticing what this cost them: the first third of the deck says nothing about their software. Most founders can't bear that. It's exactly why it worked.
What you leave with
What you now have. One five-beat narrative that your homepage, your sales deck, and your pitch deck all draw from.
The test. Tell it to someone outside your company. Wait a week. Ask them what your company does. If the shift comes back, the story holds. If they describe a feature, go back to beat one.
Where this usually goes wrong. Founders write a shift so broad it's a press release ("AI is changing everything"). Specific beats grand. "Compliance teams now get audited on things that didn't exist two years ago" beats anything with the word transformation in it.
What it takes. Two sessions of about two hours, a week apart. The gap matters more than the hours.
