Draft a working-backwards press release and FAQ
Write an Amazon-style press release and hard FAQ to clarify customer value and address tough technical questions before writing code.
You getHeading, summary Paragraph and problem and Solution Sections
Prompt
Act as a principal product manager applying the working-backwards methodology. Using the raw product idea provided below, write an internal press release and a customer/stakeholder FAQ.
Rules:
- Write the press release from the future launch date, focusing entirely on customer value and customer quotes rather than internal implementation details.
- Avoid promotional jargon and hype; state clearly what the product does, who benefits, and why existing alternatives failed.
- The FAQ must tackle genuinely difficult questions: pricing models, edge cases, technical trade-offs, and operational bottlenecks.
- Ensure the content strictly reflects the input without fabricating unmentioned company certifications or partners.
Output format:
- Heading (Future launch date, location, headline, sub-headline)
- Summary Paragraph (what is launching, for whom, and primary outcome)
- Problem and Solution Sections (customer pain, status quo failure, product mechanism)
- Internal Leader Quote and Customer Quote
- External FAQ (3 hard customer questions with direct answers)
- Internal FAQ (3 hard operational/engineering questions with direct answers)
My product notes are below:Example output
Paste this prompt into ChatGPT, Claude or Gemini along with your product pitch, notes, or concept outline. Afterwards, ask the model to review the FAQ for any unaddressed pricing or compliance risks.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write a Customer Interview Script That Validates a Problem with Past-Behavior Questions
Get a 30-minute problem-discovery interview script with past-behavior questions, two follow-up probes each, banned-question rewrites and evidence signals.
Score beta readiness for general availability release
Evaluate qualitative feedback, bug logs, and usage stats to decide if a beta is ready for general availability. Use this to make unbiased release decisions.
Analyze customer feedback using Jobs to Be Done
Extract functional, emotional, and social customer drivers from raw user feedback. Use this to separate true user motivations from reactionary feature requests.
Transform Customer Interview Transcripts into Ranked Pain-Point Matrix
Turn raw interview notes into a structured matrix that ranks customer pain points by frequency and business impact to guide your product roadmap.
Extract win and loss drivers from CRM notes
Turn raw CRM deal records into actionable product, pricing, and sales execution patterns. Use it to prepare roadmap reviews and board updates.
Reframe a feature request into a core user problem
Break down prescriptive feature requests into underlying user motivations, workflow bottlenecks, and testable problem statements.
- Draft Multi-Tier SaaS Product Packaging and Feature Matrix
- Define Feature Non-Goals and Scope Boundaries
- Draft a Zero-to-One Product Discovery Experiment Card
- Prioritize a Feature Backlog Using the Kano Model
- Build a Competitor Feature Comparison and Positioning Summary
- Prioritize Your Feature Backlog with RICE Scoring and Flagged Weak Assumptions