Launch Announcement

You are a Product Marketing Manager creating launch messaging for [Product/Feature Name] launching on [Launch Date].

Create coordinated messaging across channels:

## CORE MESSAGING

### Value Proposition (One-liner)
[Compelling statement of value in <10 words]

### Elevator Pitch (30 seconds)
[2-3 sentences explaining what, for whom, and why it matters]

### Three Key Benefits
1. **Benefit 1:** [Feature] enables [outcome]
2. **Benefit 2:** [Feature] enables [outcome]
3. **Benefit 3:** [Feature] enables [outcome]

## EMAIL ANNOUNCEMENT

**Subject Line:** [Compelling, action-oriented, <50 characters]

**Body:**
Hi [Name],

[Hook - problem or opportunity statement]

[Introduction of solution with key benefit]

[2-3 bullet points of capabilities]

[Social proof or early results if available]

[Clear CTA with link]

[Sign-off]

## SLACK/TEAMS MESSAGE

@here Exciting news! 
[One sentence announcement]

**What's new:**
• [Benefit 1 in user terms]
• [Benefit 2 in user terms]
• [Benefit 3 in user terms]

**Get started:** [Link or simple instruction]
**Learn more:** [Documentation link]
**Questions?** [Support channel]

## SOCIAL MEDIA

### Twitter/X Thread
1/ [Announcement with emoji hook]

2/ [Problem this solves]

3/ [Key capability 1]

4/ [Key capability 2]

5/ [Customer quote or result]

6/ [CTA with link]

### LinkedIn Post
[Professional announcement paragraph]

Key capabilities:
- [Capability 1]
- [Capability 2]
- [Capability 3]

[Results or impact statement]

[CTA and link]

## IN-APP NOTIFICATION

**Title:** [Feature name or benefit]
**Message:** [One sentence description]
**CTA Button:** [Action verb + benefit]
**Learn More:** [Link to guide]

## SEGMENT-SPECIFIC MESSAGING

### For Power Users
[Technical capabilities and advanced features]

### For New Users
[Simple benefits and easy getting started]

### For Admins
[Control, security, and management features]

## SUCCESS METRICS
- Email open rate target: [X%]
- Click-through rate target: [X%]
- Feature adoption target: [X% in Y days]
- Social engagement target: [X interactions]

Ensure consistent tone while adapting length and detail for each channel.

## 🔍 Web Search Enhancement

**Leverage current web data to strengthen this analysis:**

1. **Search Priority Areas**
   - Recent market trends and industry reports (last 12 months)
   - Competitor updates, product launches, and strategic moves
   - Current pricing models and market positioning
   - Regulatory changes and compliance requirements
   - Customer sentiment and review data
   - Technology trends affecting this space

2. **Data Requirements**
   - Cite all sources with [Source Name, Date] format
   - Prioritize data from the last 6 months; flag anything older than 12 months
   - Distinguish between direct quotes, data points, and your interpretations
   - When multiple sources conflict, present both viewpoints with context

3. **Search Integration**
   - First, gather relevant web data before beginning analysis
   - Validate key assumptions against current market realities
   - Update any outdated benchmarks or statistics
   - Cross-reference claims with multiple authoritative sources

4. **Output Formatting**
   - Mark web-sourced facts with 🔍 indicator
   - Include a "Data Sources" section at the end with full citations
   - Highlight any data gaps where current information wasn't available
   - Separate factual findings from strategic recommendations

**Note**: If specific data cannot be found, explicitly state this rather than using outdated or assumed information.

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."