At Concept, no one expects a bulletproof risk matrix or a scale-ready ops plan — but they do expect you to know what could break early, and how you’re testing to avoid it. Show that you see the sharp edges, and that your plan to grow is realistic, not reckless.
Investors trust founders who name the scary stuff — and show they’re already poking at it.
Purpose
- Surface the biggest early risks across tech, adoption, funding, or market behavior.
- Show you’re already running small tests to reduce uncertainty.
- Clarify what scaling depends on — and where it could break.
- Signal maturity by balancing ambition with control.
When to Complete
- Alongside Financials & Funding, before pitching advisors or seed investors.
- Before committing capital that assumes smooth scaling.
- Before you risk “premature scaling” (burning money before fit).
Proof Sections
Key Risks You See
- What could kill this idea early? Be blunt.
- B2B SaaS: “If we can’t onboard users in <10 minutes, adoption collapses.”
- B2C CPG: “If unit cost doesn’t drop 30% at scale, we can’t hit retail pricing.”
- Services: “If training isn’t standardized, delivery quality fails beyond 5 clients.”
Early Mitigation Plans
- What are you testing now to de-risk?
- B2B SaaS: Running onboarding pilots via Loom to measure drop-off.
- B2C CPG: Trial runs with 2 co-packers to validate production consistency.
- Services: Documenting SOPs during early pilots to train replacements.
Scalability Dependencies
- What does growth hinge on, and what breaks if it’s too fast?
- B2B SaaS: Cloud costs, support load, developer bandwidth.
- B2C CPG: Packaging supply, shelf-life, retailer terms.
- Services: Hiring pipeline, training time, QA overhead.
Roadmap to Controlled Growth
- How will you pace expansion so you don’t implode?
- B2B SaaS: Cap pilots at 100 users while measuring infra + support.
- B2C CPG: Limit launch to 3 regional retailers before chasing nationals.
- Services: Expand city-by-city with max 10 clients per trainer until QA proves consistent.
Founder Reflection (Optional)
- What’s the risk that keeps you up at night — and how are you designing around it?
- “If churn spikes above 20%, we don’t survive. So we’re building a proactive retention playbook before scaling sales.”
Execution Requirements
- 1–2 sentences on Key Risks.
- 2–3 sentences on Early Mitigation Plans.
- 1–2 sentences on Scalability Dependencies.
- 3–5 bullets on Controlled Growth Guardrails.
Domain Adaptability: Specialized
- SaaS: onboarding friction, infra costs, developer throughput.
- CPG: cost curve, regulatory/label hurdles, shelf-life.
- Services: training consistency, QA, client concentration.
Expected Output
- 1–2 paragraphs (Risks → Mitigation → Scalability Path).
- Optional bullets for dependencies/guardrails.
- Link to a risk map or growth roadmap doc.
Linked Asset
View
Edit
Optional Enhancements (Pro-Level Execution)
- Create a 1-page Risk Map (High / Medium / Low + Mitigation).
- Run a “10× stress test”: what breaks first if demand jumps suddenly?
- Capture regulatory/market barriers (e.g., FDA, GDPR, zoning) early.
- Draft a controlled growth playbook: limits, triggers, and fallback plans.