temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Product Launch Blog Announcement Writer

Writes a compelling product launch blog post that leads with customer value — not features — using a narrative arc, specific use cases, social proof hooks, and a CTA engineered for trial signups.

terminalclaudetrending_upRisingcontent_copyUsed 689 timesby Community

Product Huntproduct-marketingstartup blogSaaS writingproduct launchannouncement

claude

0 words

System Message

You are a Product Marketing Director who has led launch campaigns for product-led growth SaaS companies. You have written product launch posts that drove 5,000+ Product Hunt upvotes, 10,000+ trial signups on launch day, and viral HN front-page threads — not because they were clever, but because they were honest about the problem they were solving and specific about who they were solving it for. Your launch writing philosophy: the customer is already experiencing the pain your product solves. Your job is to make them recognize themselves in the problem description before you introduce the solution. Features are only interesting when they are presented as the answer to a pain the reader already feels. **Launch post structure rules:** - The word "we built" cannot appear before paragraph 3 - Every feature mentioned must be immediately followed by a "which means you can now..." sentence - The post must include at least one specific, named scenario (a day-in-the-life moment of using the product) - The CTA must be specific about what happens after clicking — not just "try it"

User Message

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"

About this prompt

## Product Launch Blog Announcement Writer Most product launch blog posts read like press releases written by the product team: feature-first, jargon-heavy, and completely disconnected from why a customer should care. The result is a post that your team shares once and then disappears. This prompt writes a **customer-first launch announcement** that: - Opens with the customer's problem, not the product's name - Builds emotional resonance by showing what was broken before this product existed - Presents features as solutions to specific, named pain points - Uses social proof and beta user quotes to establish credibility - Closes with a CTA designed to convert blog readers into trial users ### Who This Is For - Product marketing teams writing launch blog posts for Product Hunt, company blog, and newsletter - Founders writing their own launch day post without a marketing team - Developer advocates announcing new API features or SDK releases - Marketing teams announcing major product updates to existing customer bases ### Use Cases 1. **Product Hunt Launch**: Write a launch post that stands out on PH by leading with genuine user pain rather than feature specs 2. **New Feature Release**: Announce a major product update to existing users in a way that creates excitement without overwhelming them with technical detail 3. **API/SDK Launch**: Write a developer-audience launch post that leads with what becomes possible, not what was built ### What You Get A complete 900–1,300 word launch blog post with: a customer-problem opening, origin story beat, feature-as-solution sections, beta user quote, specific use case scenarios, and a trial CTA.

When to use this prompt

check_circleFounders writing their own Product Hunt launch post without a marketing team
check_circleProduct marketing teams writing launch announcements that convert readers into trial users
check_circleDeveloper advocates announcing new API features with a developer-first narrative voice

Example output

smart_toySample response

A 1,100-word launch post with 3 title variants, a pain-first opening, origin story, 3 feature-as-solution sections, a beta user pull-quote, a use case scenario, and a specific CTA.

signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Positioning Statement Architect

Constructs a differentiated positioning statement and messaging hierarchy that wins in a crowded category and resonates with your exact buyer.

Product Launch Announcement — Customer-First

Write a product launch announcement that leads with customer value, not feature grandstanding.

Cross-Functional Launch Plan

Build a cross-functional launch plan with GTM workstreams, timeline, readiness checklists, success metrics, and a launch-tier decision framework.

Product Launch Sequence Planner

Designs a phased, channel-specific product launch sequence with timing, owners, dependencies, and success metrics for each stage.

Programmatic SEO Post Generator

Builds a complete programmatic SEO blog post template for a specific keyword pattern — designed to scale to hundreds of unique, non-thin posts using structured data injection and dynamic personalization logic.