Finally — your brilliant idea.
You’ve scoped the market. You’ve tagged your core team. Now: what exactly are you building, and why does it matter now?
This is your clearest articulation of belief — before validation, before data, before traction. It’s the raw WHAT and WHY behind everything you’re about to do.
Make it clear. Make it bold. Make it real — enough to pull others in.
Purpose
- State the problem in human terms (who hurts, where, how often).
- Paint the vision — the better world if you succeed (outcome, not features).
- Surface the unique insight (timing shift, angle, wedge) that gives you an unfair shot.
- Create a one‑slide story founders, teammates, and advisors can rally around.
When to Complete
- Before writing a product spec or committing to an MVP scope.
- Before recruiting early believers (first hires, advisors, pilot customers).
- Before you ask anyone for money or time beyond friends‑and‑family curiosity.
Proof Sections
Problem
- What pain, inefficiency, or broken behavior are you targeting?
- Who feels it most (user/buyer), and where’s the friction line today?
- B2B SaaS: “Ops managers at mid‑market warehouses lose hours reconciling shipments across four systems.”
- B2C CPG: “Parents want truly low‑sugar lunch snacks; labels hide sugars and options are overpriced.”
- Services: “Independent restaurants bleed margin to delivery apps and can’t reach direct customers.”
Solution (Concept‑Level)
- Outcome, not features: what changes for the user if this works?
- What stays the same (critical constraints) and what goes away (pain)?
- B2B SaaS: “Single screen to reconcile inbound/outbound in minutes, not hours — with audit trail.”
- B2C CPG: “Affordable, genuinely low‑sugar snack that kids like and parents trust.”
- Services: “Local delivery collective that drops fees, keeps data, and boosts repeat orders.”
Unique Insight
- Why now? What do you see in behavior/regulation/tech/channel that others miss?
- What’s your wedge into the first segment?
- B2B SaaS: “Retailers standardizing EDI finally make SMB warehouse data clean enough to automate.”
- B2C CPG: “GLP‑1 culture shifted taste toward low‑sweetness; kids’ aisle hasn’t caught up.”
- Services: “Dense clusters of restaurants along new bike lanes enable 15‑minute delivery at low cost.”
Optional: Technology Hypothesis
- If tech is the enabler, state the simple claim you’ll test (no wiring diagrams).
- B2B SaaS: “Off‑the‑shelf LLM + rules engine can auto‑match 90% of discrepant shipments.”
- B2C CPG: “Allulose/monk‑fruit blend hits ‘sweet enough’ with low glycemic impact at target COGS.”
- Services: “Open‑source routing + shared courier pool can beat third‑party costs by 20%.”
Execution Requirements
- One‑sentence Problem Statement (who/where/how painful).
- Two‑to‑three sentence Vision/Outcome (life after your solution).
- One‑sentence Unique Insight/Wedge (why you win first).
- 3–5 testable assumptions tied to early interviews or pilots.
Domain Adaptability: Universal
Same questions across domains; the answers differ in language and constraints.
- SaaS: quantify workflow minutes saved, data sources, compliance.
- CPG: target consumer segment, taste/price thresholds, retail leverage.
- Services: local density, unit economics, repeat behavior & referrals.
Expected Output
- 1–2 paragraphs (Problem → Outcome → Insight).
- Optional tech note (one line) or a brief PR‑FAQ/one‑pager link.
- A vision one‑liner you could read aloud on slide 1.
Linked Asset
View
Edit
Optional Enhancements (Pro‑Level Execution)
- Vision Poster — headline, subhead, outcome image, one‑liner.
- PR‑FAQ (Amazon‑style) — press release + five brutal FAQs.
- Problem Tree — symptom → root cause → measurable outcomes.
- Tenets — 5–7 non‑negotiable product principles to steer tradeoffs.