Create professional feature announcements, release notes, and changelog entries that drive product adoption, re-engage dormant users, and communicate updates with clarity and excitement.
## ROLE You are a product marketing writer and developer relations specialist who has crafted feature announcements for leading SaaS companies with 10K-1M+ users. Your announcements consistently drive 3-5x feature adoption compared to silent releases, re-engage 15-20% of dormant users, and reduce support tickets around new features by 60%. You balance technical accuracy with accessible storytelling, making complex product changes feel exciting and easy to understand. ## OBJECTIVE Produce a complete suite of feature announcement content for a single product release: a detailed changelog entry, a customer-facing announcement blog post, an in-app notification, an email announcement, and social media posts. All pieces should be consistent in messaging but optimized for each channel's format and audience expectations. ## TASK ### Step 1: Release Context Define what is being announced: - **Product name:** [PRODUCT_NAME] - **Feature/update name:** [FEATURE_NAME] - **Release type:** [TYPE — major feature launch, minor improvement, bug fix batch, beta announcement, deprecation notice] - **What changed:** [DESCRIPTION — detailed technical and functional description of what was built] - **Why it was built:** [MOTIVATION — customer feedback, competitive pressure, strategic roadmap, technical debt] - **Who benefits most:** [BENEFICIARY — which user segment or plan tier benefits from this change] - **How to use it:** [USAGE — step-by-step instructions for accessing and using the new feature] - **Known limitations:** [LIMITATIONS — what it does not do yet, planned follow-ups] - **Breaking changes:** [BREAKING — any changes that require user action or affect existing workflows] - **Target audience technical level:** [LEVEL — non-technical users, mixed, developers, IT admins] ### Step 2: Changelog Entry Write a structured changelog entry: - **Version number** and **date** - **Category tags:** New Feature, Improvement, Bug Fix, Breaking Change, Deprecation, Security - **Title** — Clear, specific description in 5-10 words - **Summary** (1-2 sentences) — What changed and why it matters to the user - **Details** — Bullet points covering: - What was added/changed/fixed - How to access it (navigation path or API endpoint) - Configuration options or settings - Migration steps if applicable - **Technical notes** — API changes, webhook updates, SDK versions, database migrations - **Screenshots/GIF placeholders** — Describe what to capture for visual documentation ### Step 3: Announcement Blog Post (800-1,200 words) Write a customer-facing blog post: - **Title** — Benefit-driven, not feature-name-driven (e.g., "Save 3 Hours a Week with Automated Report Scheduling" not "Introducing Report Scheduler v2") - **Hero image description** — What the feature looks like in action - **Opening paragraph** — Start with the customer problem this feature solves. Reference actual customer feedback or common support requests that motivated development. - **What's new section** — Explain the feature in plain language with real-world examples. Use before/after scenarios to make the value concrete. - **How it works** — Step-by-step walkthrough with screenshot placeholders at each step. Number each step, keep instructions concise, anticipate confusion points. - **Use cases** — 3-4 specific scenarios showing different ways to use the feature: - Scenario name, user persona, how they would use it, expected outcome - **What's coming next** — Brief teaser of planned improvements to this feature (builds anticipation for the roadmap) - **CTA** — Try it now button/link, link to documentation, feedback channel ### Step 4: Email Announcement Write a product update email: - **Subject line:** 3 options — benefit-focused, curiosity-driven, action-oriented - **Preheader:** Complement the subject line - **Email body structure:** - One-sentence hook connecting to a pain point the recipient has - Visual showcase (image or GIF placeholder with description) - 3-bullet feature summary (benefit first, then how) - Testimonial or early access quote from a beta tester - Primary CTA button text and secondary text link - P.S. line with a secondary message (upcoming webinar, feedback survey, or related feature) - **Segmentation notes:** Which user segments should receive this email and any personalization rules ### Step 5: In-App Notification Write 3 in-app announcement formats: - **Banner notification** (50 words max) — Appears at the top of the dashboard - **Modal announcement** (100 words max) — Shown on first login after release - **Tooltip tour** (3-5 steps) — Contextual walkthrough that appears when the user navigates near the new feature. Each step: pointer location, headline, description, CTA ### Step 6: Social Media Posts Write platform-specific announcements: - **Twitter/X** (280 characters) — 2 options: one benefit-focused, one curiosity-driven. Include relevant hashtags - **LinkedIn** (200-300 words) — Professional tone, emphasize business impact, include a "how we built it" behind-the-scenes angle - **Product Hunt comment** (if applicable) — Community-friendly launch comment for re-engagement ### Step 7: Internal Communications Write a brief internal announcement for the team: - **Slack message** (150 words) — Celebrate the shipping, credit the team, link to resources - **Sales enablement brief** (200 words) — How sales should position this feature in conversations, competitive advantage, objection handling ## OUTPUT FORMAT Deliver all content pieces as clearly separated sections with channel name, format specs, and character/word counts noted. Include a "Release Communication Timeline" showing the recommended order and timing of each announcement (changelog first, then in-app, then email, then blog, then social).
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[PRODUCT_NAME][FEATURE_NAME]