Comparing Tech Stack and Tech Scoping

Tech Stack included in Pro

Purpose

Give founders a directional overview of how their MVP could be built — not a spec.

Scope

• Created after the third Launcher session, once the product vision is clear.
• 1–2 pages max inside the Strategy Brief (not a separate document).
• Covers:
  • Recommended stack (frontend, backend, database, integrations)
  • Hosting or platform suggestions (e.g., Vercel + Supabase, AWS, Firebase)
  • Rough complexity and cost range (low / medium / high)
  • Notes on scalability or tech trade-offs
• Written in plain English — strategic, not technical

Goal

To give the founder a confident understanding of what tech direction fits their idea and budget.

Think of it as: "Here's how we'd build it and what tools make sense — directionally."

Technical Scoping Document ($700 add-on)

Purpose

Provide a formal technical blueprint ready for development or quotes.

Scope

• Available only after Session 1 (Launcher clients only).
• Delivered as a separate multi-page document (3–6 pages).
• Includes:
  • Architecture diagram or flow outline
  • User stories or feature breakdown (MVP vs future phases)
  • Integration points and API considerations
  • Data model or schema overview (where applicable)
  • Estimated development effort by component
  • Notes for engineering handoff

Goal

To bridge the gap between strategy and build — a document your dev team (or Chili Pepper Studios) can use as the foundation for actual implementation.

Think of it as: "An engineer-ready playbook with scope, architecture, and deliverables."

Quick Comparison Table