How to Create a Startup Pitch Deck: A Slide-by-Slide Guide

A startup pitch deck is a short investor narrative designed to earn the next meeting. It is not a business plan compressed into slides, and it is not a substitute for diligence. Its job is to make five things clear enough that an investor wants to keep going:

1. What the company does.
2. Why the problem matters now.
3. What evidence says the solution can work.
4. Why this team can build a large company.
5. What the requested capital will accomplish.

That sounds simple. It is not. Founders know too much about their companies, so they put every important fact into the deck and accidentally hide the story. The better approach is to treat every slide as a proof obligation: what must an investor believe after seeing this slide that they did not believe before?

This guide gives you the complete structure, but not a rigid template. There is no universal slide order. Y Combinator’s seed fundraising guide explicitly says there is no fixed format or order, while its seed-deck template emphasizes clarity and concision. Sequoia’s pitching guide covers a familiar sequence—purpose, problem, solution, why now, market, competition, business model, team, financials, vision—but the sequence is a checklist, not a law.

The practical rule is this:

Start with clarity. Then move your strongest evidence earlier than convention says you should.

A pre-seed company may need to lead with founder insight and timing. A seed company growing quickly should reveal traction near the front. A Series A company should make repeatability, retention, and efficient growth difficult to miss.

Before the slides: decide which deck you are making

Most founders need two versions of the same story.

The send deck

This is the PDF or link that travels through inboxes, gets forwarded to partners, and may be read without you. It must be self-contained.

A send deck can carry slightly more context than a presentation deck, but “more context” does not mean paragraphs in 14-point type. Use a clear headline that states the point, one visual or evidence block, and short supporting copy. An investor should be able to skim only the headlines and understand the company.

The live deck

This is the version you present in a meeting or on a video call. It should be visually simpler because your voice supplies the detail. If a slide contains every sentence you plan to say, the investor will read ahead or stop listening.

Use the live deck to control pacing:

• one idea per slide;
• large, legible evidence;
• minimal body copy;
• product visuals where possible;
• backup slides for predictable questions.

Keep the facts, metrics, and narrative consistent across both decks. You are changing information density, not inventing a second company.

The appendix

The appendix is where depth lives without breaking the core story. Useful backup slides include:

• detailed cohort retention;
• pipeline composition;
• market-sizing assumptions;
• unit economics by segment;
• financial-model drivers;
• technical architecture;
• security or regulatory progress;
• product roadmap;
• customer references;
• cap table and prior financing summary.

A good core deck creates informed questions. A good appendix proves you anticipated them.

Write the investment story before opening presentation software

Do not start by choosing a template. Start with a one-page narrative.

Write one sentence for each of these prompts:

1. Company: We help [specific customer] achieve [valuable outcome] by [distinct mechanism].
2. Problem: Today, that customer loses [money, time, control, access, or opportunity] because [specific failure in the status quo].
3. Why now: A change in technology, regulation, cost, behavior, or distribution makes a new solution possible or necessary now.
4. Proof: The strongest evidence is [customer behavior, product use, revenue, retention, technical result, signed demand, or founder insight].
5. Scale: If the wedge works, the company can expand into [larger market or durable platform].
6. Team: We are unusually suited to win because [earned insight, technical ability, distribution access, or operating history].
7. Raise: We are raising [amount] to reach [measurable milestone] over [runway period].

Read the seven sentences straight through. If they do not form a coherent argument, slides will not fix them.

The story should create a chain, not a collection:

This customer has an urgent problem → the old solution fails → a new approach is possible now → our product delivers it → behavior shows it works → the market can become large → this team has a credible path to win → this capital reaches the next proof point.

The pitch deck at a glance: what every slide must prove

Use this as the completeness check before choosing the order.

