Build a risk-tiered launch checklist in minutes. Input your product type, market conditions, and team capacity—get back a prioritized checklist that separates what breaks launches from what's nice to have.
You are a product launch strategist. Generate a prioritized launch checklist based on the following constraints:
Product Type: {{PRODUCT_TYPE}}
Market Conditions: {{MARKET_CONDITIONS}}
Team Size: {{TEAM_SIZE}}
Days to Launch: {{DAYS_TO_LAUNCH}}
Key Risk: {{PRIMARY_RISK}}
Create a checklist organized into three tiers:
1. CRITICAL (tasks that block launch or cause immediate revenue loss)
2. HIGH (tasks that damage reputation or customer trust if missed)
3. STANDARD (tasks that improve experience but aren't blockers)
For each task, include:
- Task name
- Owner role (e.g., Product, Marketing, Ops, Support)
- Why it matters at this risk level
- Dependencies (what must happen first)
- Time estimate
Assume the team is resource-constrained. Recommend which Standard tasks to cut if timeline slips. Format as a table or structured list, not prose.1. Fill in your product type (SaaS, mobile app, marketplace, etc.), current market conditions (competitive, regulated, price-sensitive), your actual team size, and days remaining. 2. Name your primary risk: data security, regulatory compliance, competitor response, customer churn, or technical stability. 3. Run the prompt. 4. Copy the Critical and High tiers into your project management tool (Linear, Asana, whatever). 5. Share the Standard tier with your team and agree now on what gets cut if you slip. 6. Update the checklist weekly—move tasks between tiers as risks shift.
Product Type: B2B SaaS (compliance-heavy) Market Conditions: Highly competitive, 3 new entrants in 6 months Team Size: 8 people (2 eng, 2 product, 1 design, 1 marketing, 1 sales, 1 ops) Days to Launch: 14 Key Risk: Regulatory compliance (SOC 2 audit in progress)
CRITICAL - [ ] SOC 2 Type II attestation or interim letter (Owner: Ops, Why: Non-negotiable for enterprise sales, Dependency: Security audit complete, Time: 2 days) - [ ] Data residency compliance docs (Owner: Legal/Ops, Why: GDPR/CCPA enforcement risk, Dependency: Infrastructure locked, Time: 1 day) - [ ] Customer onboarding workflow (Owner: Product, Why: Blocks revenue recognition, Dependency: API stable, Time: 3 days) - [ ] Incident response runbook (Owner: Ops, Why: First outage will test this, Dependency: Monitoring live, Time: 1 day) HIGH - [ ] Customer support playbook (Owner: Support, Why: First week chaos without it, Dependency: Product stable, Time: 2 days) - [ ] Competitive positioning doc (Owner: Marketing, Why: Sales needs talking points, Dependency: Feature parity check, Time: 1 day) - [ ] Pricing page and terms (Owner: Legal/Marketing, Why: Trust signal, Dependency: Final pricing locked, Time: 1 day) STANDARD (Cut if timeline slips) - [ ] Case studies or testimonials (Owner: Marketing, Time: 3 days) - [ ] Advanced analytics dashboard (Owner: Product, Time: 2 days) - [ ] Blog post series (Owner: Marketing, Time: 2 days)