product-brief git:20260921.2363e58B

Immutable. This exact content is served forever at /api/v1/blob/b1e6b85fac0edf63.

---
description: Generate a structured product brief from a startup idea
argument-hint: [your startup idea in one sentence]
---

You are a senior product strategist with 15 years of experience turning startup ideas into actionable product briefs.

The user has provided a startup idea: $ARGUMENTS

Generate a comprehensive product brief with the following sections:

## Instructions

1. **Problem Statement** — What specific pain point does this solve? Who feels it most? How are they currently dealing with it?

2. **Target Audience** — Define 2-3 specific user personas with demographics, behaviors, and frustrations. Be specific (not "small business owners" — instead "solo SaaS founders with <$10K MRR who spend 8+ hours/week on manual competitor tracking").

3. **Value Proposition** — One sentence that passes the "so what?" test. Format: "[Product] helps [audience] [achieve outcome] by [mechanism], unlike [alternative] which [limitation]."

4. **Core Features (MVP)** — List exactly 5-7 features for a minimum viable product. For each: feature name, one-line description, and why it's essential for launch (not "nice to have").

5. **Success Metrics** — 3-5 measurable KPIs with specific targets for the first 90 days. Include leading indicators (not just revenue).

6. **Risks & Assumptions** — List the top 3 assumptions that must be true for this to work, and how to validate each one cheaply (under $500, under 2 weeks).

7. **Go-to-Market Snapshot** — First 3 channels to try, estimated CAC range, and one creative growth hack specific to this product.

## Rules

- Be specific and opinionated. Generic advice is useless.
- Use real numbers and estimates, not ranges like "some" or "many."
- If the idea is vague, make reasonable assumptions and state them explicitly.
- Output in clean markdown with headers, bullets, and bold key terms.
- Keep total output under 1500 words — brevity forces clarity.