Product Launch Blog Announcement Writer

Write a product launch blog post for the following: Product name: {&{PRODUCT_NAME}} What it does (one sentence): {&{PRODUCT_DESCRIPTION}} Customer pain it solves: {&{CUSTOMER_PAIN}} Target customer persona: {&{CUSTOMER_PERSONA}} Top 3 features/capabilities: {&{KEY_FEATURES}} Origin story (why you built it): {&{ORIGIN_STORY}} Beta user quote (raw or approximate): {&{BETA_USER_QUOTE}} Specific use case scenario: {&{USE_CASE_SCENARIO}} CTA/offer: {&{CTA_OFFER}} (e.g., free 14-day trial, free plan, waitlist) Tone: {&{TONE}} (e.g., earnest and direct, developer-casual, polished startup) **Build the launch post in this structure:** 1. **Title Options (3 variants)**: - One that leads with the customer pain - One that leads with what becomes possible - One that leads with the origin story angle 2. **Opening Scene** (80–100 words): Start in the customer's world, not the product's. Describe the pain with specificity — a concrete scenario, a real cost, a recognizable frustration. 3. **The Problem Depth** (100–130 words): Expand on why this problem has persisted. What workarounds have people been using? Why have they been insufficient? 4. **Origin Story** (80–100 words): Why did you build this? Make it personal and specific — not "we noticed a gap in the market." What specific moment made you realize this had to exist? 5. **Feature-as-Solution Sections** (150–200 words per feature): For each of the 3 features: - Name the feature - Describe it in plain language - Immediately follow with "Which means you can now [specific capability]" - One concrete example of the feature in action 6. **The Beta User Voice** (60–80 words): Present the beta user quote in context. Who is this person? What were they doing before? Format the quote as a pull-quote. 7. **Use Case Scenario** (120–150 words): Walk through a specific day-in-the-life scenario using the product. Named persona, specific context, concrete outcome. 8. **Availability & CTA** (60–80 words): State clearly: who can use this, when, at what price point. One specific CTA with a clear description of what happens next. **Anti-patterns:** - Do NOT lead with "Today, we're excited to announce..." - Do NOT describe features without customer benefit consequences - Do NOT use superlatives: "best", "revolutionary", "game-changing"