Pitch deck outline
The slide order investors expect, with what each slide has to establish before the next one lands.
Copyable template
Pitch deck
Move from information to investor conviction.
By The Raise Memo team · August 19, 2026 · Updated October 25, 2026
The most useful pitch narrative explains why this company deserves further investigation. A reader should understand who needs the product, how the company helps, what has happened so far and what the proposed funding would let the team learn or deliver next. The order can change with the company; the evidence behind the story should remain consistent.
Decide what you want the next conversation to resolve. At an early meeting, that may be whether the investor understands the customer and sees a plausible opportunity. During diligence, it may be whether retention, technical results or contract evidence supports a claim. A deck intended to start a conversation needs different depth from a document answering an investment committee's detailed questions.
Write a short working explanation before arranging slides: “We help this customer do this important task. The current approach creates this problem. We have built and tested this alternative. Funding would let us reach this next milestone.” Fill each part with something concrete from your company, then check which statements are observations and which are still plans.
If you begin with a customer problem, the next section should show how your product changes that customer's work. Product evidence leads naturally to questions about adoption and payment. Those results lead to the size of the reachable market, the route to customers and the team needed to deliver. The funding request should follow from the work still to be done.
Some companies have a result that deserves to appear earlier. A completed technical test might make a hard-to-explain product easier to understand. A retention cohort may establish why an existing product matters. Present that result with enough context to interpret it, then fill in the customer and product story. A large number with no definition cannot carry the opening by itself.
Imagine a company building maintenance software for small manufacturers. In this example, the draft opens with a broad industrial-software market estimate, follows with twelve feature screenshots and ends with a request for $900,000. Those facts do not yet explain why a manufacturer would buy or what the money would accomplish.
A clearer sequence starts with the maintenance coordinator who currently assembles work orders from spreadsheets and messages. It then shows one completed workflow in the product. The evidence section reports that three of five pilot sites used the workflow each week during a six-week test, while two sites did not complete setup. These are invented teaching inputs, not a customer result.
The commercial section separates the two paid pilots from the three unpaid pilots and explains the proposed renewal terms. The funding section identifies the next test: whether the team can onboard ten additional sites and retain their use without the founders doing each setup manually. The $900,000 request still needs a cost and cash plan; a well-told story does not validate the amount.
If a result comes from a small sample, name the sample. If customers paid a discounted pilot fee, do not present it as established annual pricing. If an integration is planned, distinguish it from a working feature. These details let an investor ask a useful question instead of discovering later that two slides used different definitions.
Use an appendix for supporting calculations and detailed methods, but keep any qualification that materially changes the headline on the main slide. For example, revenue from a one-time implementation project should not be hidden inside a recurring-revenue chart simply because the total looks stronger.
Ask a reader unfamiliar with the company to describe the customer, the product's role, the strongest evidence and the purpose of the raise. If their answer differs from yours, find the point where the explanation became ambiguous. Revise that section before spending another afternoon adjusting the presentation's visual details.
Geoff Ralston's 2016 Demo Day guide advises developing the story before building slides around it. Its short-presentation setting is different from a full capital raising process; it does not establish a required slide count or guarantee investor interest.
The Pitch Deck Pressure Test can help you work through the questions behind the presentation. Keep a claim-and-evidence note for each major section so that a later revision changes the explanation without accidentally changing the underlying facts.
Apply this to your company
A structured self-check on how clearly your deck tells the story.
Take it with you
The slide order investors expect, with what each slide has to establish before the next one lands.
Copyable template
Draft, cut, and test the one sentence that has to do the work before anyone opens the deck.
Copyable template
Originally published in The Raise Memo.
Build a pitch deck around the customer, evidence and funding decision, with a clear source for every important claim.
Choose the shortest deck that makes the decision legible.
Amount, use of funds, and the milestones the capital buys.