Plan a product launch and go-to-market
Launch messaging, audiences, channels, timeline, and success metrics.
The prompt
Role: Act as a product marketer leading the go-to-market for a launch.
Context: What is launching and why now: [LAUNCH_WHAT_WHY]. Target audiences and their current alternative: [AUDIENCES_ALT]. Top 3 benefits with proof: [BENEFITS_PROOF]. Positioning vs competitors: [POSITIONING]. Launch tier / ambition: [TIER]. Date and constraints: [DATE_CONSTRAINTS]. Sales and channel context: [SALES_CONTEXT].
Goal: Give the launch team one aligned story and a clear plan so messaging, sales and channels all say the same thing on day one.
Task: Produce: (1) the launch narrative (problem, shift, our answer, why believe, call to action); (2) messaging by audience (headline, 3 talking points, one-liner); (3) an objection/FAQ set; (4) a GTM brief: channels and their role, asset checklist with owners, internal enablement needs, timeline milestones, and the success metrics (leading and lagging).
Constraints: Benefits must map to the proof I gave; flag any that do not. Keep the narrative under 250 words. No competitive claims that need Legal review without flagging them. Asset list must fit the launch tier.
Examples: Narrative shape: 'Today [problem]. That's because [old way]. [Product] changes it by [shift]. It works because [proof]. [CTA].' Message-by-audience row: 'Audience | Headline | 3 points | One-liner.'
Format: Sections: Launch narrative | Messaging by audience (table) | Objections/FAQ | GTM brief (channels / assets / enablement / timeline / metrics). ~900 words.
Verification: List every claim needing Legal, Security or benchmark verification before launch.
Validation: Test the narrative on someone outside the product team: can they retell it in two sentences? If not, simplify the shift.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Marketing & Brand prompts
What to fill in
- LAUNCH_WHAT_WHY
- AUDIENCES_ALT
- BENEFITS_PROOF
- POSITIONING
- TIER
- DATE_CONSTRAINTS
- SALES_CONTEXT
- problem
- old way
- Product
- shift
- proof
- CTA
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Create a lead magnet people wantIdeas and an outline for a checklist, guide, template, or tool that attracts the right leads.
- Plan an account-based marketing program for target accountsAn ABM plan with account selection, tiers, buying-committee messaging, coordinated plays, and measurement.
- Plan a co-marketing campaign with a partner companyA joint campaign plan with shared goals, roles, lead-sharing rules, and a launch timeline both companies agree to.
- Write a campaign brief and channel planA campaign brief with objective, audience, message, channels, timeline, and measurement.