| 1 | --- |
| 2 | style_id: investor-pitch |
| 3 | kind: style |
| 4 | summary: Fundraising narrative method that carries an investor from why now to why this team, on evidence rather than adjectives. |
| 5 | keywords: [fundraising, pitch, startup, traction, investor] |
| 6 | --- |
| 7 | |
| 8 | # Investor Pitch — Style Specification |
| 9 | |
| 10 | > Method and design defaults only. No project communication contract, brand identity, page structure, or SVG prototypes. |
| 11 | |
| 12 | ## I. Style Overview |
| 13 | |
| 14 | | Property | Value | |
| 15 | |---|---| |
| 16 | | Style Name | Investor Pitch | |
| 17 | | Best Fit | Fundraising decks, investor meetings, demo days, partner and board pitches, and internal venture funding requests | |
| 18 | | Reusable Intent | Give an investor the shortest honest path to a decision — the opportunity, the evidence that it is being captured, and what the money buys — with every claim survivable in diligence | |
| 19 | | Sources | Authored in-repo as a bundled reference Style, 2026-08-07; distilled from fundraising-presentation practice, not a single external document | |
| 20 | |
| 21 | ## II. Communication Method |
| 22 | |
| 23 | - **Preferred Mode**: narrative |
| 24 | - **Argument Flow**: Open on the change in the world that makes this possible now, name the problem it creates and who feels it, show the solution and the evidence that it is working, then widen to the market it can reach, how it makes money, who is building it, and what this round buys. Adapt weight to the stage: early rounds are carried by insight and team, later rounds by traction and unit economics. Never bury the thing that is actually strongest. |
| 25 | - **Page Message Discipline**: Give each page one claim and put the evidence for it in view. Write the title as the claim itself, not as a section label, so the deck reads correctly when forwarded without a presenter. Keep a metric and its definition on the same page, and never let one page carry two arguments an investor must weigh separately. |
| 26 | - **Claim Discipline**: Keep achieved, contracted, in-pipeline, and projected clearly and visually distinct, and never let a projection borrow the credibility of a result. Define every metric where it first appears and keep that definition fixed for the whole deck. State the basis for any market size and show the derivation, name the real competitors and where they win, and present the risks the team is taking on rather than a diligence-proof story with no exposure. A claim that would not survive diligence is removed, not softened. |
| 27 | |
| 28 | ## III. Page Role Vocabulary |
| 29 | |
| 30 | | Role | Communication Job | Evidence Obligation | Composition Tendency | |
| 31 | |---|---|---|---| |
| 32 | | Why now | Establish the change that makes this newly possible | Point to a real shift — technology, regulation, cost curve, behavior — with evidence | One dominant statement or figure; this page sets the frame for everything after | |
| 33 | | Problem | Make the pain specific and expensive | Quantify who suffers it and what it costs them today; name the current workaround | Keep one concrete situation dominant rather than a category description | |
| 34 | | Solution | Show what was built and why it resolves the problem | Show the actual product or mechanism, not a description of intent | Let the artifact hold the page; keep explanation to one line | |
| 35 | | Product evidence | Prove it exists and works | Show real interface, output, or deployment; disclose anything staged | Full-frame artifact with minimal chrome around it | |
| 36 | | Traction | Establish that the market is responding | Show the honest curve with its axis definitions and cohort basis, not a cropped window | Let the trend dominate and mark the inflection with its cause | |
| 37 | | Business model | Explain how value converts to revenue | State pricing, unit economics, and payback with the assumptions they rest on | Keep one revenue mechanism primary; show the arithmetic rather than asserting margin | |
| 38 | | Market opportunity | Size the reachable prize | Derive bottom-up from customers and price; state assumptions and reachable share | Show the derivation, not a nested set of large circles | |
| 39 | | Competition | Position honestly against real alternatives | Include the incumbent and the status quo; state where alternatives genuinely win | Compare on axes that actually decide purchases, never on a self-serving two-axis frame | |
| 40 | | Go-to-market | Show how customers are reached repeatedly | Give channel evidence with cost and conversion where known | Keep the repeatable motion primary over a list of untested channels | |
| 41 | | Team | Establish why these people win this | Give specific relevant history and the earned insight, not title inflation | A few people at real prominence; avoid logo walls standing in for experience | |
| 42 | | Financials and plan | Show the trajectory and what drives it | Tie projections to named drivers and current rates; keep assumptions visible | Keep the driver arithmetic legible rather than presenting a polished output | |
| 43 | | The ask | State what is being raised and what it buys | Give amount, use of funds, milestones it reaches, and resulting runway | One page, unmistakable; never leave the ask implied | |
| 44 | | Diligence appendix | Hold the detail a serious investor asks for | Retain cohorts, definitions, contracts, pipeline, and methodology | High density, organized for retrieval during questions | |
| 45 | |
| 46 | ## IV. Evidence & Data Expression |
| 47 | |
| 48 | - **Argument Trace**: Every claim traces to something verifiable in diligence — a measured metric with its definition, a signed contract, a working product, a named customer, or a cited source. Anything that traces to none of these is cut. Where evidence is thin, the deck says which claims are still hypothesis rather than presenting them at equal confidence. |
| 49 | - **Charts**: Show the full available history rather than the flattering window, keep axes unbroken and starting at zero for magnitude claims, label the metric definition on the chart, and mark where a definition or scope changed. Distinguish actual from projected visually within any series that carries both. Never present a cumulative curve where the periodic rate is what matters, and never let chart choice hide a decline. |
| 50 | - **Tables**: Use tables for cohorts, unit economics, pricing, and use of funds. Keep one row shape, show the arithmetic that produces derived figures, state period and currency, and mark estimated or unaudited entries explicitly. |
| 51 | - **Sources**: Attribute market data, benchmarks, and third-party figures with source and date on the page where they appear. Give internal metrics their definition, measurement period, and system of record. Name a customer only with permission, and label pilots, letters of intent, and pipeline as what they are rather than as revenue. |
| 52 | - **Native Editability**: Prefer editable native charts and tables for traction, cohort, and financial data — these numbers change between meetings and must be refreshable without rebuilding the page. Keep product screenshots and deployment photographs as images. |
| 53 | |
| 54 | ## V. Visual System Defaults |
| 55 | |
| 56 | - **Preferred Visual Style**: dark-tech |
| 57 | - **Composition**: One claim per page with one dominant element carrying it. Fix a consistent position for the claim line so a reader scanning the forwarded deck moves quickly. Reserve full-frame treatment for product and traction pages, and keep the ask and team pages simple enough to be absorbed in seconds. |
| 58 | - **Density**: Sparse in the main arc, dense only in the appendix. A pitch page should be readable in the time an investor gives it — a few seconds on a screen, not a study session. Move every supporting detail behind the appendix boundary rather than compressing it into the narrative. |
| 59 | - **Decoration**: Restrained. Let product imagery, one strong number per page, and typography carry the deck. Avoid gradient meshes, glow, floating three-dimensional devices, stock-photo collages, and the ornamental infographic vocabulary that signals effort rather than substance. The default field is dark and modern; open it to a lighter, warmer register when the venture is consumer or lifestyle rather than technical. |
| 60 | - **Color Behavior**: Commit to a small range with one accent reserved for evidence — the traction curve, the decisive number, the ask. Keep that accent rare so it stays a signal, and never use a semantic status color decoratively. Ensure any color that distinguishes actual from projected also differs in shape or texture. Any confirmed Brand or Deck identity replaces these tendencies. |
| 61 | - **Typography Character**: Use a confident modern sans-serif with a large statement scale for claims and numbers, tabular figures wherever metrics align in columns, and a quiet scale for definitions and attribution. Keep number formatting, currency, and period notation identical throughout. Exact families remain current-project or resolved identity decisions. |
| 62 | |
| 63 | ## VI. Image & Icon Direction |
| 64 | |
| 65 | - **Preferred Image Rendering**: corporate-photo |
| 66 | - **Image Usage**: Lead with real artifacts — the product in use, actual deployments, genuine customers, the team. Use market or context imagery only at the opening beat. Never use stock imagery of anonymous professionals or abstract technology to fill a page that lacks evidence. |
| 67 | - **Image Treatment**: Crop product captures to what carries the claim and keep their text legible on a laptop screen, since most reading happens there rather than in the room. Apply consistent framing across the deck, use a real scrim where text sits over an image, and caption what to notice. Avoid mockups implying capabilities that do not exist, distorted aspect ratios, and synthetic text inside generated images. |
| 68 | - **Icon Treatment**: Use one coherent icon family at consistent weight, only to mark a recurring class such as channel, segment, or milestone. Avoid customer and investor logo walls used as evidence without context, icon rows substituting for a feature list, and mixed icon languages on one page. |
| 69 | |
| 70 | ## VII. Review Focus |
| 71 | <!-- visual-review-trigger: explicit-user-only --> |
| 72 | > Apply this section only after the user explicitly activates visual review. It never triggers that stage. |
| 73 | |
| 74 | - Each page's claim is identifiable without a presenter, since the deck will be forwarded. |
| 75 | - Achieved, contracted, pipeline, and projected values remain visually distinct wherever they appear together. |
| 76 | - Traction charts show the full available history with unbroken axes and a stated metric definition. |
| 77 | - Every metric carries its definition and measurement period on the page where it appears. |
| 78 | - Market sizing shows its derivation rather than asserting a total. |
| 79 | - Product imagery and its embedded text remain legible on a laptop screen. |
| 80 | - The ask states amount, use of funds, and the milestones it reaches, on one unmistakable page. |
| 81 | - Appendix density does not leak into the narrative arc. |
| 82 |