# Slide templates Markup for the shell in [deck-design-system.md](deck-design-system.md). Every slide is a `
` with a label, a claim as the headline, one block of evidence and a `.notes` block. Which slides to use, and in what order, is in [pitch-structure.md](pitch-structure.md). ## Per-slide content | Slide | Headline shape | Evidence block | Speaker-note prompt | |---|---|---|---| | Title | `{{NAME}}`, then "does {{WHAT}} for {{WHO}}" | Category and stage tags | The bar test in one breath; create curiosity, don't explain | | Problem | The pain as a claim, with a number | Three pain points, or one real user quote | Let it land; "costs $X, takes Y hours, fails Z% of the time", each sourced | | Why now | "Until {{CHANGE}}, this wasn't possible" | Before/after of the enabling change, dated | Why didn't this exist two years ago? | | Solution | What it does in one sentence | Three features, each answering one pain | Map each feature to a pain from the problem slide | | Demo | The outcome the user gets | A real screenshot (inlined), three callouts, explorer link | Live if you can, recorded backup either way | | Why crypto / Solana | What is impossible without the chain | Two or three concrete reasons as you measured them | If this slide is hard to fill, revisit the idea | | Traction | The best checkable metric and its trend | Three metric cards with sources ([onchain-metrics.md](onchain-metrics.md)) | Explain filtering of bots and incentivised flow before they ask | | Market | Bottom-up SAM as one number | The multiplication, each factor sourced | Never top-down | | Competition | The one dimension you win on | Comparison table with your row highlighted | Admit competitor strengths | | Business model | Who pays, when, how much | Price, volume and margin after onchain costs | "Free now, monetise later" is not a model | | Team | Why this team for this problem | Two to four people, one shipped thing each | Shipped, scaled, domain expert; not "passionate" | | Ask | Amount, instrument, milestone | Use-of-funds split and the milestone it buys | Specific; instrument choices for tokens go to legal | | Roadmap (optional) | The next milestone with a metric | Three or four phases, current one marked | "1k weekly active wallets on mainnet", not "launch mainnet" | | Tokenomics (optional) | What the token does in the product | Allocation, cliffs, vesting, circulating supply | No returns, yield or fee-share language; see [crypto-pitch-mistakes.md](crypto-pitch-mistakes.md) #4 | | Contact | Name and one link | Email or handle, site, repo, program ID | End here; no extra summary | ## Markup Claim slide (problem, why now, solution, why crypto): ```html
The problem

{{CLAIM}} {{ONE_WORD}}

``` Metrics slide (traction, market): ```html
Traction

{{HEADLINE_METRIC_AS_A_CLAIM}}

{{VALUE}}

{{LABEL}}

Source: {{LINK_OR_QUERY}}
``` Comparison slide (competition): ```html
Competition

{{THE_DIMENSION_YOU_WIN_ON}}

{{CRITERION_1}}{{CRITERION_2}}{{CRITERION_3}}
{{ALTERNATIVE}}✓——
{{PROJECT}}✓✓✓
``` Title and contact slides drop the label and use `

`. Screenshots go in as `…` so the file stays self-contained.