Slide	What it must prove	Strong evidence	Common failure
Company purpose	A stranger can understand the company in one sentence	Specific customer, outcome, mechanism	A slogan that could describe 50 startups
Problem	A real customer has a costly, frequent, urgent pain	Customer behavior, workflow, primary research, source data	A broad societal observation with no buyer
Solution	The product changes the customer’s outcome	Product screenshot, workflow, before/after	A feature list or technical architecture dump
Why now	Timing creates an opening that did not exist before	Regulatory shift, cost curve, platform change, behavior change	”AI is growing” or another generic trend
Product	The thing exists or can credibly exist	Demo, screenshot, technical proof, user flow	Mockups that hide the core experience
Traction	Customers are pulling the product into the market	Revenue, growth, retention, usage, conversion, contracts	Vanity totals with no time frame or denominator
Market	A focused wedge can grow into a venture-scale outcome	Bottom-up customer count × realistic annual value	A top-down percentage of a giant report
Business model	Value can turn into durable revenue	Pricing, gross margin logic, contract/usage model	”Subscription” with no buyer or willingness-to-pay evidence
Go-to-market	The company can reach customers repeatedly	Working channel, sales motion, pipeline, cycle, conversion	A logo cloud of every possible channel
Competition	You understand alternatives and have a right to win	Direct and indirect alternatives, customer switching logic	”No competitors” or a self-serving 2×2
Team	This group has founder-market fit and execution range	Relevant lived experience, results, technical insight	Prestigious logos unrelated to the problem
Financials and milestones	The plan is operationally coherent	Driver-based forecast, hiring plan, cash and runway	A smooth five-year revenue curve with hidden assumptions
Ask	The round buys a specific reduction in company risk	Amount, runway, use, next-round milestone	”We are raising to grow”

Not every company needs exactly 13 slides. You may combine solution and product, business model and GTM, or financials and ask. A technically complex company may need two product slides. The point is to answer every material question once, clearly.

Slide 1: Company purpose

The first slide should make the company understandable before it makes the company impressive.

Use this formula:

[Company] helps [specific customer] achieve [specific outcome] through [distinct mechanism].

Good company descriptions exclude people. “Automated compliance for US community banks” is stronger than “the operating system for trust.” The first tells an investor which mental folder to open. The second creates decoding work.

Include:

• company name and logo;
• one declarative sentence;
• founder name and contact information in the send deck;
• optionally, one strong proof point if it changes how the rest of the deck is read.

Do not force the entire vision into the tagline. Clarity earns attention; ambition can expand later.

Slide 2: Problem

Describe a painful situation experienced by a specific person—not an abstract market inefficiency.

A strong problem slide answers:

• Who has the problem?
• What are they trying to accomplish?
• What happens today?
• Why is the status quo expensive, slow, risky, or impossible?
• How often does the problem occur?
• Who owns the budget or decision?

Show the current workflow when possible. A simple five-step process with the broken step highlighted is often more persuasive than a paragraph about industry transformation.

If you use a statistic, cite the original source on the slide or in a small footer. If the evidence comes from your own interviews, say what it is: “18 of 24 finance leads interviewed still reconcile this workflow manually” is evidence when it is true and documented. “Companies struggle with finance” is not.

Avoid leading with the total market. Investors cannot care about the size of a problem they do not yet understand.

Slide 3: Solution

The solution slide should answer “what changes for the customer?” in plain language.

Use a before-and-after structure:

Before	After
Trigger or input	Same trigger or input
Existing steps and friction	New workflow
Time, cost, or risk	Improved outcome

Describe outcomes before features. “Closes the books continuously by matching transactions as they happen” is more useful than “AI-powered reconciliation engine.”

If the product is technical, explain the mechanism at one level above implementation. The core algorithm may matter, but only after the investor understands what it enables.

Slide 4: Why now

“Why now?” is the counterfactual slide: if this opportunity is so good, why was the company not built successfully five years ago?

Good timing arguments point to a specific change:

• a technology became capable or cheap enough;
• a platform opened a distribution surface;
• regulation created a requirement or removed a barrier;
• buyer behavior crossed a threshold;
• a new data source became available;
• an incumbent’s business model created a neglected segment;
• a cost center became large enough to demand software.

A trend line is not enough. Connect the change to your product:

Because X changed, customers can now do Y, which makes our approach Z possible.

“The AI market is growing” is not a why-now argument. “Inference cost fell enough to run a model inside a workflow that was previously too expensive to automate” can be—if you can source the cost claim and show why it matters to your unit economics.

Sequoia’s guide puts “why now” directly after solution for a reason: timing explains why a new company has an opening against established alternatives.

