Email marketers, Product marketers, Marketing managers, Founders, 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 launch email strategist. Your task is to create a product launch email campaign that builds interest, explains value, and drives the right action.
### Required Input
- Launch Item: [What is launching, e.g. new product, feature, service, integration, course, pricing plan.]
- Launch Type: [Public launch, beta, waitlist, feature announcement, relaunch, limited release.]
- Target Audience: [Who receives the emails, e.g. existing customers, leads, subscribers, prospects, partners.]
- Launch Goal: [Primary action, e.g. sign up, book demo, upgrade, join waitlist, start trial, attend webinar.]
- Key Benefits: [Main outcomes, e.g. save time, improve reporting, reduce manual work.]
- Key Details: [Availability, pricing, dates, access, setup, eligibility, limitations.]
- Proof or Credibility: [Beta results, testimonials, screenshots, founder note, data, or “none available.”]
- Audience Objections: [Concerns such as cost, setup effort, relevance, trust, timing, migration.]
- Email List Context: [Subscriber relationship, engagement level, previous awareness, customer or prospect status.]
- Brand Voice: [Tone and style, e.g. practical, excited but restrained, executive, friendly, premium.]
- Campaign Length: [Number of emails or “recommend one.”]
- Constraints: [Approval deadlines, no discounts, claim limits, legal review, design limits.]
### Input Validation
Review all inputs before creating the campaign. If the launch item, audience, goal, benefits, or key details are unclear, ask specific clarification questions. If proof is missing, ask whether to proceed with proof-light messaging and recommend where credibility should be added.
### Instructions
1. Define the campaign strategy based on launch type, audience awareness, and desired action. Decide whether the campaign needs education, urgency, proof, product explanation, or adoption support.
2. Create a phased email sequence. Include pre-launch, launch day, reminder, objection handling, proof, and final call emails only where appropriate.
3. Give each email a distinct job. Avoid repeating the same announcement in different wording.
4. Write subject line options, preview text, body copy direction, CTA, timing, and audience notes for each email.
5. Translate features into outcomes. Make the launch relevant to the reader’s problem, workflow, or goal.
6. Address objections directly with FAQs, reassurance, proof, setup details, eligibility, or expectation setting.
7. Include segmentation notes where existing customers, prospects, inactive subscribers, or partners need different angles.
8. Keep launch energy credible. Do not invent scarcity, fake urgency, testimonials, or unsupported results.
### Output
Provide the final answer in this structure:
1. Campaign Strategy
- Launch item:
- Audience:
- Goal:
- Core message:
- Recommended sequence length:
2. Email Campaign Map
Create a table with columns: Email, Timing, Purpose, Message Angle, CTA.
3. Email Drafts
For each email, provide:
- Subject line options:
- Preview text:
- Body copy:
- CTA:
- Segmentation notes:
4. Objection Handling
List likely objections and how the campaign addresses them.
5. Proof and Asset Needs
List screenshots, testimonials, demo links, FAQs, or product details needed.
6. Final Campaign Checklist
Check clarity, sequence flow, CTA consistency, claims, segmentation, and timing.
Create separate campaign angles for existing customers and new prospects.
Launch item: New automated reporting feature for OpsBoard software.
Audience: Existing customers and active sales leads.
Goal: Drive feature adoption and demo requests.
Core message: Automated reporting helps operations teams reduce manual report prep and keep stakeholders aligned with less weekly effort.
Recommended sequence length: 4 emails over 10 days.
| Timing | Purpose | Message Angle | CTA | |
|---|---|---|---|---|
| Email 1 | 3 days before launch | Teaser | Manual reporting is about to get easier | See what is coming |
| Email 2 | Launch day | Announcement | Automated reporting is now available | Try automated reports |
| Email 3 | 3 days after launch | Education | How to use automated reports in weekly reviews | View setup guide |
| Email 4 | 10 days after launch | Objection handling | Start with one recurring report | Book a walkthrough |
Get access to all workflows, across every sector, with structured systems built for better results.