- An investor spends roughly two minutes on a cold deck. Around 20% of startups get a first call; 1–2% get funded. The deck's only job is to earn the meeting.
- For a raise, you want one deck: the investor deck. Ten to fifteen slides, twelve in practice, ideally under 40 words each.
- The spine runs in four acts — the hook, can-it-make-money, why-you, and the close — and each slide has one job. Break the order and you lose the reader.
- The deck is a door opener, not the pitch. The investment happens in the room that follows: the Q&A, the follow-ups, the diligence.
An investor gives your deck about two minutes before deciding whether you are worth a call. Two minutes, against months of your life. That is the arithmetic every founder raising a round is up against — and most decks lose on it. Not because the company is weak, but because the deck makes the investor work too hard to see why it isn't.
This issue distils the playbook of Matas Ramanauskas, who is joining the Product Pieces bench as our fundraising partner. Matas spent his career on the other side of the table: a background in venture capital where he ran 32 early-stage deals worth around €30m, plus Big Four valuations, financial due diligence and M&A. He now helps founders get a "yes" from people like the old him. His full Pitch Deck 101 guide — every slide, real good-versus-bad examples, and an investor-deck template you can copy — is available here. What follows is the spine of the method, and the way we use it when a founder we work with is heading into a round.
First, pick the right deck.
There are more than ten kinds of pitch deck, and founders lose time building the wrong one. The elevator deck is five to seven slides for pitching live in a couple of minutes. The due-diligence deck goes deep once an investor is already interested. The technical deck is for technical VCs. The master deck is your internal bible you cut everything else from. For a raise you need exactly one of them: the investor deck. Ten to fifteen slides, made to do two jobs — make an investor curious enough to book the first call, then carry that first meeting, which is roughly 20% you presenting and 80% questions.
The twelve-slide spine.
Every VC has their own idea of a perfect deck, so there is no universal template. But there is an order investors expect, and a strong reason to follow it: each slide sets up the next. Cover states what you do. Problem earns the solution. Market and model prove it can be a business. The team proves you can pull it off. You can move a slide if it tells your story better — strong traction, for instance, earns a spot right after the solution — but deviate as little as you can.
Cover, problem, solution — the first ninety seconds.
The cover is the slide shown longest and, often, the only one seen. So it has to say exactly what you do in under ten words: who you help, what you do, how it helps. The trap is the vague, buzzword one-liner — "building the future platform of financial empowerment" — that means nothing to anyone but the founder. Say "automated month-end reconciliation for enterprise finance teams" instead. Clear target, clear topic, clear proposition.
The problem slide is one of your strongest levers, often more than the solution. Make it a single statement of who has the problem, how big it is, and why today's options fail. Investors back big, painful problems, because painful problems carry big revenue. Build a painkiller, not a vitamin. And the solution must mirror the problem exactly — the two are a pair of shoes. If the problem is "slow, costly and manual," the solution is "fast, cheap and automated," and nothing else. The fastest way to lose the room early is a solution that answers a different problem than the one you just set up.
Market, product, model — can this make money.
Market size is where founders make the most mistakes. Never "the market is £300bn, we take 1%." Build it bottom-up: count how many of your ideal customers exist, multiply by your yearly price, and name the beachhead you go after first. A TAM in the billions is credible; one in the trillions means you have counted a market that isn't yours. Show TAM, SAM and SOM with a one-line explanation of each.
The product slide answers three questions fast: what is it (the category — app, API, hardware), how does a user actually flow through it, and what value they get. Show the stage of development so investors know what is built and what is still imagination. If your solution slide already covers it, this one is optional. The business model slide does one thing: show how you make money. Name the model, give one price point per tier, and let the investor run the napkin maths in their head. Do not bury it under a ten-row feature matrix.
Go-to-market, competition, team — the why-you.
Go-to-market is the other slide founders routinely get wrong, usually by being generic. Name a specific ideal customer — "we target hospitals" tells an investor nothing; which hospitals, what size, where — and the acquisition channels that already work for you. The point is to prove you know something your competitors don't. On competition, never claim you have none; it just says you haven't done the research. Use a clean quadrant or a benefits matrix kept to five competitors and five features that actually matter to your customer, and state the one angle where you win.
The team slide is the one early-stage investors care about most, because before product-market fit the company will pivot many times and they are betting on who can survive that. Portraits and names alone are not enough. For each founder: photo, name, role, relevant experience, real achievements, and any strong company or university logos. One clear CEO, not two. The slide has to answer why you are the team that pulls this off.
Traction, ask, outro — the close.
Traction is about momentum, not numbers. "£5,000 MRR" says little on its own — reached in three months or three years? Always show direction: month-on-month or year-on-year growth. Cut the vanity metrics; downloads, visits and sign-ups don't count. Show what happens after: paid users, active users, retention, conversion, and the metrics specific to your model. If your traction is strong, move this slide up.
The ask and use of funds slide leaves no room for ambiguity: how much you are raising, what milestone it reaches, and in what timeframe. "Raising £2m to enter the UK and reach £150k MRR in 18 months." Add a simple pie chart of three to five spend categories. Do not put your valuation or the round name in the deck. The outro is your business card: logo, contact, and a short vision statement. Clean, confident, nothing more than what is needed.
The mistakes that lose the room.
Most decks don't die on the idea; they die on avoidable self-inflicted wounds. Keep these in view as you build:
- No hook. Investors spend around two minutes on the deck. Put your strongest proof — team, traction, IP — up front, before they lose interest.
- Vanity over momentum. A number with no growth rate and no timeframe tells an investor nothing. Show the direction.
- Not knowing your numbers. The meeting is 80% questions. Know your metrics, forecasts and unit economics by heart, and expect the sharp ones: why are you 10x better, why now, why this team, what breaks it, what runway.
- Hiding things. Be honest about traction, team gaps and risks. Diligence finds everything; the founder who said it first keeps the trust.
- Sending it wrong. Export as a PDF, share it as a link — not an attachment bolted to a cold email.
How we use this at Product Pieces.
A great deck isn't about design or animation. It is a clear storyline an investor can follow in two minutes and come away understanding what you do, why it matters, how big it can get, and why you are the team to do it. That is the same discipline we bring to a product function — and when a founder we work with is heading into a round, fundraising is where a strong product story meets a very different audience. That is the piece Matas plugs in. His full Pitch Deck 101 guide is the whole thing: every slide broken down, real good-versus-bad examples, the VC questions to expect, and a template to build from.