Slide 5: Product

Show the product doing the valuable thing.

Prefer, in order:

1. a live demo;
2. a short recorded product flow;
3. a real screenshot with the key interaction highlighted;
4. a simple workflow diagram;
5. a prototype clearly labeled as a prototype.

The product slide is not a tour of navigation. Show the shortest path from input to outcome.

For a developer product, include the moment of technical leverage: a concise API request and result, an integration flow, a deployment change, or the reduction in steps. For a marketplace, show how supply and demand meet. For a physical product, show the use context and the enabling technical proof.

Silicon Valley Bank’s pitch-deck guidance makes the point directly: a product demonstration is more useful than a description when one is possible.

Slide 6: Traction

Traction is evidence that reality agrees with some part of your thesis.

The right metric depends on the business. Use the metric closest to durable value, not the largest number available.

B2B SaaS

• monthly or annual recurring revenue;
• net new revenue by month;
• logo and revenue retention;
• expansion;
• sales-cycle length;
• pipeline conversion;
• usage of the core workflow.

Consumer

• cohort retention;
• active users at the natural product frequency;
• engagement with the core action;
• organic acquisition or referral;
• paid conversion;
• contribution margin where monetization exists.

Marketplace

• gross transaction value alongside net revenue;
• transaction frequency;
• repeat rate;
• liquidity by market;
• take rate;
• contribution margin;
• supply and demand retention.

Pre-launch or deep tech

• signed design partners;
• paid pilots;
• letters of intent, with their non-binding nature stated honestly;
• benchmark or technical performance;
• regulatory milestones;
• validated demand from a defined buyer group;
• speed of product iteration.

Always label axes, dates, units, and definitions. “300% growth” is meaningless without the starting point and period. “MRR grew from $4,000 to $16,000 between January and June” is interpretable.

If traction is weak, do not camouflage it with cumulative signups, app-store impressions, or pipeline that has not advanced. Move traction later and lead with a stronger earned insight, technical breakthrough, or founder-market-fit argument. Weak evidence does not become strong because it is placed on slide three.

For a deeper look at the metric investors use to separate acquisition from product pull, see The Retention Curve That Predicts Your Next Raise.

Slide 7: Market

The market slide should show a credible path from a narrow entry point to a large outcome.

Start bottom-up:

Reachable customers × realistic annual revenue per customer = initial serviceable market.

Then explain expansion:

• more customers in adjacent segments;
• more seats, usage, locations, or volume per customer;
• additional products sold into the same account;
• geographic expansion;
• a new transaction layer or marketplace take rate.

TAM, SAM, and SOM are useful only when the assumptions are visible. SVB’s guide defines the familiar hierarchy, but the calculation matters more than the labels.

A defensible market slide might show:

Layer	Calculation	What it says
Beachhead	8,000 US target accounts × $18,000 ACV	The first segment can support a meaningful company
Expansion	35,000 adjacent accounts × $30,000 ACV	The sales motion can broaden
Platform	Transaction or product expansion model	The upside is not capped at the first SKU

Those numbers are illustrative—not benchmarks. Your deck needs sourced account counts and pricing assumptions grounded in your actual buyer.

Avoid “If we capture 1% of a $100 billion market…” It proves neither reachability nor customer value.

Slide 8: Business model

Explain who pays, what they pay for, and how revenue grows.

Cover:

• buyer and budget owner;
• pricing model;
• value metric;
• contract or transaction structure;
• gross-margin logic;
• expected expansion or repeat behavior;
• major cost required to deliver the product.

For SaaS, name whether pricing is per seat, usage-based, tiered, or platform-plus-usage. For a marketplace, show the take rate and who pays it. For fintech, separate interchange, subscription, spread, and transaction revenue. For hardware, show product margin and recurring service revenue separately.

If pricing is still a hypothesis, say so and show what customer behavior informed it. Our guide to setting your first SaaS pricing model explains how to choose a value metric without pretending early data is more precise than it is.

Do not confuse a revenue mechanism with an economic model. “We charge a subscription” does not answer whether the price supports customer acquisition, service, infrastructure, and growth.

Slide 9: Go-to-market

A go-to-market slide should describe a motion, not list channels.

