Pitch Deck Structure (2026): Slide-by-Slide Outline, Copy-Paste Script & 60s Video Blueprint
A pitch deck should help the listener follow your argument. Start with the customer and problem, show how the product helps, separate evidence from assumptions, explain the business and finish with a specific request. Slide count comes after that sequence.
5 min read · By Axiom Lab · Published · Updated
Who is in the room
This outline is for an early-stage investor conversation. A customer proposal needs more attention to scope, implementation and price; a class project needs the method and assessment criteria. Do not send the same deck unchanged to every audience.
The six groups below are an outline, not a six-slide rule. A five-minute first conversation might combine some topics. A longer meeting may need separate market, competition, team and financial slides. Follow the recipient’s instructions.
The listener can connect a customer problem to our product, evidence, business and requested next step.
| Format | Duration | Best use & goal |
|---|---|---|
| Elevator pitch | 30s (~65–75 words) | First introduction or referral; name the problem and earn a follow-up conversation. |
| Async pitch video | 60–90s (product range: 30–180s) | Sent before a meeting; stands on its own with problem, solution, proof and dated request. |
| Live deck pitch | 5-min live talk + Q&A | Demo Day or formal review; cover unit economics, assumptions, risks and live questions. |
What to say, in order
- Customer and problemOpening
- Product and workflowShow the change
- Evidence and unknownsSupport the claim
- Market and businessExplain the model
- Team and executionExplain who will deliver
- Ask and next milestoneClose
Customer and problem
Name a specific user, the task they struggle with and the current alternative. Ground the problem in an observation you can substantiate.
Product and workflow
Use a product image or three-step workflow to explain one useful task. Label a prototype as a prototype.
Evidence and unknowns
Show what you have observed and what remains an assumption. Include the source, period and definition for any metric.
Market and business
Define the buyer, pricing hypothesis, relevant alternatives and a bottom-up starting market. State financial assumptions explicitly.
Team and execution
Connect each role to the work ahead. Describe completed milestones and the next risks to resolve; do not invent credentials.
Ask and next milestone
State what you are requesting and what it enables. Put detailed cost assumptions in the appendix if they would interrupt the main story.
Give every slide one job
ILLUSTRATIVE REWRITE
Before
Problem, market size, product features and the funding request compete on the same slide.
After
One slide explains the customer’s task. The next shows the product workflow. Evidence and the request each have their own place.
Separating the questions makes gaps visible. If you cannot support a claim, label the assumption or remove it instead of hiding it among other material.
Fill the brackets
If a bracket has a missing fact, cut the sentence. Do not invent a number to make the line sound finished.
- Problem slide
[Customer] currently uses [alternative] to [task]. We observed [specific issue, with source].
- Product slide
Our [prototype/product] lets them [one workflow]. Here is [visual demonstration].
- Evidence slide
We have [verified observation]. We have not yet established [unknown].
- Business slide
The intended buyer is [role]. Our current pricing and delivery assumptions are [assumptions].
- Team slide
[Person/role] owns [relevant work]. The next milestone is [verifiable output].
- Ask slide
We are seeking [specific request] to reach [milestone]. The next conversation should resolve [question].
Worked outline: an early inventory prototype
Fictional editorial example. No customers, revenue, funding or performance results are claimed.
Problem: a small workshop tracks stock across a spreadsheet and handwritten notes. Before presenting this as a common problem, the founder needs permissioned observations from actual workshops.
Product: show a prototype screen for recording an incoming delivery and updating an item count. Mark it “prototype” and show the complete task rather than a wall of feature icons.
Evidence: display the current prototype state and a list of research questions. Do not fill an empty traction slide with invented signups or unlabeled projections.
Business: identify the workshop manager as the proposed buyer. List pricing, support effort and data-import costs as hypotheses to test.
Team and next step: explain who will run interviews and maintain the prototype. Request introductions to workshop managers for a scoped workflow review.
What to have ready
A source ledger
One product sequence
A clear request
An appendix
A sent deck needs more context than a live deck
In a meeting, your voice can explain a short headline and visual. A deck read without you needs captions, definitions and source notes. Test the sent version by asking someone to describe the argument without a spoken explanation.
A video summary can introduce the same argument, but it does not replace due diligence or a complete financial model. Use a shorter script and point to the full deck for details.
Where it goes wrong
Treating an outline as a mandatory slide count
Confusing a target with traction
Make it a film
Complete the project brief with your verified facts, then choose the part of the deck that belongs in a short video introduction.
A project video runs about a minute, in three chapters: the painful situation, the solution, and the advantages. You submit the name, the audience, the situation, the solution, how it works, the evidence and the next step, and you can upload a plan, a deck, a PDF or photos. Select Start to analyse the material. On the film page, review the suggested length and select Confirm and start to proceed. Do not include a result you cannot source. A film is delivered only after it passes checks, and charged only once delivered.
During the beta, a new address needs an invite code. If you do not have one, write to sales and ask for access.
FAQ
What should a pitch deck include?
Cover the customer problem, product, evidence, market, business model, relevant alternatives, team and request. The order and number of slides depend on the audience and stage.
How many slides should a pitch deck have?
There is no universal number. Use the meeting length and recipient’s requirements, then check whether each essential question is answered without overcrowding.
Is this a downloadable PowerPoint template?
This page provides an outline and speaker-note examples. The linked project brief is an editable text template, not a designed PPTX deck.
Sources and editorial notes
- Y Combinator · How to Pitch Your Company
Clear explanations of the product, progress, business model and request.
- Sequoia Capital · Writing a Business Plan
Questions to cover when explaining a business, including the customer problem and alternatives.
These references provide related principles. The sequence, timings and fill-in scripts on this page are Axiom Lab's editorial suggestions, not endorsements by those organizations or measured fundraising or sales results. Adapt them to the audience's requirements and replace placeholders with verifiable facts.
Our public demonstrations use fictional projects and include their actual inputs and transcripts; they are not customer evidence. View the production notes · Editorial and corrections policy