# PR/FAQ: {Product name}

> Status: DRAFT — working-backwards document, not a spec.
> Author: {role} · Date: {date} · Imagined launch date: {launch-date}

## Press release

**{Headline: product name + customer benefit in one sentence}**

*{Sub-headline: the key detail the headline compressed}*

{CITY} — {launch-date} — {Problem paragraph: the customer's current pain, in their words. What do they do today, and where does it hurt?}

{Solution paragraph: what the product does, and the mechanism that makes it different from what the customer uses today.}

"{Leadership quote: one sentence naming the strategic rationale}," said {role, e.g. "the VP of Product"}.

"{Customer quote: a named persona describing a concrete before/after moment}," said {persona name, role at company-type}.

{Call to action: what the customer does next to get started.}

## Adoption hypothesis

- **First-success event:** {the one customer action that proves first value — behavioral, observable within a session}
- **Repeat-value behavior:** {what brings the customer back after first success}

## Customer FAQ

<!-- 3–5 questions a real buyer asks before switching. At least one answer concedes a trade-off. -->

**Q: How is this different from {what they use today}?**
A: {honest answer, mechanism not category}

**Q: What does it cost / what's the switching cost?**
A: {…}

**Q: {reliability / data / privacy question}**
A: {answer that concedes the real trade-off}

## Internal FAQ

**Q: What's the riskiest assumption, and how do we test it first?**
A: {the belief that kills the product if wrong} → {the cheapest test}

**Q: What's the hardest technical/operational problem?**
A: {…, and why we believe it's solvable}

**Q: How do the first 10 customers concretely arrive?**
A: {named path, not "marketing"}

**Q: What's the success metric?**
A: {a count of the first-success event, with a target and timeframe}

**Q: What would make us kill this?**
A: {a named condition}

## Hand-off

- Idea survives → `prd-draft` (requirements) or `business-case` (the investment ask)
- Riskiest assumption unproven → design its test before anything else