Answer:

1. Who is the first buyer?
2. What event makes them receptive?
3. How do you reach them?
4. What gets them to try or buy?
5. How long does the decision take?
6. Who must approve it?
7. What evidence says this can repeat?

A useful GTM slide might diagram:

Trigger → channel → conversion step → sales/product motion → activation → expansion

For example:

New compliance requirement → partner webinar → assessment call → paid pilot → annual contract → second department

If the motion is founder-led, say so. Founder-led sales is not a weakness at seed; pretending it is already a scalable machine is. Explain what you have learned, which parts repeat, and what the next hires will systematize.

Use channel economics only when you have enough data to define them. Early CAC calculated from a tiny campaign and founder labor can be misleading. Report the evidence you actually have: response rate, qualified meetings, pilot conversion, sales cycle, or organic activation.

Slide 10: Competition and alternatives

Every problem has an alternative, even when no startup looks exactly like yours.

Your real competitors may be:

• a direct software product;
• an adjacent platform;
• an internal team;
• a spreadsheet;
• a service provider;
• doing nothing;
• tolerating the problem.

The competition slide should prove two things:

1. you understand why customers choose the status quo;
2. your advantage changes a buying decision that matters.

Avoid a feature matrix where your company has every checkmark. It signals that you chose the axes after choosing the winner.

Better formats include:

• workflow comparison: where the alternative breaks;
• customer segment map: who each option is built for;
• tradeoff table: where competitors are honestly stronger and why your target buyer still chooses you;
• strategic wedge: the initial advantage and how it compounds through data, distribution, network effects, switching costs, or cost structure.

J.P. Morgan’s guidance warns founders against claiming a blue ocean. An investor may have reviewed several companies attacking the same problem that week. Saying “no competition” usually proves a research gap, not a moat.

Slide 11: Team

The team slide answers: why are these founders unusually equipped to discover and execute the winning path?

For each founder, connect experience to the company:

• lived the problem as a customer or operator;
• built the relevant technical system;
• sold to the target buyer;
• developed unusual distribution access;
• worked together under pressure;
• achieved a result that predicts this work.

Use one or two relevant proof points per person. A wall of employer logos asks the investor to infer the connection.

At pre-seed, founder-market fit can be one of the strongest signals in the deck. At later stages, add the leadership capacity required for the next phase and be honest about critical gaps.

Do not use advisors to cover a missing founding capability. YC’s seed-deck guidance focuses the team slide on founders and what makes them suited to the problem. Advisors can appear in the appendix when their involvement is real and material.

Slide 12: Financials and operating milestones

Financial projections should expose the operating model, not perform certainty.

At pre-seed, a simple 18–24 month plan can be enough:

• hiring dates and loaded costs;
• product and infrastructure spend;
• sales or launch assumptions;
• revenue when applicable;
• monthly net burn;
• ending cash;
• milestones reached.

At seed and Series A, connect the forecast to business drivers:

• new customers;
• price or ACV;
• conversion;
• sales capacity and ramp;
• retention and expansion;
• gross margin;
• headcount;
• cash collection timing.

Show base assumptions. Keep the detailed model in the appendix or data room, but make the core deck internally consistent with it. A deck that claims a capital-efficient motion while the financial model assumes a large sales team will fail diligence quickly.

Our startup financial model guide walks through the linked schedules and scenario structure. Use the model to decide the round—not merely to justify a number you already chose.

Slide 13: The ask

A useful ask slide completes this sentence:

We are raising [amount] to fund [operating plan] for approximately [runway], reaching [measurable milestone] that removes [next major company risk].

Include:

• amount being raised;
• financing stage and, when appropriate, instrument;
• expected runway;
• two to four major uses of funds;
• operating milestones;
• the state the company should be in before the next financing.

The milestone should be specific enough to evaluate:

• ship and validate a regulated product;
• reach a defined recurring-revenue range with evidence of retention;
• prove a repeatable acquisition channel;
• complete a technical benchmark at production scale;
• expand from paid pilots into annual contracts;
• launch in a second market after proving liquidity in the first.

Do not reduce the slide to a use-of-funds pie chart. “50% product, 30% sales, 20% operations” says where money goes, not what changes.

