Product launch
Launch plans, release notes for users, go-to-market checklists.
Download all 54
Start here 2
The general, start-from-zero entry for a need in this category: it works from a blank start, asks for what it needs and hands off to the specific entries. Example: Plan a trip.
- Product launch track
Takes a launch from positioning to a tiered plan, launch assets, a go or no-go readiness review and a post-launch retro, pausing for approval between steps.
- Plan a product launch
Builds a launch plan sized to the launch tier, with a readiness checklist by function, owners, a dated communications timeline, go or no-go criteria, a rollback plan and success metrics.
Specific 51
One situation, audience, tool or format inside the category. Example: Plan a road trip with children.
- Write a launch announcement
Writes a customer-facing launch announcement for a blog, email, in-app message or changelog that leads with the problem solved and shows exactly how to get started.
- Product marketing manager
Acts as a product marketing manager who connects the product to its market through positioning, launches, sales enablement and customer insight grounded in what buyers actually say.
- Prepare a product demo
Writes a product demo script built around the audience's pains, with setup checklist, story arc, three wow moments, recovery plans for failures and a strong close, timed to the slot.
- Write a competitive battlecard
Writes a one-competitor sales battlecard with where we win and lose, landmines, objection responses, proof points and discovery questions, every claim sourced or flagged.
- Write a launch FAQ
Writes internal and external launch FAQs covering pricing, availability, migration, limitations and tough questions, with an owner and deadline for every unknown. Use before launch day.
- Plan a feature adoption push
Plans a post-launch adoption push for a feature by diagnosing where users drop off, then targeting in-app prompts, emails and enablement by stage, with guardrails and measurement.
- Plan a price change communication
Plans how to communicate a price change, covering impact by segment, grandfathering options, notice timeline, the customer email, support macros, account talk tracks and churn monitoring.
- Write a sales enablement brief
Writes an internal enablement brief for sales and customer success - what shipped, who it is for, talk track, discovery questions, objection handling, what not to promise and an FAQ.
- Choose a launch date
Chooses a launch date by weighing readiness, holidays, competitor and industry events, buying cycles, news cycles and team availability, and names a fallback date and the trigger to use it.
- Define launch tiers
Defines launch tiers for a company, from major launches to silent releases, with criteria, the activities and owners for each tier, edge-case rules and a checklist for tiering new features.
- Plan a Product Hunt launch
Plans a Product Hunt launch with a fit check, goals, a six-week timeline, listing drafts, a launch-day run sheet in Pacific Time, community rules to respect and follow-up.
- Write an in-app feature announcement
Writes in-app announcement copy for a new feature as a tooltip, modal, banner or empty state, with the benefit, one action, dismiss behaviour, targeting rules and how to measure it.
- Write an internal launch announcement
Writes the company-wide announcement of a launch for chat, email or an all-hands, with what shipped, why it matters, who to thank, how to talk about it and where to send questions.
- Write a one-page launch brief
Writes the one-page internal brief that kicks off a launch - what and why, who it is for, tier, date confidence, scope in and out, the ask of each team and the open decisions, with owners.
- Write a monthly product update
Writes a monthly product update for customers covering what shipped, why it matters to them, how to try it and what is coming, in benefit-first language with careful commitments.
- Build a launch budget
Builds a budget for a product launch sized to its tier and goal, with line items by workstream, cost assumptions to price, a contingency, what to cut first and how spend will be judged.
- Design a launch offer
Designs a launch offer - founding price, first-term discount, longer trial or bonus - with eligibility, a real end date, the switch to full price at renewal, a margin check and honest wording.
- Name a new feature
Generates and tests names for a feature inside an existing product against clarity, findability, fit with existing names and trademark risk, and decides between a descriptive and a branded name.
- Plan a branch-by-branch rollout
Plans rolling out a product, process or service change across stores, branches, clinics or depots in waves, with pilot criteria, readiness checks, halt rules, learning loops and rollback.
- Plan a launch retrospective
Plans a blameless launch retrospective with the data to bring, a timed agenda, prompts on what went to plan, surprises, customer reaction and team health, and a template for decisions.
- Plan a product relaunch
Diagnoses why a first launch underperformed, then plans a relaunch with what changed, a new story, the audience to target, channels and the evidence needed before going loud again.
- Brief frontline staff on a release
Writes a one-off briefing for store, call centre, clinic or field staff on a product or service change - what changes, a one-line explanation, likely questions and what to do if it goes wrong.
- Build a launch press kit
Builds a press kit for a product launch with a fact sheet, key messages, spokesperson bios, an image and video list with captions, company boilerplate, embargo instructions and media contacts.
- Plan an AI feature launch
Plans launching an AI feature with quality and safety review, expectation-setting copy, a labelled beta, staged access, cost guardrails, a bad-output feedback loop and launch metrics.
- Plan a developer product launch
Plans launching an API, SDK or developer tool with docs and quickstart readiness, sample apps, versioning and support, developer channels and adoption metrics like time to first call.
- Plan a hardware product launch
Plans launching a physical or connected device with certification and manufacturing gates, ship-date confidence, pre-orders, reviewer units, day-one firmware, fulfilment, returns and support.
- Plan an internal tool rollout
Plans rolling out a new or replacement internal tool with change impact by role, champions, training, cutover and fallback, early support, adoption measures and a date to switch off the old way.
- Plan a launch-day command centre
Plans the launch-day command centre - roles, one channel, a timed run sheet, the signals to watch with thresholds, escalation, halt and rollback triggers and status updates.
- Plan a product launch event
Plans a live or online product launch event - whether it is worth it, audience and goal, format, run of show, live demo safeguards, roles, invitations, follow-up and what to measure.
- Plan a retail shelf launch
Plans launching a physical product into shops - the sell-in pitch, terms to check, shelf-ready packaging, in-store material, staff briefing, stock and the first 12 weeks of rate-of-sale reviews.
- Plan a staged feature rollout
Plans exposing a feature to users in stages - internal, early cohorts, percentages, everyone - with entry and exit rules, guardrail metrics, soak times and comms for each stage.
- Plan a waitlist and invite-wave launch
Plans opening a product from a waitlist in invite waves sized to capacity, with priority rules, the sign-up and invite emails, activation follow-up and the numbers to watch between waves.
- Run a launch compliance check
Checks a launch for legal and compliance exposure - claims, privacy and consent, terms changes, accessibility, trademarks, pricing and regulated wording - and lists what needs sign-off.
- Run a launch enablement session
Plans a live pre-launch training session for sales, success and support teams, with a timed agenda, demo walkthrough, objection drills, role-plays, a short certification quiz and follow-up.
- Take a new service live
Takes a new or changed service to go-live in gated steps - readiness across people, process, systems and premises, staff training, a soft launch, a go or no-go review and a first-month review.
- Write a feature rollback notice
Writes the notice to users when a launched feature is pulled back - what was turned off and why, what happens to their data or work, what to do now and when they will hear next.
- Write a launch delay notice
Writes the notices when a promised launch date slips - for waitlist, pre-order or beta customers, partners and staff - with the honest reason, the new date or when it is set, and what changes.
- Plan a mobile app launch
Plans a mobile app launch with store readiness, beta testing, a phased rollout with halt rules, review prompts, crash monitoring, support readiness and the first-week metrics to watch.
- Decide which plans get a new feature
Decides where a new feature goes in existing plans - every plan, a higher tier, a paid add-on or usage-based - weighing adoption, upgrade pull, existing customers and cost to serve.
- Launch a new product to existing customers
Plans launching a new, separately sold product or add-on to existing customers, with fit-based segments, account team outreach, in-product moments, offers and expansion targets.
- Plan the first 30 days after a launch
Plans the month after a launch with daily then weekly monitoring, a feedback triage cadence, protected quick-fix capacity, follow-up communications and a day-30 decision on what comes next.
- Plan a redesign rollout to existing users
Plans rolling out a redesign of a familiar interface to existing users, with an opt-in preview, a switch-back period, feedback capture, change communications and a firm cut-over date.
- Run a launch go or no-go review
Runs a launch go or no-go review from readiness evidence, separating blockers from accepted risks, and records a go, go with conditions, slip or no-go decision with owners.
- Write a known issues page for a release
Turns internal bug notes into a public known-issues page for a release, with symptoms users recognise, who is affected, workarounds, status and an update policy, without leaking internal detail.
- Plan support readiness for a launch
Prepares a support team for a launch - likely contact reasons, macros, a known-issues list, triage tags, escalation paths, a contact-volume estimate with its assumptions and a feedback loop.
- Launch an integration on a partner app marketplace
Plans listing and launching an app or integration on a platform marketplace such as Shopify, Salesforce, Atlassian or Slack, with review requirements, listing copy, first reviews and ranking factors.
- Pitch an app to store editors for featuring
Prepares a featuring pitch to App Store and Google Play editors for a launch or major update, with the story angle, timing, quality checks, assets and the submission text itself.
- Plan the move from beta to general availability
Plans graduating a product or feature from beta to general availability with exit criteria, what changes for beta users (price, limits, support, SLA), their communications and a GA checklist.
- Plan a joint launch with a partner
Plans launching an integration or joint offer with a partner - shared goals, who announces what and when, approvals for quotes and logos, listings, enablement on both sides and joint follow-up.
- Plan a soft launch in test markets
Plans a soft launch of an app or game in a few test markets, with market choice, KPI gates for retention and monetisation, what to tune each cycle and the criteria for a global launch.
Showing 50 of 51. See them all in search
Advanced 1
Expert or deep work that assumes the user can judge expert output. Example: Plan croissant lamination.
- Plan a quarterly launch calendar
Builds a quarter's launch calendar from many teams' planned releases - tiering each, spacing them to avoid collisions and audience fatigue, respecting blackout dates and flagging dependencies.