✏️Prompts

Product Launch Checklist Prompt

Prompt

You are a product manager preparing for a product or major feature launch.

Launch data:
[DESCRIBE: What is launching, launch date, target customer segments, ARR opportunity (new logo / expansion / churn prevention), pricing changes (if any), key use cases, internal teams involved (sales/CS/marketing/support), any beta testing results, go-to-market strategy]

ARR context:
[PASTE: Expected MRR/ARR impact at 90 days if successful | Churn risk this addresses (ARR amount) | NRR improvement expected | Customers in beta and their ARR]

Build the launch checklist:

Pre-launch (2+ weeks before):
- Feature complete and QA signed off
- Documentation (help articles / release notes) written
- Sales and CS enablement: how does this feature affect renewal conversations and expansion pitches?
- Pricing and billing systems updated (if applicable)
- Marketing assets (email / landing page / social) ready

Launch day:
- Feature flags enabled for target segments
- Monitoring and alerting configured
- Customer communication sent
- Sales and CS notified with talking points linking feature to customer ARR outcomes

Post-launch (first 30 days):
- Usage tracking confirmed
- Customer feedback being collected
- ARR impact measured: any churn prevented, expansion closed, or new logos won citing this feature?
- Success metrics reviewed at day 7 and day 30

Output: Launch checklist by phase. Owner for each item. ARR success metrics defined. Go/no-go criteria. Post-launch ARR impact review schedule.

Why it works

Structuring the checklist across pre-launch, launch day, and post-launch phases ensures nothing falls into the gap between planning and execution. Connecting feature enablement to ARR impact aligns the launch with revenue outcomes rather than just shipping a feature. Including go/no-go criteria forces the team to define what 'ready' looks like before the pressure of launch day.

Watch out for

The checklist will be comprehensive but generic — your specific stack, release process, and team structure will require significant customisation. ARR impact estimates in the brief should be validated by finance, not taken from the AI output.

Used by

MarketersExecutives