Build the raise from cash and milestones. Pre-Seed Fundraising, Decided by Data explains the milestone-backwards method, while SAFE vs. Convertible Note covers the instrument tradeoffs once you know what you need to raise.

Change the order by funding stage

Templates fail when they treat a company with an idea and a company with repeatable revenue as if investors evaluate them the same way.

Stage	Lead with	Prove next	What can stay lighter
Pre-seed	Founder insight, problem, why now, product vision	Team, customer evidence, technical feasibility, market, milestone plan	Detailed historical metrics and precise long-range forecasts
Seed	Product and strongest traction signal	Retention or usage, wedge, business model, early GTM repeatability, team	Fully optimized unit economics
Series A	Growth quality and repeatability	Retention, expansion, sales efficiency, market scale, leadership, operating plan	Basic product explanation unless the product is complex

Pre-seed order

A practical pre-seed sequence is:

1. company purpose;
2. founder insight or problem;
3. why now;
4. solution and product;
5. customer evidence or technical proof;
6. market;
7. business model;
8. early GTM plan;
9. competition;
10. team;
11. operating milestones;
12. ask.

Investors know the business is early. The deck should prove that the founders have earned an insight, can build, can recruit early believers, and know which risk the round must remove.

Seed order

If the product has real use, move evidence forward:

1. company purpose;
2. problem and why now;
3. solution/product;
4. traction;
5. customer or cohort evidence;
6. market;
7. business model;
8. GTM;
9. competition and advantage;
10. team;
11. financial plan;
12. ask.

At seed, “people tried it” matters less than “the right people return, pay, expand, or refer.”

Series A order

A Series A narrative usually needs to prove a machine is forming:

1. company purpose plus headline scale;
2. growth and retention;
3. customer proof;
4. product and moat;
5. market expansion;
6. repeatable GTM;
7. business model and unit economics;
8. competition;
9. team and leadership plan;
10. financial plan;
11. use of funds and Series B milestones.

The company story still matters, but operating evidence carries more of the argument.

Design the deck for comprehension, not applause

Presentation design has one job: make the evidence easier to understand.

Use assertion headlines

Replace labels such as “Market” with the point of the slide:

• Weak: Market Opportunity
• Strong: Independent dental practices spend $X annually across three disconnected workflows

The second headline makes a claim. The body proves it.

Keep one idea per slide

Y Combinator’s deck-design guidance recommends identifying the few ideas investors should remember, then making slides simple and obvious. If a slide needs two headlines joined by “and,” split it.

Make charts answer a question

A chart should show one conclusion at a glance. Highlight the relevant series, label the key point directly, and remove decorative gridlines or legends that force decoding.

Never manipulate axes, omit time periods, or combine unlike metrics to manufacture momentum. Investors will ask for the underlying data.

Show sources

Add a small source line for external claims. For internal data, define the cohort, period, and metric. Keep a claim log with:

• slide number;
• claim;
• source URL or internal query;
• date accessed or data period;
• owner responsible for verification.

This takes an hour and prevents a painful diligence correction later.

Make the deck portable

Before sending:

• export to PDF and inspect every page;
• confirm fonts render correctly;
• compress images without making charts blurry;
• remove private customer data;
• check links;
• use a stable filename with company and month;
• include founder contact information;
• test on a laptop and phone.

Tracking links can help you understand whether a deck was opened, but do not mistake opens for investor intent. The goal is a qualified conversation.

The red-team review: test the deck before investors do

Most deck feedback is too polite. “Looks great” does not tell you whether the argument works.

Run these five tests.

1. The four-minute comprehension test

Give the send deck to a smart person outside your company. After four minutes, take it away and ask:

• What does the company do?
• Who has the problem?
• Why now?
• What is the strongest proof?
• How does the company make money?
• Why can this team win?
• How much is being raised, and what will it achieve?

Do not explain their wrong answers. Record them. A wrong retelling is a deck problem.

2. The headline-only test

Read only the slide headlines in order. They should form a coherent investment argument. If the sequence reads “Problem / Solution / Market / Team,” the headlines are labels, not a story.

3. The claim audit

For every number and comparative statement, ask:

