Investor Pitch Mechanics
Category: Concepts Source: Pitch deck feedback notes (April 1, 2026) Last updated: 2026-04-06
Overview
On April 1, 2026 — the day of the Agentdex launch — Jack logged a structured set of notes titled “Pitch deck feedback notes (Problem/Solution, Team, Market, Mechanics).” These appear to be distilled learnings from a VC review session or a Granola founder playlist. The notes were cleaned and rated “AI Summarized” confidence.
Summary
“Notes on investor pitch mechanics: quantify customer pain + research; map solution directly to pain; place team slide early; keep market sizing logic simple; business model should be comparable + include unit economics; avoid live demos; keep slides visual; leave time for Q&A; be authentic about unknowns.”
The Mechanics
Problem/Solution
- Quantify the customer pain — don’t just describe it, put a number on it
- Map your solution directly to the pain — one-to-one correspondence
- Research your customers deeply before the pitch
Team Slide
- Place it early — after problem/solution, not at the end
- Explicitly address experience gaps — don’t hide them
- VCs invest in people first; the team slide earns permission for everything after
Market
- Keep market sizing logic simple — TAM/SAM/SOM but don’t over-engineer it
- Be comparable — reference known companies that have addressed adjacent markets
Business Model
- Include unit economics — not just revenue model but CAC, LTV, margin
- Be comparable — reference business model archetypes investors already understand
Mechanics
- Avoid live demos — pre-record instead (live demos fail; Murphy’s Law)
- Keep slides visual, minimal text — investors read fast
- Leave time for Q&A — don’t fill all 20 minutes with slides
- Be authentic about unknowns — saying “we don’t know yet but here’s how we’ll find out” is more credible than fake certainty
Timing
- 3–5 minutes: story (narrative hook)
- 15 minutes: deck
- 10 minutes: Q&A
Decisions Made
“Avoid live demos; pre-record instead; keep slides visual with minimal text; place team slide early (after problem/solution); explicitly address experience gaps.”
The explicit “address experience gaps” decision is interesting — Jack and the team are young, without traditional startup credentials. Rather than hoping investors don’t notice, they’re planning to name it directly and counter-program it.
Related
Revision history
| Date | Commit | Edit summary |
|---|---|---|
| 2026-04-06 06:43:54 | 5ebe9165 | build: auto-update 2026-04-06 06:43 UTC (112 pages) |
| 2026-04-06 06:38:25 | 83d226b5 | build: auto-update 2026-04-06 06:38 UTC (110 pages) |
| 2026-04-06 05:04:20 | c3410fe8 | expand: books section (4 pages), projects (4 pages), fitness (3 pages), dreams (3 pages), concepts (3 new pages), nav updated to show all 9 sections |