Investor‑Ready Pitch Appendix: The 1‑Page Research & Metrics Pack to Ship With Every Demo

Treat the appendix as the operational handoff: the page you’d email a contractor or an investor right after the demo so they can run a build or sanity‑check diligence without calling you. Keep it to four panels: market proof (TAM/SAM/SOM), competitor pricing map, WTP signals, and two acceptance tests. Each panel answers a single decision question: Is the market big enough? How will we price? Do customers pay? Can we ship and validate quickly?

Investors care about defensibility and replicability. A bottom‑up TAM rooted in observable filters (addressable customer count × ACV) is far more credible than headline industry totals. A pricing map that shows public prices, observable list prices, and inferred realized prices helps investors and contractors estimate revenue and build implementation plans. Early WTP signals — deposits, Stripe links, pilot commitments — convert “intent” into measurable probability. Finally, short, binary acceptance tests translate product claims into pass/fail criteria contractors can execute.

Skip the ‘1% of a $100B market’ math. Start bottom‑up: list the exact customer segment (e.g., US, mid‑market HR teams, 50–500 employees), find the count from a reputable data source, and multiply by annual contract value (ACV). Present both the top‑down figure (for context) and the bottom‑up derivation — investors expect both and will compare them.

Include the filters you applied and one sensitivity line: a conservative SOM (first 3 years) aligned with your current GTM resources. A credible appendix shows the calculation steps (customer count × penetration × ACV) so an analyst or contractor can reproduce the math in minutes — that reproducibility is what turns a number into evidence.

Design the pricing map as a two‑axis snapshot: vertical axis = price (list / inferred realized), horizontal axis = product sophistication or feature set. Plot public competitors, and annotate each point with the source of the price (website, S-1, job ad mentioning price, or a screenshot). If you infer realized price from public data, show the inference rule (e.g., list price × typical discount).

Include one behavioral datapoint for each competitor where possible: churn cues, trial length, or target ICP. This allows an investor or contractor to estimate likely ACV and implementation complexity quickly — which is what they need to cost build and integration work.

Collect payment‑adjacent signals that require a small commitment: deposit payments, paid pilot commitments with defined scope, pre‑orders through Stripe links, or signed LOIs with minimal non‑binding terms. Report the experiment format, traffic source, conversion rate, and absolute numbers. For example: 42 paid pilot signups from targeted outreach; 3 deposits via Stripe Link from cold demo follow‑ups.

If you don’t have payments yet, run rapid experiments before the demo: landing page + pricing + CTA, a Calendly + prepayment option, or a short paid pilot pipeline. Present the hypothesis, KPI (e.g., deposit conversion), and result. Investors read these numbers as evidence of demand rather than promises.

Include two short, executable acceptance tests on the page so a contractor can scope a first sprint and an investor can see a clear go/no‑go. Suggested tests: (1) Pilot Acceptance Test — deliver the core workflow for a single customer within X weeks and achieve Y outcome (e.g., 80% task completion rate or a signed internal approval). (2) Feature Acceptance Test — implement the paywall and capture a deposit via payment link and record conversion ≥ Z% from demo traffic.

Each test must include the success metric, required inputs (data, integrations), timebox, and owner. Make the tests binary (pass/fail) and constrained — ambiguous acceptance criteria are the fastest path to ignored appendices. These tests convert product claims into developer tickets and pilot scopes.