Your Pitch Deck Structure Is Killing Your Story
I tanked my first investor meetings. Completely.
I'd moved to Canada 15 months earlier with no professional network. Through sheer persistence, we scored a few meetings with angels and VCs. I walked in thinking the hard part was behind me. I walked out with nothing. That's when I learned: getting the meetings isn't the hard part. Telling a story that makes people believe you is.
I spent the next three months inside FounderFuel, a startup accelerator built entirely around storytelling. Every week I pitched to VCs and successful entrepreneurs. By the end of it, I stood in front of 1,200 people and presented BenchSci's story. I was no longer tanking.
Storytelling is the most important skill a CEO can master. Not just for investors — it's how you hire, sell, manage crises, and build your partner ecosystem. I've watched companies raise enormous rounds before hitting any of the usual milestones, and I've watched great companies struggle to raise at all. The difference almost always comes down to one thing: whether the CEO can tell a compelling story.
Here's what I've learned about how to do it.
Kill these two myths first
Most pitch deck advice is wrong. Two myths in particular need to go before you build a single slide.
Myth one: Use the standard structure. Problem. Solution. Market Size. Team. You've seen this a hundred times. We raised over $40M at BenchSci and never used that structure for any of our decks. Here's why: that's not how stories work. Imagine watching a film where every scene is labeled — "Background," "Plot Twist," "Crisis." It would kill the experience. A pitch deck should take the audience on a journey. You still cover the problem, the solution, the team — but you do it without announcing each one like a PowerPoint template. Structure kills interest.
Myth two: Keep it to 10 slides. Our Series A and Series B decks were 35 slides each. A deck can be 40 slides. What matters is the content, not the count. I'd rather have 35 clean, focused slides than 10 overloaded ones where every slide is trying to do five things at once. Stop counting slides. Start building a story.
The only framework you need
At FounderFuel, we learned a simple framework that I've used ever since. Every pitch deck needs to answer three questions — in this order:
- Why should I care?
- Why should I believe?
- Why should I join?
Get those three questions right and you will get term sheets. Miss any one of them and you'll wonder why the meeting went sideways.
Why should I care?
Most founders open their deck by describing their product. That's a mistake.
What your company does needs to be bigger than the specific problem your product solves today. You need to start with the world — the real value you're bringing to it — before you ever show a screenshot or explain a feature.
Look at how the best companies in the world describe themselves. Square sells a credit card reader. But their leadership says they "enable everyone to participate and thrive in the economy." LinkedIn makes most of its money from recruiters. But what they say they're doing is "connecting the world's professionals to make them more productive and successful."
When you're trying to attract investment or talent, which excites you more: working on a credit card reader, or enabling everyone to thrive in the economy?
Nobody gets fired up about another marketplace, another AI to optimize X, another Uber of Y. Which meaningful problem you're solving — at the level that actually matters — is what makes people lean forward. Your first two to three slides need to do that work. If the audience doesn't care by slide three, the rest of the deck doesn't matter.
Why should I believe?
Once you've made people care, you have to convince them you can actually pull it off. This is the meat of the deck — and where most founders either win or lose the room.
Solution. Not what your product does. Which problem it solves. What are you fixing in the world?
Why now. Why is this the right moment? Why hasn't it been solved before? There's almost always a specific reason — a technology shift, a regulatory change, a new behavior. Name it explicitly.
Technology and product. Show screenshots. Convey the value to the user and how they actually use it. If you have a technical product, go deep — two or three slides explaining why your technology is defensible is not too many. Don't be scared of complexity here.
Go-to-market strategy. How are you going to win? What's the first market you'll monopolize, and how do you expand from there? If you haven't read Zero to One by Peter Thiel, read it before you build this slide.
Validation, traction, momentum. This is where many first-time founders fail. To make people believe your story, you need to show them the market already believes it. In the early days at BenchSci, we had a problem: we needed to raise money to build our AI technology, but we were months away from a prototype. So we got creative. We created designs of our future platform, printed them out, rented a car, and drove all over Ontario to meet scientists from 500 different labs. We asked each of them: would this platform solve the problem you're facing with failed experiments? They all said yes. We asked them to sign up for our soft launch and wrote their names down on a piece of paper. Our deck had a slide that said: "Over 500 labs have signed up to use BenchSci." There is always a way to show validation. Get creative.
Competitors. Address them — don't ignore them. I prefer to weave competitors into the story rather than use the standard matrix, but either way, you need a clear answer to why you win.
Team. Comes at the end of this section. Not the beginning. Save it for after you've made people care and believe — by then, they actually want to know who's behind this.
Why should I join?
This section is the most straightforward, and the one founders most often fumble by over-complicating it.
Investors join for financial return. Your job here is to show a massive opportunity and make the math believable.
Financials. If you're raising from VCs, you need to show how your company gets to a billion-dollar valuation. In SaaS, that means $100M in ARR. One critical fact: for best-in-class SaaS companies, it takes on average five to seven years after hitting the first million in revenue to reach $100M ARR. The moment your model shows it happening in three years, investors stop believing everything else you've said. Don't do it.
The ask. Show how much you're raising and what milestones you'll hit with that capital. Don't focus on how you'll spend the money — focus on what you'll accomplish. And skip the slide on target valuation or exit strategy. On valuation: run a good process and let the market decide. On exit strategy: if you're raising from VCs, there's only one answer — go public.
Putting it together
Three questions. Ten to forty slides. One story.
Why should I care? → Problem
Why should I believe? → Solution, Why now, Technology and product, Go-to-market, Validation, Competitors, Team
Why should I join? → Financials, Ask
Just don't label your slides with those headings. The moment you title a slide "Why Should I Care?", you've turned a story into a template. And templates don't raise money. Stories do.
Member discussion