Pitch deck help: writing the story behind the slides

Content and narrative, not visual design

Before anything else, it helps to be clear about what a pitch deck actually needs solved. There are two separate problems hiding inside "make me a pitch deck." One is visual: layout, typography, color, iconography, how the slide looks when it is projected on a screen or scrolled through in an email. The other is narrative: what each slide needs to say, in what order, and how the whole sequence adds up to a case someone would actually act on. These are different skills, done by different kinds of specialists, and conflating them is one of the most common reasons decks come out weak on both fronts.

This guide is about the second problem: the story and the content. It is the harder problem to get right and the one that determines whether a deck works, regardless of how it looks. A beautifully designed deck with a muddled problem statement and an unsupported market-size claim still fails. A plainly formatted deck with a sharp, specific, well-sequenced story can still get a second meeting. Get the narrative right first. Design is a finishing step, not a substitute.

The standard slide sequence and what each slide's job is

Most fundraising decks that work follow a recognizable sequence, not because investors demand a formula, but because this order answers their questions in the sequence they naturally ask them. Deviating from it is fine when there's a good reason. Skipping a slide entirely because it feels uncomfortable to write (the competition slide, the honest financials slide) usually is not a good reason.

Ten slides is a guideline, not a rule. Some decks fold competition into the market slide, or combine business model and traction when the two are tightly linked. What matters is that every one of these questions gets answered somewhere in the deck, clearly, and that the deck doesn't spend three slides on something a reader will skim past while giving one rushed sentence to something they will scrutinize.

What makes each slide land instead of fall flat

The sequence above is the skeleton. Most decks that fail aren't missing a slide, they have all ten and still don't work, because the content on each one is vague, unsupported, or generic. A few slides deserve particular care.

The problem slide should be specific and relatable rather than abstract. "Businesses struggle with inefficient workflows" describes nothing and could open a deck for almost any software company ever pitched. A problem stated as a concrete situation, with a specific person or role experiencing a specific frustration in a specific moment, is what makes a reader recognize the problem as real rather than invented to justify the product.

The market-size slide should show credible reasoning for its numbers, not an inflated top-down guess with no visible methodology. A slide that simply states "$50 billion market" with no explanation of where that figure came from invites the exact skepticism it was meant to prevent. Showing the calculation, even a simple one (this many potential customers, at this price, buying this often), does more to build confidence than a bigger, unsupported number ever will.

The traction slide should lead with the most credible evidence available, even if it is modest, rather than padding the slide with vanity metrics that don't actually indicate demand. A small number of paying customers who renewed is worth more on this slide than a large number of app downloads or newsletter subscribers that never converted to anything. Padding a thin traction slide with metrics chosen because they're large numbers, rather than because they're meaningful ones, tends to read as exactly what it is.

The ask slide should be a specific number with a specific stated use, not something vague like "raising to grow the business." A specific ask ("raising $X to fund a defined use, over a defined period, to reach a defined next milestone") signals a team that has actually thought through what the money accomplishes. A vague ask signals the opposite, whether or not that's fair.

The solution, business model, team and competition slides

The solution slide should connect directly back to the problem slide that came before it, in language a reader can follow without a product demo standing next to it. It is tempting to fill this slide with a feature list, but a feature list answers "what does it do" without answering the more important question, "why is this the right way to solve the specific problem just described." A solution slide that opens with the connection ("because of X, we built Y to do Z") reads as a reasoned choice rather than a list of capabilities in search of a justification.

The business model slide needs to state, plainly, who pays, how much, and how often. This sounds obvious, but a surprising number of decks describe an entire product without ever stating clearly whether the customer is billed monthly, annually, per transaction, or some other way, and at what price point. If real unit economics exist, even rough ones, showing them (what it costs to acquire a customer, what that customer is worth over time) does more for credibility than restating the product's benefits a second time.

The team slide needs to do more than list titles and past employers. Its actual job is to answer a specific question: why is this team, specifically, positioned to execute this specific idea. That might be direct experience in the exact problem space, a track record of building and shipping in a related area, or a combination of skills on the team that maps cleanly onto what the business actually needs to do next. A team slide that reads as an impressive résumé recap but never connects those résumés to this particular business tends to leave the reader wondering rather than reassured.

