There's a proven narrative structure for B2B sales decks. Here are the 12 slides, the purpose of each, and the design requirements that make them work.

Pitch Deck Story Structure: 12 Slides That Sell

The best B2B sales decks follow a narrative structure that mirrors the buyer's evaluation process: acknowledge the problem, present the solution, prove it works, explain the model, and make the next step obvious.

Here are the 12 slides, the purpose of each, and what the design needs to accomplish.

Slide 1: The Opening Context (20 seconds)

Purpose: Establish what world the buyer lives in. A brief, specific description of the market context or trend that makes the rest of the conversation timely.

Design requirements: One strong visual or data point. No bullet lists. The visual should be a metaphor or illustration that frames the problem emotionally, not just logically.

Slide 2: The Problem

Purpose: Make the buyer feel the problem. Describe the situation your buyer is currently in — the version without your product.

Design requirements: The problem should be described from the buyer's perspective, not the vendor's. "Your campaigns ship slower than your ideas" is buyer perspective. "Design is a bottleneck in GTM organizations" is vendor perspective.

Slide 3: The Cost of Inaction

Purpose: Quantify what the problem costs. This is often missing from sales decks and its absence allows prospects to defer.

Design requirements: A clean, concrete number or estimate. "Teams that can't iterate design weekly lose an estimated X leads per quarter to competitors who can." Visual emphasis on the cost figure.

Slide 4: The Solution Introduction

Purpose: Introduce your solution at the category level. Not a feature list — a positioning statement.

Design requirements: One strong headline, one supporting sentence. Visual that shows the "after" state — what the world looks like with the solution.

Slide 5: How It Works (The Process)

Purpose: Remove the "but how does it actually work?" anxiety. A 3-step process is ideal.

Design requirements: Three visual steps with brief labels. Icons or illustrations for each step. The steps should feel intuitive, not complex.

Slide 6: What You Get (Scope Clarity)

Purpose: Be specific about what's included and what isn't. Scope clarity builds trust.

Design requirements: A clear list of included items (with visual checks or icons) and 1-2 clear "out of scope" items. The latter builds credibility — companies that know their limits are trustworthy.

Slide 7: Social Proof (Case Study)

Purpose: Prove the solution works for someone like the buyer.

Design requirements: One specific customer, their situation before, their outcome after. A pull quote from the customer. A visual that represents the customer's industry or company type.

Slide 8: More Social Proof (Logo Bar or Metrics)

Purpose: Validate at scale. Just because one customer succeeded doesn't mean the pattern holds.

Design requirements: Either a logo bar of recognizable customers (for brand recognition) or specific aggregate metrics ("Across 40 B2B SaaS customers, average design cycle time decreased by 72%").

Slide 9: Pricing Overview

Purpose: Establish price and frame value relative to alternatives.

Design requirements: Clear tier differentiation, the price point (or a range), and a cost anchor ("One designer hire is $90,000+ fully loaded. Sako Ops Base is $4,500/month"). Don't require buyers to ask about price — it signals evasion.

Slide 10: The Comparison (Optional but powerful)

Purpose: Place yourself favorably against the alternatives the buyer is already considering.

Design requirements: Simple comparison table. Be honest — mark the dimensions where competitors are comparable or better. Dishonest comparisons get called out and damage trust.

Slide 11: The Team / About

Purpose: Establish that the people behind the product are credible.

Design requirements: Focus on relevant experience, not impressive titles. "20 years working in B2B SaaS GTM" beats "Former [Famous Company]" for your specific buyer.

Slide 12: The Next Step

Purpose: Make the post-meeting action obvious. One clear action, not a menu.

Design requirements: "Here's what we need from you to [start/proceed to the next step]." Not "Questions?" — a specific, single, actionable next step with a timeline.

The narrative arc: problem → cost of inaction → solution → proof → model → next step. Follow the arc with this structure and your deck creates a buying journey, not just a presentation.

Get your sales deck designed with this structure →. See examples of Sako's deck work →.