A product launch press release written in the Amazon PR/FAQ format forces product managers to describe the product from the customer's perspective before a single line of code is written — making it one of the most effective tools for validating that you are building the right thing and communicating it clearly when you ship.
The press release format is powerful for two reasons. First, it forces clarity: if you can't explain the product's customer benefit in a press release headline, the benefit is unclear. Second, it creates alignment: a shared press release eliminates ambiguity about what's being built and why.
This guide covers both how to write a launch press release and how to use the PR/FAQ format as a product planning tool.
The Amazon PR/FAQ Format
Amazon requires product teams to write a press release and FAQ before starting development. This is the PR/FAQ format:
- Headline: The product benefit in one sentence, written as if a journalist wrote it
- Subheadline: The who and what in one or two sentences
- Summary paragraph: 3-4 sentences covering what the product does and who it's for
- Problem paragraph: What problem does this solve? Who has it? How painful is it today?
- Solution paragraph: How does the product solve the problem? What does it let you do that you couldn't do before?
- Customer quote: What would a real customer say about this? (Not a testimonial — a realistic reaction)
- Call to action: What do you want readers to do?
- FAQ: 5-10 questions customers or press would ask, answered honestly
According to Lenny Rachitsky's writing on product planning, the PR/FAQ format is the most efficient alignment tool available to product teams — it surfaces disagreements about what the product does, who it's for, and why it matters before any engineering investment is made, when the cost of misalignment is lowest.
Section 1 — The Headline
H3: Headline Rules
- Name the customer benefit, not the feature: "Sales teams close 30% more deals" not "New AI-powered CRM features"
- Be specific: Numbers work. "30% more deals" is more compelling than "close more deals."
- Write it as a journalist would: Would this appear in TechCrunch? Would a customer share it?
Bad headline: "Acme Inc. Launches New Dashboard Update" Good headline: "Sales Reps at Acme Customers Save 3 Hours Per Week With Automated Pipeline Reports"
Section 2 — The Problem and Solution
H3: Problem Paragraph
The problem paragraph should make the reader nod in recognition. Use the language of the customer, not the language of the product team.
Bad: "Legacy CRM systems suffer from poor data integration and sub-optimal workflow automation." Good: "Every Monday morning, sales managers at mid-size companies spend two hours pulling together pipeline data from three different tools before they can answer their CEO's weekly pipeline question."
H3: Solution Paragraph
Describe what the customer can now do, not how the technology works.
Bad: "Our AI model processes structured and unstructured data using natural language processing to generate pipeline summaries." Good: "With Acme's new pipeline summary tool, you ask a question in plain English and get an accurate pipeline report in 30 seconds — no spreadsheets, no data team, no Monday morning scramble."
According to Shreyas Doshi on Lenny's Podcast, the solution paragraph is where most product press releases fail — teams describe the technology instead of the customer outcome. The test is whether a customer could read the solution paragraph and immediately understand what they can do that they couldn't do before.
Section 3 — The Customer Quote
The customer quote is not a real testimonial — it's what you wish a customer would say. Write it in the voice of your target customer.
H3: Customer Quote Rules
- Specific outcome, not vague praise: "I gave back three hours every Monday" not "It's amazing."
- Target persona voice: Write it in the language your customer actually uses
- Believable: If no customer would actually say this, rewrite it
Bad: "This product is revolutionary and has transformed our business." Good: "I used to dread Mondays because the CEO's pipeline question took half my morning to answer. Now I have the report ready in two minutes."
Section 4 — The FAQ
H3: Types of Questions to Include
- Customer questions: What does it cost? How long does it take to set up? Does it work with [common integration]?
- Skepticism questions: Why should I believe this saves 3 hours? Is my data secure?
- Competitive questions: How is this different from [competitor]?
- Edge case questions: What happens if [unusual scenario]?
Honest answers to skepticism questions build more credibility than marketing-speak answers. If you don't have a good answer, that's a product gap.
According to Gibson Biddle on Lenny's Podcast, the FAQ section of a PR/FAQ document is where product weaknesses surface — when the team can't honestly answer a skepticism question, they've identified a product gap that needs to be addressed before launch.
Using the PR/FAQ as a Planning Tool
H3: The Working Backwards Method
- Write the press release before building anything
- Share with product, engineering, design, marketing, and sales
- Surface disagreements about what the product does and who it's for
- Resolve disagreements in the document, not in the product
- Use the approved document as the product brief
According to Annie Pearl on Lenny's Podcast discussing product planning, the working backwards method using press releases is the fastest alignment tool she used — it converts abstract product discussions into concrete customer outcomes and exposes assumptions that would otherwise surface as expensive misalignments after the product ships.
FAQ
Q: What is a product launch press release? A: A document written in the format of a press announcement that describes the customer benefit of a new product or feature, the problem it solves, and a realistic customer quote — used both for external distribution and as an internal product planning alignment tool.
Q: What is the Amazon PR/FAQ format? A: A product planning tool requiring teams to write a press release and FAQ before building — covering headline, problem, solution, customer quote, and 5-10 honest questions from customers or press to surface misalignments before development starts.
Q: What should a product launch press release headline include? A: The customer benefit, not the feature name. Written as if a journalist is reporting on customer outcomes, specific enough to include measurable results, and compelling enough that a customer would share it.
Q: How do you write a customer quote for a product press release? A: Write the quote in the voice of your target persona describing a specific outcome, not vague praise. The quote should be what you hope a real customer would say after experiencing the product's core value.
Q: When should you write a product press release? A: Before building, as a planning tool, to align the team on customer benefit and surface assumptions early. Then revise and distribute externally at launch with real customer quotes and specific metrics.
HowTo: Write a Product Launch Press Release
- Write the headline as a customer benefit statement rather than a feature announcement — it should name a specific, measurable outcome your target customer cares about
- Write the problem paragraph in customer language describing the exact situation that creates the pain without using technical or product team jargon
- Write the solution paragraph describing what the customer can now do rather than how the technology works
- Write a realistic customer quote in the voice of your target persona describing a specific outcome they achieved not vague praise
- Write 5 to 10 FAQ answers including honest responses to skepticism questions that surface product gaps requiring attention before launch
- Use the PR/FAQ internally before building to surface team disagreements about what the product does and who it is for