Product Launch Checklist Generator by Risk Level

Full prompt

You are a product launch operations expert. Generate a launch readiness checklist for a {{PRODUCT_TYPE}} launching to {{TARGET_MARKET}}.

Context:
- Product category: {{PRODUCT_TYPE}} (e.g., B2B SaaS, mobile app, physical product, feature release)
- Target market: {{TARGET_MARKET}} (e.g., enterprise, SMB, consumer, existing user base)
- Market maturity: {{MARKET_MATURITY}} (e.g., new category, established market, crowded segment)
- Team size: {{TEAM_SIZE}} (e.g., 2–5 people, 5–20 people, 20+ people)
- Launch timeline: {{LAUNCH_TIMELINE}} (e.g., 4 weeks, 8 weeks, 12+ weeks)
- Key constraint: {{KEY_CONSTRAINT}} (e.g., limited budget, first launch, regulatory approval required, competitor pressure)

Deliver a checklist organized into three risk tiers:

**Critical (must complete before launch):** Tasks that block go-live or create legal, compliance, or security risk.
**High (strongly recommended):** Tasks that significantly impact adoption, revenue, or brand perception.
**Standard (nice-to-have):** Tasks that improve experience but are not blockers.

For each task, include:
- Task name
- Owner role (e.g., Product, Marketing, Engineering, Legal)
- Timeline (e.g., Week 1–2, Week 3–4, Launch week)
- Key dependency (if any)
- Success criteria (1–2 sentences)

Organize by phase: Pre-Launch (4+ weeks out), Launch Prep (2 weeks out), Launch Week, Post-Launch (first 30 days).

Be specific to {{PRODUCT_TYPE}} and {{TARGET_MARKET}}. Avoid generic advice. Prioritize based on {{KEY_CONSTRAINT}}.

How to use

1. Fill in all six input fields with your launch specifics. Be honest about team capacity and timeline—this shapes the checklist realism. 2. Run the prompt in your preferred AI tool (Claude, ChatGPT, etc.). 3. Copy the output checklist into a project management tool (Asana, Linear, Notion) and assign owners. 4. Use the risk tiers to set sprint priorities: complete all Critical tasks before moving to High. 5. Review the checklist weekly and mark tasks complete; flag blockers early. 6. Post-launch, document what you skipped and why—this informs your next launch.

Customization tips

• Adjust task depth based on team size: lean teams should focus on Critical tasks only; larger teams can parallelize High and Standard tasks.
• If regulatory approval is required (healthcare, fintech), add 2–4 weeks to timeline and elevate compliance tasks to Critical.
• For feature releases to existing users, reduce pre-launch tasks (skip sales outreach, support training) and focus on in-app messaging and onboarding.
• If budget is constrained, cut paid ads, analyst outreach, and video production from High/Standard; keep product, engineering, and legal Critical tasks.
• For first-time founders, add a 'Launch Retrospective' task post-launch (Week 4) to document what worked, what didn't, and lessons for next launch.
• If competitor threat is high, accelerate timeline and add competitive monitoring task to High tier.
• Customize owner roles to match your org: if you lack a dedicated marketing person, assign marketing tasks to product or sales.
• Use the checklist as a template, not gospel—remove tasks that don't apply (e.g., physical product logistics if you're a SaaS) and add domain-specific tasks (e.g., app store optimization for mobile).