• Is it true?
• Is it current?
• Is the definition clear?
• Is the denominator shown?
• Can we produce the source or raw data?
• Would the claim still feel honest if an investor called the source during the meeting?

Delete any claim that survives only because it is vague.

4. The alternative-explanation test

Try to disprove your own interpretation.

If usage is growing, could it be a launch spike? If revenue is rising, is one customer responsible? If retention looks strong, is the cohort mature enough? If pipeline is large, how much is qualified? If the market seems huge, can the target customer actually buy at the assumed price?

Put the stronger, more honest interpretation in the deck. Credibility compounds.

5. The unanswered-question test

Write the ten questions an investor is most likely to ask. For each, decide whether the answer belongs:

• in the core deck because the story is incomplete without it;
• in the appendix because it is predictable depth;
• in the data room because it requires detail;
• in conversation because the answer depends on context.

The goal is not to remove every question. It is to make the questions better.

A practical build process

Step 1: Build the evidence inventory

Before writing slides, collect:

• product screenshots and demo flow;
• customer interview notes;
• usage and revenue exports;
• cohort analysis;
• pricing and contracts;
• pipeline stages;
• market-source links;
• competitor notes;
• founder bios and relevant proof;
• financial model and runway plan.

You cannot design around evidence you have not assembled.

Step 2: Write the headline spine

Create 12–15 blank slides and write only the assertion headlines. Rearrange them until the argument works.

Step 3: Add one proof per slide

Choose the best chart, screenshot, workflow, table, or short evidence block. Do not add decoration to make a weak slide feel finished.

Step 4: Build the appendix from rejected detail

When you remove material from the core deck, move useful depth into the appendix. Cutting is easier when the work is not lost.

Step 5: Reconcile the deck with the model and data room

Check that revenue, customer count, burn, headcount, runway, market assumptions, and financing history agree everywhere. Version drift is a credibility problem.

Step 6: Rehearse questions, not a script

Know the first sentence you will say on every slide, but spend more time practicing the transitions and hard questions. An investor meeting is a discussion, not demo day.

Step 7: Update from patterns, not every opinion

Log investor questions. If several qualified investors misunderstand the same point, revise the deck. Do not rebuild the story after every meeting based on contradictory personal preferences.

Common pitch deck mistakes

The company is impossible to describe

If the first slide requires a minute of explanation, the category and customer are not clear enough.

The deck starts with market size

A giant market does not make an unclear problem investable.

The slides describe features instead of outcomes

Investors need to understand what customers can do that they could not do before.

Traction has no denominator

Totals, percentages, and growth rates without dates or starting points invite suspicion.

The market is top-down only

A report can validate the category, but it cannot prove your reachable wedge or price.

The competition slide denies reality

The status quo is always a competitor. “No competitors” usually means “we have not mapped the buying decision.”

The team slide is a résumé collage

Relevant earned insight beats prestige without connection.

The projections are detached from capacity

Revenue does not grow because a spreadsheet applies 15% every month. Customers arrive through a product, channel, and team with constraints.

The ask is not connected to a milestone

A round is not a budget refill. It should buy enough time to remove the next company-killing risk.

The deck is overdesigned

SVB’s guide warns that a slick, overly produced deck can signal misplaced priorities. Investors fund companies, not transitions.

The final standard

A strong pitch deck is not the one with the prettiest template or the canonical slide order. It is the one an informed investor can retell accurately after a few minutes—and still has questions worth asking.

Before you send it, confirm:

• the company is clear in one sentence;
• the problem belongs to a specific buyer;
• why now is causal, not trendy;
• the product is shown;
• traction uses the right metric and definition;
• market sizing is bottom-up;
• the business model names who pays and how revenue grows;
• GTM describes a motion;
• competition includes the status quo;
• the team has relevant proof;
• the financial plan exposes assumptions;
• the ask connects capital to a milestone;
• every numerical claim has a source;
• the send deck works without narration;
• the appendix answers predictable questions.

The deck will not close the round by itself. It can do something more useful: get the right investor to lean forward and say, “Tell me more.”

For more on the full fundraising sequence, start at the Fundraising pillar, then use the pre-seed sizing guide and SAFE-versus-note comparison to connect the story in the deck to the structure of the round.