MarketingProduct Marketingintermediate 45 min saved

Feature Release Announcement Pack

Create a complete, evidence-aware feature launch pack for email, social, sales, and support.

Customise & copy

Add the context you have. The prompt updates as you work.

Feature description and capabilities *

Describe what the feature does, its main capabilities, availability limitations, and any setup requirements.

Target customer segment *

Name the customer group or user role this launch is intended for.

Launch date and time zone *

Provide the public launch date, time, and time zone.

Primary value proposition or benefit *

State the main customer benefit in concrete terms without unsupported performance claims.

Live prompt

4 fields

Create a complete feature release announcement pack using only the information provided below. Do not ask questions, invent testimonials, add social proof, or claim unsupported capabilities. Avoid hype openers and politeness padding. Write clear, specific copy that is usable after one light edit.

Feature description and capabilities: {{feature_description}}
Target customer segment: {{target_customer_segment}}
Launch date and time zone: {{launch_date_timezone}}
Primary value proposition or benefit: {{primary_value_proposition}}

Return exactly these four labeled sections:

1. CUSTOMER EMAIL
Include a subject line, preview text, and an email body ready to send. State what is launching, who it is for, the primary benefit, key capabilities supported by the feature description, and the launch date and time zone. Include a clear call to action without inventing a link; use [CTA LINK] only if a link is needed.

2. SOCIAL MEDIA POST
Write one post of no more than 280 characters. Include the feature name or a concise description, the primary benefit, target customer relevance, and launch timing. Do not use unsupported claims, hashtags, emojis, or hype language.

3. SALES TALKING POINTS
Provide concise bullet points covering the customer problem, what the feature does, the primary benefit, who should care, launch timing, and one objection-handling point based only on the provided information. Do not invent pricing, results, integrations, or customer evidence.

4. SUPPORT ONE-SHEET
Include: feature summary, eligible users or target segment, launch timing, supported capabilities, how to get started, and troubleshooting steps. Make troubleshooting practical and conservative. Use only known facts; where feature-specific details are unavailable, provide general checks such as confirming launch availability, access permissions, supported configuration, and contacting the appropriate support channel without inventing channel details. Clearly label any item that requires confirmation before publication.

Proof before you use it

A real example

Tested on gpt-5.6-luna on 2026-09-10

{
  "feature_description": "The clinic scheduling platform now supports automated waitlist matching. When an earlier appointment becomes available, the system identifies eligible patients based on appointment type and sends staff a review notification. Staff must confirm the replacement before the appointment is changed.",
  "launch_date_timezone": "October 7, 2025 at 7:00 AM Eastern Time",
  "target_customer_segment": "Operations managers at multi-location outpatient clinics",
  "primary_value_proposition": "Reduces manual waitlist coordination while keeping staff in control of appointment changes."
}

A small ritual that works

How to use it

01Enter the feature description and supported capabilities.
02Specify the target customer segment.
03Add the launch date, time, and time zone.
04State the primary customer benefit.

Why it works

The prompt defines a complete launch-communications package with four clearly separated deliverables: customer email, social post, sales talking points, and support one-sheet. It supplies four focused inputs covering the feature, audience, timing, and primary benefit, then limits the content to those facts. Specific guardrails reduce unsupported additions by prohibiting invented testimonials, pricing, integrations, results, social proof, and links. The required labels and content checklists give each section a distinct purpose, while the support section includes conservative guidance for details that are not available.

Where it fails

The prompt is constrained by the information provided in its four variables. If the feature description does not explain setup, availability, supported capabilities, or access requirements, the resulting launch materials must remain general and mark certain details for confirmation. The fixed four-section format also leaves limited room for additional audiences, channels, FAQs, localization, or product-specific implementation guidance. The 280-character social post limit can force prioritization when the feature, benefit, audience, and launch timing all need to be included.

Customisation tips

Make the feature description concrete: include the feature name, supported actions, eligible users, availability limits, setup requirements, notification methods, and important exclusions. State the target segment using the role, team type, or account characteristic that should guide the messaging. Provide the launch date, time, and time zone in a publication-ready format. Write the primary benefit as a specific customer outcome without adding performance claims. If the support one-sheet needs exact navigation, permissions, escalation routes, or configuration steps, include those facts in the feature description so they can be used instead of generic guidance. Adjust the section requirements if you need additional channels, localization, legal language, or a different social-post length.

Watch-outs

The prompt permits only information supplied in the variables, so important product facts omitted from the inputs cannot be safely filled in.
The call to action may need a real destination added later because the prompt uses [CTA LINK] when a link is required.
Generic support checks are intentionally conservative and may not replace confirmed product documentation.
Items marked as requiring confirmation should be verified before publication, especially exact setup steps, permission requirements, support channels, and troubleshooting details.

Works in

Product marketingFeature launchesGo-to-market planningLaunch enablement

Was this useful?

Submit your variation

If your version helps, it may be published with your name and a link back to you.

Want to make AI useful across your team? Explore Atul's training.