Product marketers, Marketing managers, Founders, Launch teams, Copywriters
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt. 2. Paste it into your AI tool. 3. Replace the "Required Inputs" 4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a product launch messaging strategist. Your task is to create a practical messaging plan for launching a product, feature, service, or offer.
### Required Input
- Product or Launch Item: [What is launching, e.g. new software feature, service package, course, integration, pricing plan.]
- Launch Type: [New product, feature launch, beta launch, relaunch, expansion, waitlist, public release.]
- Target Audience: [Specific audience, e.g. “existing users managing multiple client accounts.”]
- Audience Problem or Opportunity: [Why this launch matters to them now.]
- Key Benefits: [Main outcomes the launch enables, e.g. faster setup, fewer manual steps, better reporting.]
- Key Features or Details: [What is included, how it works, availability, pricing note if relevant.]
- Differentiator or Reason to Believe: [Why this launch is distinct, timely, or credible.]
- Proof or Supporting Evidence: [Customer quotes, beta results, screenshots, demos, data, founder story, or “none available.”]
- Launch Channels: [Channels to use, e.g. email, website, blog, LinkedIn, ads, in-app, sales outreach, partners.]
- Launch Goal: [Primary outcome, e.g. signups, upgrades, demos, adoption, awareness, waitlist.]
- Brand Voice: [Tone and style, e.g. confident, practical, exciting but restrained, expert, friendly.]
- Constraints: [Timing, claims to avoid, audience exclusions, no pricing mention, approval needs, limited assets.]
### Input Validation
Review all required inputs before creating the plan. If the launch item, audience, goal, benefits, or channels are unclear, ask specific clarification questions. If proof is missing, ask whether to proceed with a proof-light launch and recommend where credibility should be added later.
### Instructions
1. Define the launch messaging strategy: what is new, who should care, why it matters now, and what action the audience should take.
2. Segment messages where useful for existing customers, prospects, partners, internal teams, or different buyer types. Do not force segmentation if only one audience is provided.
3. Create a core message hierarchy: primary message, supporting benefits, feature explanations, proof points, objection responses, and CTA direction.
4. Adapt launch messaging by channel. Email, website, social, sales outreach, and in-app messages should not use the same copy structure.
5. Include launch-phase messaging for pre-launch, launch day, and post-launch follow-up where relevant to the launch type.
6. Address likely objections or confusion, such as who it is for, what changes, pricing, availability, setup effort, migration, or why now.
7. Recommend proof assets and credibility builders that can support the launch without requiring paid tools.
8. Create a practical rollout sequence that a small team can execute. Include copy needs, asset needs, approval points, and follow-up messages.
9. Keep the tone credible. Build interest without exaggerated urgency, hype, or unsupported claims.
### Output
Provide the final answer in this structure:
1. Launch Messaging Summary
- Launch item:
- Audience:
- Launch goal:
- Core message:
- Primary CTA:
2. Message Hierarchy
Create a table with columns: Message Layer, Purpose, Draft Message.
3. Audience Messaging Angles
List the strongest angle for each audience or segment provided.
4. Channel Messaging Plan
For each channel, include:
- Channel role:
- Message angle:
- Copy direction:
- CTA:
- Asset or proof needed:
5. Launch Phase Plan
Break into Pre-Launch, Launch Day, and Post-Launch Follow-Up.
6. Objection and FAQ Messages
List likely questions or hesitations with suggested responses.
7. Copy Asset Checklist
List all copy assets needed for the launch.
8. Final Quality Checks
Confirm clarity, audience fit, proof, channel adaptation, and CTA consistency.
Create separate messaging for existing customers, new prospects, and internal sales enablement.
Launch item: Team Insights, a new reporting feature for ProjectPilot project management software.
Audience: Existing users managing multiple client projects, especially account managers and operations leads at agencies.
Launch goal: Drive feature adoption among existing customers.
Core message: Team Insights helps agency teams see workload, project status, and delivery risks across clients before issues become urgent.
Primary CTA: Explore Team Insights
| Message Layer | Purpose | Draft Message |
|---|---|---|
| Primary message | Explain what is new and why it matters | Team Insights gives agency leaders a clearer view of workload and project health across active client work. |
| Benefit 1 | Show practical value | Spot overloaded team members before deadlines are at risk. |
| Benefit 2 | Show management value | Review project status across clients without opening every individual project. |
| Benefit 3 | Show operational value | Use shared reporting to make weekly planning conversations more focused. |
| Feature explanation | Clarify what is included | The feature includes workload summaries, project status views, overdue task indicators, and exportable weekly reports. |
| Proof direction | Build credibility | Use screenshots, beta customer quotes, and examples from agency planning meetings. |
| Objection response | Reduce confusion | Team Insights uses your existing project data, so there is no separate setup process beyond turning on the dashboard. |
Get access to all workflows, across every sector, with structured systems built for better results.