For Marketing Managers launching products this week who need announcement copy fast. These 25 prompts generate finished launch emails, press releases, social campaigns, and internal communications you can edit lightly and send.
These prompts pair well with Jasper AI for Marketing Managers-specific tone control, or Copy.ai for fast iteration.
Launch Email Campaigns
You are writing a product launch announcement email to existing customers.
Product: {product_name} Launch date: {launch_date} Key benefit: {primary_customer_benefit} Price: {price_or_pricing_model} Target audience: {existing_customer_segment} Competitive advantage: {what_makes_this_different} Call to action: {specific_action_you_want} Email tone: {professional / excited / exclusive / urgent}
Write a 250 to 350 word launch email with subject line. Open with the benefit, not the product name. Include one customer pain point this solves. Add social proof or credential in the middle. Close with clear next steps and create urgency around {launch_date}. Include a single, specific call-to-action button.
When to use it: Tuesday morning when your launch email needs to go to your email marketing team by end of day.
Pro tip: If your product solves multiple problems, pick the one that costs customers the most money or time. Generic “productivity” benefits get ignored.
You are writing a product launch email to prospects who downloaded a lead magnet but haven’t purchased.
Product: {product_name} Lead magnet they downloaded: {guide_or_resource_name} Days since download: {time_elapsed} Product connection: {how_product_relates_to_lead_magnet} Launch offer: {discount_or_bonus} Offer deadline: {deadline_date} Main objection: {price / timing / trust / need} Success metric: {specific_result_customers_get}
Write a 300 to 400 word launch email connecting their {guide_or_resource_name} download to {product_name}. Reference their download in the opening line. Address {main_objection} directly in paragraph two. Include one specific customer result using {success_metric}. Close with {launch_offer} and deadline urgency.
When to use it: When you need to activate leads sitting in your CRM during a product launch week.
Pro tip: Mention the lead magnet title in the subject line. “About that [Guide Name] you downloaded” gets higher opens than generic launch announcements.
You are writing a VIP early access launch email to your highest value customers.
Product: {product_name} VIP segment: {top_customers / subscribers / past_buyers} Early access window: {how_many_hours_or_days} Regular launch date: {public_launch_date} VIP-only benefit: {exclusive_bonus / discount / feature} Product category: {software / course / service / physical} Personal connection: {founder_name_or_team_story} Anticipated demand: {limited_quantity / high_demand / waitlist}
Write a 200 to 300 word VIP launch email that feels personal and exclusive. Open with appreciation for their loyalty. Reveal {product_name} as an exclusive preview. Emphasize the {early_access_window} advantage over general launch on {public_launch_date}. Include {personal_connection} to make it feel insider access, not mass marketing.
When to use it: 24-48 hours before your main launch when you want to reward top customers and create early momentum.
Pro tip: Send VIP emails from the founder’s personal email address, not your general marketing email. It increases the exclusivity factor and reply rates.
You are writing a product launch email to customers who bought a related product 6+ months ago.
Previous product: {product_they_bought} Purchase timeframe: {when_they_bought_it} New product: {new_product_name} Progression story: {how_new_product_builds_on_old} Implementation assumption: {assume_they_used_previous_product} Next level result: {advanced_outcome_new_product_delivers} Bundle offer: {discount_for_existing_customers} Case study: {customer_who_used_both_products}
Write a 350 to 450 word launch email positioning {new_product_name} as their next step after {previous_product}. Assume they’ve implemented and gotten results from {previous_product}. Focus on {next_level_result} rather than repeating basic benefits. Include {case_study} as proof of progression. Present {bundle_offer} as recognition of their loyalty.
When to use it: When launching complementary products to customers who bought your entry-level or foundational product last quarter or earlier.
Pro tip: Segment by actual usage data if you have it, not just purchase data. Customers who never used the first product need different messaging.
You are writing a launch announcement email to trial users whose free trial expires soon.
Product: {saas_or_service_name} Trial expiration: {days_remaining} Trial usage data: {features_they_used_most} Upgrade path: {paid_plan_name} Price: {monthly_or_annual_cost} Usage milestone: {progress_they_made_in_trial} Risk of stopping: {what_they_lose_without_upgrade} Onboarding incentive: {bonus_for_upgrading_now}
Write a 250 to 350 word upgrade email tied to the new product launch. Reference their {usage_milestone} from the trial. Connect their trial activity to {new_features_in_launch}. Create urgency around both trial expiration in {days_remaining} and launch pricing. Position upgrade as continuing momentum, not starting over.
When to use it: When your product launch includes new features that trial users haven’t seen yet, typically 2-3 days before trials expire.
Pro tip: Reference their specific usage data in the subject line: “Your 47 reports expire in 3 days” works better than “Your trial expires soon.”
Press Release and Media Outreach
You are writing a press release for a B2B software product launch.
Product: {software_name} Company: {company_name} Industry problem: {specific_problem_this_solves} Target market: {job_titles_and_company_sizes} Key differentiator: {unique_technology_or_approach} Founding story: {why_founders_built_this} Early customer: {notable_beta_customer} Funding status: {bootstrapped / seed / series_a / etc} Availability: {when_and_where_to_get_it}
Write a 400 to 500 word press release following AP style. Lead with the industry problem and market size. Position {software_name} as the solution with {key_differentiator}. Include one quote from founder about {founding_story} and one quote from {early_customer} about results. End with company boilerplate and availability details.
When to use it: Monday morning when you need press release copy for your PR agency or media outreach by Wednesday.
Pro tip: Lead with the problem size, not your solution. “73% of logistics companies struggle with X” gets more journalist attention than “Company Y launches new software.”
You are writing a media pitch email to a tech journalist who covers your industry.
Journalist name: {reporter_name} Publication: {media_outlet} Recent article: {article_they_wrote_recently} Product: {your_product_name} News angle: {why_this_is_newsworthy_now} Exclusive offer: {data / interview / early_access} Industry trend: {broader_trend_this_connects_to} CEO availability: {interview_availability} Supporting data: {market_research_or_customer_data}
Write a 150 to 200 word pitch email to {reporter_name} at {publication}. Reference {recent_article} in opening. Connect {product} to {industry_trend} they cover. Lead with {news_angle}, not product features. Offer {exclusive_offer} and {CEO_availability} for interview. Include one compelling {supporting_data} point.
When to use it: When you need personalized media pitches for your product launch press campaign, typically 1-2 weeks before launch.
Pro tip: Pitch the trend story, not the product story. Journalists want to write about industry shifts, with your product as one example.
You are writing an industry analyst briefing email about your product launch.
Analyst name: {analyst_name} Research firm: {gartner / forrester / idc / etc} Market category: {category_they_cover} Your market position: {startup / established / category_leader} Product innovation: {technical_or_business_model_innovation} Market validation: {customers / revenue / partnerships} Competitive landscape: {how_you_fit_vs_incumbents} Briefing goal: {inclusion_in_report / market_education / relationship} Meeting preference: {call / demo / in_person}
Write a 200 to 300 word analyst briefing request email. Position your launch within {market_category} evolution. Emphasize {product_innovation} and {market_validation} as briefing value. Reference their recent research if relevant. Request 30-minute {meeting_preference} to discuss market implications, not just product demo.
When to use it: 3-4 weeks before major product launches when you want analyst coverage or market category inclusion.
Pro tip: Analysts care about market dynamics, not product features. Frame your briefing as “market education” about where the category is heading.
You are writing a launch announcement for a company blog post that will be shared on social media.
Product: {product_name} Development timeline: {how_long_you_built_this} Customer research: {interviews / surveys / feedback_that_shaped_it} Problem validation: {data_showing_problem_size} Solution approach: {your_unique_methodology} Beta results: {early_customer_outcomes} Team story: {who_built_this} Next steps: {how_readers_can_get_involved} Social sharing angle: {why_people_will_share_this}
Write a 500 to 600 word blog post announcing {product_name} launch. Structure as a story: problem discovery, solution development, early results. Include {customer_research} and {beta_results} as proof points. Make {team_story} personal and relatable. End with clear {next_steps} for different reader types. Write for social sharing with natural quote-worthy lines.
When to use it: Week of launch when you need cornerstone content for your blog that marketing can adapt for social, email, and other channels.
Pro tip: Write 2-3 sentences that work as standalone social media quotes. Journalists and customers often pull quotes from launch blog posts.
You are writing a product launch announcement for LinkedIn targeting B2B decision makers.
Product: {b2b_product_name} Your role: {ceo / founder / product_manager} Problem story: {client_situation_that_inspired_this} Development insight: {surprising_thing_you_learned_building_it} Early adopter: {company_or_person_using_it} Industry impact: {how_this_changes_current_approaches} Personal stake: {why_this_matters_to_you_personally} Professional ask: {what_you_want_from_your_network} Comment prompt: {question_to_drive_engagement}
Write a 200 to 250 word LinkedIn post from your personal account. Open with {problem_story} as a narrative hook. Share {development_insight} as behind-the-scenes value. Mention {early_adopter} for credibility. Connect to broader {industry_impact}. Include {personal_stake} to humanize. End with {professional_ask} and {comment_prompt} to drive engagement.
When to use it: Launch day morning when you want organic reach through your professional network before paid promotion kicks in.
Pro tip: Post at 8 AM Tuesday-Thursday for maximum B2B engagement. Avoid launch announcements on Mondays when everyone’s catching up.
Social Media Campaign Content
You are creating a product launch social media campaign across multiple platforms.
Product: {product_name} Launch date: {specific_date} Target audience: {demographic_and_psychographic} Key benefit: {main_value_proposition} Visual element: {product_demo / behind_scenes / customer_stories} Hashtag strategy: {branded_hashtag} Platform priority: {instagram / linkedin / twitter / tiktok} Campaign duration: {days_or_weeks} Engagement goal: {shares / comments / signups}
Create a 7-day social media campaign calendar with 2-3 posts per day across {platform_priority}. Day 1-2: teaser content, Day 3-4: behind-the-scenes, Day 5: launch announcement, Day 6-7: customer stories and social proof. Include captions of 50-150 words, {hashtag_strategy}, and {visual_element} descriptions for each post.
When to use it: Two weeks before launch when you need a complete social campaign mapped out for your social media manager or agency.
Pro tip: Create platform-native content, don’t just resize the same post. LinkedIn posts should sound professional, Instagram should be visual-first, Twitter should be conversational.
You are writing social media captions for product launch countdown posts.
Product: {product_name} Days until launch: {countdown_number} Sneak peek element: {feature / benefit / behind_scenes} Audience pain point: {problem_this_solves} Team member: {person_to_feature} User generated content: {customer_quote_or_story} Call to action: {follow / sign_up / set_reminder} Tone: {playful / professional / urgent / educational} Platform: {instagram / twitter / linkedin}
Write 5 countdown post captions for {platform} counting down from {countdown_number} days. Each post should reveal {sneak_peek_element} while maintaining anticipation. Mix problem-focused posts with solution hints. Include {team_member} story in one post and {user_generated_content} in another. Match {tone} and include {call_to_action} in each.
When to use it: When you need a week’s worth of countdown content for your product launch social media campaign.
Pro tip: Make countdown posts valuable standalone content, not just “X days left” announcements. Each post should teach something or entertain.
You are creating launch day social media content for maximum reach and engagement.
Product: {product_name} Launch moment: {time_launched} Celebration element: {team_photo / milestone / customer_reaction} Immediate benefit: {what_people_get_today} Limited time offer: {launch_day_special} Share incentive: {reason_people_should_repost} Founder quote: {personal_message_from_leader} Next 24 hours: {what_happens_after_launch} Engagement ask: {specific_action_for_followers}
Write launch day social media content package: announcement post (100-150 words), celebration post with {celebration_element}, founder message featuring {founder_quote}, and engagement post asking for {engagement_ask}. Include {share_incentive} and {limited_time_offer} across posts. Create urgency around {next_24_hours}.
When to use it: Launch day morning when you need coordinated social content across all accounts and team members.
Pro tip: Pin your main launch announcement post and reply to every comment within the first 2 hours. Early engagement signals to algorithms that your content is worth showing to more people.
You are writing social media posts to handle product launch day problems or delays.
Issue: {server_overload / shipping_delay / technical_problem} Affected customers: {who_is_impacted} Timeline: {when_problem_started} Resolution plan: {what_you_are_doing} Estimated fix: {when_it_will_be_resolved} Compensation: {refund / credit / bonus_for_inconvenience} Team accountability: {who_is_taking_responsibility} Updates frequency: {how_often_you_will_communicate} Alternative action: {what_customers_can_do_meanwhile}
Write crisis communication social media posts: immediate acknowledgment (50 words), detailed explanation (100-150 words), and resolution update (75 words). Take full responsibility, explain {resolution_plan}, offer {compensation}, and commit to {updates_frequency}. Maintain launch excitement while being transparent about {issue}.
When to use it: When launch day technical issues or delays require immediate public communication while you’re fixing the problem.
Pro tip: Post updates even when you don’t have new information. “Still working on it, update in 2 hours” builds more trust than radio silence.
You are creating social media content for post-launch momentum and user acquisition.
Product: {product_name} Launch results: {signups / sales / downloads_so_far} Customer highlight: {early_user_success_story} Unexpected use case: {surprising_way_someone_used_it} Team reaction: {how_the_team_feels_about_response} Media mention: {press_or_influencer_coverage} Next milestone: {what_you_are_aiming_for_next} Social proof: {testimonials_or_reviews} Referral ask: {how_followers_can_help_spread_word}
Create post-launch social media content series: results celebration featuring {launch_results}, customer spotlight with {customer_highlight}, surprise story about {unexpected_use_case}, and momentum post pointing toward {next_milestone}. Include {social_proof} and {media_mention} for credibility. End with specific {referral_ask}.
When to use it: 48-72 hours after launch when initial results are in and you want to maintain momentum through social proof.
Pro tip: Share specific numbers if they’re impressive, or focus on stories if numbers aren’t there yet. “127 signups in 24 hours” or “Sarah saved 3 hours in her first day using it.”
Internal Team Communication
You are writing a launch day briefing email for your customer service team.
Product: {product_name} Launch time: {when_it_goes_live} Expected volume: {anticipated_customer_inquiries} Common questions: {top_5_questions_customers_will_ask} Technical issues: {known_bugs_or_limitations} Escalation process: {when_to_involve_product_team} FAQ resource: {where_to_find_detailed_answers} Launch offer details: {pricing_and_terms} Refund policy: {launch_specific_return_rules} Team backup: {who_covers_if_overwhelmed}
Write a 300 to 400 word customer service briefing email. Cover {expected_volume} and {common_questions} with prepared responses. Explain {technical_issues} and {escalation_process} clearly. Include {launch_offer_details} and {refund_policy} specifics. Provide {FAQ_resource} and {team_backup} plan. Use bullet points for quick reference during busy periods.
When to use it: Day before launch when customer service needs to prepare for increased volume and product-specific questions.
Pro tip: Include exact screenshots of what customers will see during the purchase process. Customer service reps answer faster when they know the user interface.
You are writing a sales team launch notification with talk tracks and objection handling.
Product: {product_name} Target customers: {ideal_customer_profile} Pricing: {cost_and_payment_options} Sales process: {demo / trial / direct_purchase} Key differentiators: {competitive_advantages} Common objections: {price / timing / feature_concerns} Success stories: {early_customer_wins} Commission structure: {how_reps_get_paid} Marketing support: {leads / materials / campaigns} Training schedule: {when_product_training_happens}
Write a 400 to 500 word sales launch brief with talk tracks. Position {product_name} for {target_customers} with emphasis on {key_differentiators}. Provide scripted responses to {common_objections}. Include {success_stories} as social proof. Explain {commission_structure} and {marketing_support} clearly. End with {training_schedule} and immediate next steps for the team.
When to use it: Week of launch when sales team needs product positioning and objection handling scripts for prospects asking about the new product.
Pro tip: Record a 5-minute product demo video specifically for the sales team. They’ll use it in prospect calls and learn the positioning faster than reading documentation.
You are writing an all-hands company update about product launch results and next steps.
Product launched: {product_name} Launch date: {when_it_launched} Key metrics: {signups / revenue / downloads / engagement} Goal achievement: {hit_target / exceeded / fell_short} Team highlights: {departments_or_people_who_excelled} Customer feedback: {positive_and_negative_responses} Media coverage: {press_mentions_or_social_buzz} Lessons learned: {what_worked_and_what_didnt} Next priorities: {immediate_improvements_or_next_launch} Company impact: {how_this_affects_overall_business}
Write a 300 to 400 word all-hands update email celebrating launch results. Share {key_metrics} and {goal_achievement} transparently. Recognize {team_highlights} specifically. Include both positive {customer_feedback} and areas for improvement. Mention {media_coverage} for company pride. Connect launch to {company_impact} and outline {next_priorities}.
When to use it: End of launch week when you want to update the entire company on results and maintain momentum for the next initiative.
Pro tip: Include customer quotes, not just numbers. Teams connect emotionally with “This saved me 4 hours” more than “47% efficiency improvement.”
You are writing a product team retrospective agenda for post-launch analysis.
Product: {product_launched} Launch timeline: {planned_vs_actual_dates} Team members: {who_should_attend_meeting} Success metrics: {what_you_measured_success_by} Actual results: {real_performance_data} Process breakdown: {pre_launch / launch_day / post_launch_phases} Major challenges: {biggest_problems_encountered} Wins to celebrate: {what_went_better_than_expected} Next launch: {upcoming_product_or_feature_release} Meeting length: {60_or_90_minutes}
Write a product launch retrospective agenda for a {meeting_length} meeting. Structure in three sections: What went well, What didn’t work, What we’ll do differently next time. Include time blocks for discussing {success_metrics} vs {actual_results}, analyzing {major_challenges}, and celebrating {wins}. End with action items for {next_launch} improvements.
When to use it: 1-2 weeks post-launch when you need to capture lessons learned while they’re fresh but after immediate fires are out.
Pro tip: Send a pre-meeting survey asking each team member for their top 2 wins and top 2 improvements. You’ll get more honest feedback than in a group setting.
You are writing a launch post-mortem email to company leadership with insights and recommendations.
Product: {product_name}