The competitive landscape slide is often the one founders most want to skip or soften, out of a fear that naming real competitors makes the opportunity look smaller. The opposite is usually true. A reader who already knows the space will assume competitors exist whether the deck mentions them or not, and a deck that pretends otherwise reads as either naive about its own market or evasive about a hard question. Naming the real alternatives, including "doing nothing" or "solving it with a spreadsheet" where that's the honest comparison, and stating clearly why this approach wins on the dimension the customer actually cares about, builds more confidence than silence ever could.

An example: from vague to specific on the problem slide

The first version is a category of problem, not a problem. It could sit at the front of hundreds of unrelated decks with no changes. The second version names a specific person, a specific activity, a specific cost, and makes the reader picture it, which is what earns the next slide the benefit of the doubt.

What to gather before you start

The single biggest factor in how strong a pitch deck turns out is not the writing, it is the quality and specificity of what the founder brings to the process. A specialist can shape a narrative and sharpen language, but cannot invent your traction, your market reasoning, or your team's actual background. Before starting an order, it helps to have on hand: a plain description of the problem in your own words, including a specific example of someone experiencing it; whatever traction numbers exist, even early or modest ones, along with honest context for what they mean; the reasoning behind your market-size estimate, not just the final number; a clear statement of how the business makes money; short, honest bios for each team member that explain their relevant background; and a specific number for the ask along with what it funds.

None of this needs to be polished or already written as deck copy. Bullet points, a voice note, or a rough email are enough starting material. The specialist's job is to take that raw material and turn it into a clear, well-sequenced narrative, not to guess at facts you haven't provided. The more specific and honest the raw material, the more specific and credible the finished deck can be.

Adapting the narrative by audience and purpose

Not every deck built from this same content is aimed at the same reader, and the emphasis should shift with who is reading it. An investor pitch deck, a customer-facing sales deck, and an internal stakeholder deck share some structural bones, but they are not the same document with a different cover slide.

An investor deck weights market size, traction and team credibility most heavily, because an investor's decision is fundamentally a bet on whether this specific team, in this specific market, at this specific moment, can turn a return. A customer-facing sales deck cares far less about your fundraising history or total addressable market and far more about the problem/solution fit for that specific prospective customer's situation: their workflow, their cost structure, their reason to switch. An internal stakeholder deck, aimed at getting a budget or headcount approved inside an existing company, usually needs to spend more time on how the initiative fits the company's existing priorities and less time selling the market opportunity, since the audience already works inside that market. Writing one deck and hoping it serves all three audiences equally usually means it serves none of them well.

The practical effect of this is that the same underlying facts about a company can be true across all three decks while the deck itself reads quite differently. A traction number that would headline an investor deck's second slide might be a footnote in a customer deck that leads instead with a case study specific to that customer's industry. A team slide built around fundraising credibility for investors might be replaced entirely in a stakeholder deck by a section on internal resourcing and timeline, since the internal audience already knows the team. Deciding who the deck is actually for, before writing a single slide, saves the far more common mistake of writing a deck that tries to be everything to everyone and ends up persuasive to no one in particular.

Common mistakes that undercut an otherwise solid pitch

• A deck that is actually a business plan crammed onto slides, with dense paragraphs and small text that a reader has to study rather than absorb at a glance.
• A market-size claim with no visible methodology behind it, leaving the reader to either take it on faith or discount it.
• A team slide that lists titles and past employers without explaining why this specific team is positioned to execute this specific idea.
• An ask that is vague about the use of funds, leaving the reader unsure what the money actually buys.
• Skipping or softening the competitive landscape slide out of discomfort, which reads as either naivety about the market or an attempt to avoid a hard question.
• Financial projections presented with false precision, as if they were known facts rather than assumptions, without stating what those assumptions are.
• A solution slide that describes features without reconnecting to the specific problem stated earlier in the deck.
• Too much text on a single slide, forcing the reader to choose between listening to the presenter and reading the slide, and usually doing neither well.

How ApplicationWriters helps with a pitch deck

ApplicationWriters helps with the written content and narrative structure of a pitch deck: the slide sequence, what each slide says, and how the story holds together for the audience you're presenting to. Choose Create from my information and a specialist builds the narrative and slide-by-slide content from the details you provide about your company, market and numbers. If you already have a deck, choose Improve my draft to sharpen the story while keeping your own material, or Edit and proofread for a lighter pass. Visual design and slide layout are a separate consideration the client typically handles or sources separately, unless an order specifically includes design work. Every order is priced from the number of slides, shown before you pay.

Frequently asked questions

Get pitch deck help