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

[Mention a group only if appropriate for this channel.]
[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/ [Plain announcement of what is available]

2/ [Problem this solves]

3/ [Key capability 1]

4/ [Key capability 2]

5/ [Verified customer quote or result, if available]

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 research, when available
- Search for facts relevant to this task, such as current prices, product capabilities, market data, or applicable requirements.
- Prefer primary sources. Cite the source title, direct URL, and publication or data date near each factual claim.
- Match source recency to the claim. Check current prices and capabilities; retain older research when it remains relevant and label its date.
- Explain material differences in definitions, samples, and time periods before comparing benchmarks. Report conflicting evidence and access limits.
- Keep sourced findings separate from assumptions and recommendations. Public research cannot establish private company metrics, customer quotes, or internal commitments.
- If browsing is unavailable or a fact cannot be verified, say so. Do not invent sources or imply a search was completed.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.