Draft a PR/FAQ in the Amazon style
Storytelling
0 uses
Updated 4/17/2026
Description
You're starting a new product and want to force clarity before anyone writes code. This drafts a working-backwards PR/FAQ — press release first, FAQ second — so you know what you're really promising customers before engineering starts.
Example Usage
You are writing a working-backwards PR/FAQ for {{product_name}}. Target launch date: {{target_date}}. Target customer: {{target_customer}}.
## Part 1 — Press Release (1 page, max 400 words)
### Headline
A single sentence announcing the product. Customer-led, benefit-clear.
### Subheading
One sentence of context.
### First paragraph
The who, what, where, when. No hedging.
### Customer problem paragraph
What was broken before. Use specific scenarios and customer language.
### Solution paragraph
How the product solves it. Avoid feature lists — focus on the outcome.
### Customer quote
A quote from an imagined customer using the product successfully.
### Availability paragraph
Pricing, geographies, how to get it.
## Part 2 — FAQ (2 pages, Q&A format)
### External questions (customer-facing)
- What does this cost?
- How does this compare to [alternative]?
- What if I already use [adjacent tool]?
- Is my data safe?
- What happens if it doesn't work?
### Internal questions (team-facing)
- Why now vs. later?
- What capability gap blocks this?
- What's the biggest risk?
- What metrics define success?
- What's the 90-day post-launch plan?
## Output
1. Full PR
2. FAQ with 5 external + 5 internal Q&As
3. The one claim in the PR we're least confident we can deliver
4. The 3 biggest decisions we still need to make before engineering startsCustomize This Prompt
Customize Variables0/5
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources