Product managers who need launch documents fast. Copy these prompts into ChatGPT, fill the variables, and get working drafts in seconds instead of staring at blank pages for hours.
These prompts pair well with Jasper AI for Product Management-specific tone control, or Copy.ai for fast iteration.
Pre-Launch Strategy Documents
You are a product marketing manager preparing a competitive positioning brief for an upcoming product launch.
Product: {product_name} Target market: {primary_customer_segment} Main competitor: {biggest_competitor_name} Our key differentiator: {unique_value_proposition} Price point: {pricing_tier: premium / mid-market / budget} Launch timeline: {weeks_until_launch} Internal audience: {leadership_team / product_team / sales_team}
Write a 400-500 word competitive positioning brief. Start with a two-sentence market context. Follow with a direct comparison table showing our strengths vs competitor weaknesses across 4 key dimensions. End with 3 talking points sales can use when prospects mention the competitor. Use data-driven language and avoid marketing fluff.
When to use it: Two weeks before launch when sales keeps asking “how do we beat [competitor]” and you need ammunition for their objection-handling playbook.
Pro tip: Include one unexpected weakness of the competitor that customers wouldn’t think to ask about. This positions you as the expert who knows the market deeply.
You are writing a product launch risk assessment memo for your CEO ahead of a board meeting.
Product: {product_name} Launch date: {specific_launch_date} Revenue target: {q1_revenue_target} Biggest concern: {top_risk_factor} Mitigation already in place: {current_risk_mitigation} Team confidence level: {high / medium / low} Market readiness: {ready / cautious / uncertain}
Write a 300-350 word executive memo. Open with launch readiness status in one sentence. Present the top 3 risks in order of severity with specific mitigation plans for each. Close with a go/no-go recommendation and what you need from leadership. Use executive language - direct, fact-based, solution-oriented.
When to use it: 48 hours before your CEO asks “are we really ready for this launch?” in front of the board, and you need to sound prepared instead of defensive.
Pro tip: Always include one risk that’s already been mitigated to show you’re not just bringing problems - you’re solving them proactively.
You are a product manager writing launch success metrics for your engineering and design teams.
Product: {product_name} Primary success metric: {main_kpi} Secondary metrics: {two_supporting_metrics} Time horizon: {measurement_period} Current baseline: {existing_performance_data} Target improvement: {percentage_or_absolute_target} Team motivation: {celebrate_wins / learn_fast / prove_concept}
Write a 250-300 word team communication. Start with why these specific metrics matter to users, not just business. Explain how each team’s work directly impacts the numbers. Include specific measurement dates and who’s responsible for tracking what. End with what success looks like and how you’ll celebrate hitting targets.
When to use it: Right after you finalize launch metrics but before the team starts asking “how will we know if this actually worked?”
Pro tip: Connect engineering metrics to user behavior, not just system performance. Engineers care more when they see how code changes affect real people.
You are preparing talking points for a launch readiness meeting with customer success and support teams.
Product: {product_name} Expected support volume: {anticipated_ticket_increase} New features customers will ask about: {top_three_new_capabilities} Known limitations: {current_product_constraints} Escalation scenarios: {when_to_escalate_to_product} Documentation status: {help_docs_readiness} Training completed: {team_training_status}
Write a 350-400 word briefing document. Open with launch impact on their daily work. Detail the 3 most likely customer questions with suggested responses. Include specific scenarios when they should loop in product team vs. handle independently. Close with resources available and who to contact for edge cases.
When to use it: The day before launch when support is panicking about handling questions they’ve never seen before, and you need them confident instead of stressed.
Pro tip: Give them one “insider tip” about the product that’s not in public docs. Support teams love having special knowledge that makes them look smart to customers.
You are writing a launch timeline communication for your executive stakeholders.
Product: {product_name} Launch date: {public_launch_date} Pre-launch milestones: {key_deliverables_and_dates} Team dependencies: {critical_path_blockers} Marketing activities: {campaign_timeline_summary} Success checkpoint: {first_measurement_date} Stakeholder role: {what_you_need_from_them}
Write a 200-250 word status update email. Lead with launch date and confidence level. Highlight 3 critical milestones in the next two weeks with owners and dates. Flag any dependencies that need executive attention. End with one specific ask and a deadline for their response. Keep tone professional but urgent.
When to use it: Every Monday morning for the month before launch, when executives need to know you’re on track without having to ask.
Pro tip: Always include what you’re NOT doing to stay on schedule. Executives appreciate seeing you make trade-offs intelligently.
Launch Messaging and Positioning
You are writing a product launch announcement email for existing customers.
Product: {product_name} Customer segment: {target_user_type} Main benefit: {primary_value_proposition} Previous pain point solved: {problem_this_addresses} How to access: {where_to_find_new_feature} Training available: {onboarding_resources} Feedback channel: {how_customers_can_respond} Sender: {your_name_and_title}
Write a 300-350 word customer email. Subject line should create curiosity without being clickbait. Open by acknowledging a pain point they’ve experienced. Explain the new capability in terms of their workflow, not features. Include a clear next step to try it. Close with genuine invitation for feedback and how to reach you.
When to use it: Launch day morning when you need to tell existing customers about the new product without sounding like you’re trying to upsell them.
Pro tip: Mention one specific piece of customer feedback that led to this launch. People love knowing their voice was heard and acted upon.
You are crafting a product positioning statement for your sales team’s discovery calls.
Product: {product_name} Target customer: {ideal_customer_profile} Status quo they’re stuck with: {current_solution_problems} Unique approach: {how_your_solution_differs} Proof point: {key_metric_or_case_study} Competitive advantage: {hard_to_replicate_differentiator} Call to action: {next_step_in_sales_process}
Write a 150-200 word positioning script. Start with a problem statement the prospect will nod to. Position your solution as the alternative approach, not just another vendor. Include one surprising insight about their industry or role. End with a consultative question that gets them talking about their specific situation.
When to use it: Right before your first sales training on the new product, when reps need a confident way to introduce it without sounding like everyone else.
Pro tip: Test the opening problem statement with 3 real prospects first. If they don’t immediately say “yes, that’s exactly our issue,” rewrite it.
You are writing website copy for a product launch landing page focused on conversion.
Product: {product_name} Target visitor: {primary_traffic_source} Main headline benefit: {value_proposition_in_user_terms} Social proof: {customer_testimonial_or_metric} Key features: {top_three_capabilities} Pricing model: {cost_structure} Conversion goal: {sign_up / demo / trial / purchase} Urgency factor: {launch_offer_or_timeline}
Write 400-450 words of landing page copy. Headline should promise a specific outcome in under 10 words. Lead with benefit, not features. Include one customer quote that addresses the main objection. Present features as benefits using “you can” language. Close with clear CTA and one reason to act today.
When to use it: 72 hours before launch when marketing needs final copy for the landing page and you’re the only one who really understands what customers care about.
Pro tip: Write the FAQ section first, then work those objection-handlers into the main copy. It prevents you from overselling features nobody cares about.
You are preparing a product demo script for trade show conversations.
Product: {product_name} Demo duration: {time_limit_in_minutes} Audience level: {technical_expertise} Key workflow: {main_use_case_to_demonstrate} Wow moment: {most_impressive_capability} Common questions: {top_three_prospect_concerns} Next step: {post_demo_call_to_action} Booth setting: {noise_level / screen_size / demo_setup}
Write a 300-350 word demo script. Open with a question that qualifies interest level. Show the workflow from their perspective, not yours. Build to one “wow” moment that gets them to lean in. Handle the most common objection proactively. End with specific next step and timeline. Include natural transition phrases and backup talking points for technical difficulties.
When to use it: The night before a trade show when you’re rehearsing your demo and realize you’ve been talking about features instead of outcomes.
Pro tip: Practice the first 30 seconds until you can do it while distracted. Trade show floors are chaotic and you need a strong hook that works even with interruptions.
You are writing launch PR talking points for media interviews about your new product.
Product: {product_name} Industry context: {market_trend_or_problem} Company angle: {why_you_built_this_now} Unique insight: {contrarian_or_surprising_perspective} Customer impact: {specific_outcome_or_metric} Competitive landscape: {how_market_will_change} Future vision: {where_this_leads_next} Personal story: {why_this_matters_to_you}
Write 350-400 words of interview talking points. Structure as key messages with supporting details. Lead with industry insight that positions you as a thought leader. Connect product launch to bigger market shift. Include one personal anecdote about why this problem matters. Avoid sales language - focus on industry education and thought leadership.
When to use it: Two days before a podcast interview when you want to sound like an industry expert, not just someone hawking their latest product.
Pro tip: Prepare one contrarian take on a common industry belief. Journalists love quotes that challenge conventional wisdom and make their articles more interesting.
Internal Launch Communication
You are writing a launch day email for your entire company.
Product: {product_name} Launch significance: {revenue_impact / strategic_importance} Team effort: {key_contributors_by_department} Customer reaction: {early_feedback_or_metrics} Employee pride points: {why_team_should_be_excited} What happens next: {immediate_next_steps} How to help: {ways_employees_can_support} Celebration planned: {recognition_or_event}
Write a 250-300 word company-wide email. Subject should build pride, not just announce. Open with significance to company mission. Recognize specific teams and individuals by name. Share one early customer reaction or metric. Explain how different departments can contribute to launch success. Close with celebration details and thanks.
When to use it: Launch day afternoon when you want the whole company to feel ownership of the success instead of just knowing something shipped.
Pro tip: Include one behind-the-scenes story about overcoming a challenge. People love hearing how teams pulled together to make something happen.
You are preparing a launch retrospective agenda for your core product team.
Product: {product_name} Time since launch: {weeks_or_months_post_launch} Key metrics: {actual_vs_target_performance} Biggest surprise: {unexpected_outcome_positive_or_negative} Team feedback themes: {common_feedback_from_team} Process gaps: {what_we_missed_or_did_poorly} Next launch date: {upcoming_product_timeline} Meeting duration: {available_time_for_retrospective}
Write a 200-250 word retrospective agenda with specific discussion questions. Start with wins and metrics review. Address one major surprise and what it teaches us. Include process improvement section with actionable next steps. End with commitments for next launch. Format as numbered agenda items with time allocations and discussion prompts.
When to use it: Six weeks after launch when the dust has settled and you need to capture lessons learned before everyone forgets and moves on to the next thing.
Pro tip: Send a brief pre-work survey asking each team member for their biggest learning. You’ll get more honest feedback than in a live meeting where people edit themselves.
You are writing a product launch case study for your company’s internal knowledge base.
Product: {product_name} Launch timeline: {from_concept_to_market} Key decisions: {critical_choices_that_shaped_outcome} Results achieved: {metrics_vs_targets} Budget spent: {resources_invested} Lessons learned: {what_worked_and_what_didnt} Team structure: {roles_and_responsibilities} Replicable process: {what_future_teams_can_copy}
Write a 450-500 word internal case study. Structure as: situation, approach, results, lessons. Focus on decision-making process and trade-offs, not just outcomes. Include specific metrics and timeline details. Highlight what future product teams can apply to their launches. Be honest about mistakes and near-misses.
When to use it: Three months after launch when you’re documenting learnings for the next product team who will ask “how did you guys launch so successfully?”
Pro tip: Interview 2-3 team members from different functions before writing. You’ll catch important details you missed and different perspectives on what mattered most.
You are creating a launch readiness checklist email for your cross-functional team leads.
Product: {product_name} Launch date: {target_launch_date} Department leads: {names_and_functions} Critical dependencies: {must_have_deliverables} Risk factors: {potential_blockers} Go_no_go meeting: {decision_meeting_date} Escalation process: {who_to_contact_for_issues} Success metrics: {how_readiness_is_measured}
Write a 300-350 word checklist email with clear action items. Address each functional lead by name with specific deliverables. Include deadlines and definition of “done” for each item. Flag interdependencies between teams. Provide escalation path for blockers. End with go/no-go meeting details and what you need from each person.
When to use it: Two weeks before launch when you need every team lead to confirm their readiness instead of assuming everything is on track.
Pro tip: Include one buffer item for each team - something that can be dropped if they’re running behind. It gives you flexibility without compromising core launch requirements.
You are writing a post-launch team recognition message for your executive leadership.
Product: {product_name} Launch results: {key_metrics_and_outcomes} Team performance: {standout_contributions} Challenges overcome: {major_obstacles_resolved} Individual recognition: {specific_people_and_achievements} Organizational impact: {business_value_delivered} Future implications: {what_this_enables_next} Recognition requested: {how_leadership_should_acknowledge_team}
Write a 350-400 word recognition memo. Open with launch success summary and business impact. Highlight specific individuals and their contributions with details. Describe challenges the team overcame that leadership might not know about. Close with request for specific recognition and why the team deserves it.
When to use it: One week after successful launch when you want to make sure your team gets proper credit from leadership, not just a generic “good job everyone” email.
Pro tip: Include one story about someone going above and beyond that executives wouldn’t know about. Leaders love specific examples they can reference when they see those team members.
Post-Launch Analysis and Optimization
You are writing a 30-day post-launch performance report for your product stakeholders.
Product: {product_name} Launch goals: {original_success_metrics} Actual results: {performance_against_targets} User adoption: {signup_usage_engagement_metrics} Unexpected findings: {surprising_positive_or_negative_results} Customer feedback themes: {common_user_responses} Revenue impact: {financial_performance} Next actions: {what_youre_changing_based_on_data}
Write a 400-450 word performance report. Lead with headline results vs. targets. Break down performance by key metrics with context for why numbers matter. Include one major surprise and what it means. Present customer feedback themes with specific quotes. End with 3 concrete actions based on learnings and timeline for implementation.
When to use it: Exactly 30 days after launch when stakeholders are asking “how did we do?” and you need to show both results and learning-driven next steps.
Pro tip: Include one metric that’s performing better than expected and explain why. It shows you understand your product’s impact beyond just hitting original targets.
You are creating a customer feedback summary for your engineering team based on post-launch user responses.
Product: {product_name} Feedback volume: {number_of_responses_collected} Collection method: {surveys_interviews_support_tickets} Top praise: {what_users_love_most} Main complaints: {biggest_user_pain_points} Feature requests: {most_common_enhancement_asks} Technical issues: {bugs_or_performance_problems} Engineering priorities: {what_needs_technical_attention}
Write a 300-350 word engineering-focused feedback summary. Start with overall user sentiment and volume. Present technical feedback in order of user impact, not frequency. Include specific user quotes about performance and usability. Translate feature requests into technical requirements. End with recommended engineering priorities based on user pain vs. development effort.
When to use it: Six weeks after launch when engineering is asking what to work on next and you have real user data to guide technical priorities.
Pro tip: Group similar feedback themes and show the volume for each. Engineers respond better to “47% of users mentioned speed issues” than “some people think it’s slow.”
You are writing a competitive response strategy after observing how competitors reacted to your product launch.
Product: {product_name} Competitor responses: {how_competitors_have_reacted} Market impact: {shifts_in_competitive_landscape} Customer confusion: {mixed_messages_in_market} Our advantages: {strengths_competitors_cant_match} Vulnerability areas: {where_competitors_might_attack} Response timeline: {how_quickly_we_need_to_act} Stakeholder audience: {who_needs_this_strategy}
Write a 350-400 word competitive response strategy. Open with competitor reaction summary and market impact. Analyze their likely next moves based on their responses. Identify our defensible advantages and vulnerability areas. Recommend specific actions to maintain competitive edge. Include timeline and resource requirements for proposed responses.
When to use it: Two months after launch when competitors have had time to respond and you need to plan your next competitive moves based on market reactions.
Pro tip: Focus on what competitors can’t easily copy rather than just feature advantages. Sustainable competitive advantages come from capabilities, not features.
You are preparing a product iteration roadmap presentation based on post-launch learnings.
Product: {product_name} Launch learnings: {key_insights_from_real_users} Usage patterns: {how_people_actually_use_product} Drop-off points: {where_users_struggle_or_leave} Success stories: {ideal_user_workflows} Technical debt: {performance_or_scalability_issues} Resource constraints: {team_bandwidth_limitations} Business priorities: {revenue_or_strategic_focus_areas}
Write a 400-450 word roadmap presentation outline. Structure as: learnings, implications, priorities, timeline. Connect user behavior data to specific product improvements. Prioritize changes by user impact and development effort. Include resource requirements and dependencies. Present as quarterly milestones with measurable outcomes for each iteration.
When to use it: Quarter-end planning when you need to present data-driven product improvements based on real user behavior, not assumptions.
Pro tip: Lead with user behavior insights that surprised you. It shows you’re making decisions based on real data, not just building more features.
You are writing a launch process improvement memo for future product releases.
Product: {product_name} Launch timeline: {actual_vs_planned_timeline} Process gaps: {what_slowed_us_down_or_created_issues} Communication breakdowns: {where_information_flow_failed} Resource conflicts: {team_bandwidth_or_priority_conflicts} Success factors: {what_worked_well_to_replicate} Recommended changes: {specific_process_improvements} Next launch timeline: {when_recommendations_get_tested}
Write a 350-400 word process improvement memo. Start with timeline analysis and major gaps identified. Detail specific communication or coordination failures with examples. Highlight successful practices to maintain. Present concrete process changes with rationale and implementation steps. End with success metrics for improved launch process.
When to use it: End of quarter when you’re documenting lessons learned for the next product team, so they don’t repeat your mistakes.
Pro tip: Interview team leads from each function before writing. You’ll discover process issues you didn’t see from the product management perspective.
Frequently Asked Questions
How do I customize these ChatGPT prompts for different product types?
Replace the generic variables with specific details about your product category. For B2B software, emphasize ROI and integration concerns. For consumer products, focus on user experience and emotional benefits. The prompt structure works for any product - the variables make it relevant.
What’s the best way to use these prompts if I’m launching multiple products simultaneously?
Run each prompt separately for each product rather than trying to combine them. The specificity is what makes these prompts effective. You can batch similar documents across products, but maintain distinct messaging and positioning for each launch.
How can I make these AI-generated documents sound more like my company’s voice?
Add a tone variable like {company_voice: formal / conversational / technical} to any prompt, or include a sentence like “Write in the style of {example_company_communication}” with a link to existing content that captures your preferred tone and style.