Enterprise Product Launch Readiness Audit

Role: Principal Product Marketing Manager with 12+ years directing Tier-1 enterprise software launches.

Context

• Product being launched: {{product_name}}
• Ideal customer profile: {{target_icp}}
• Monetization and packaging: {{pricing_tier}}
• Readiness of sales collaterals: {{sales_enablement_status}}
• GTM launch classification: {{launch_tier}}
• Target revenue and pipeline milestone: {{target_pipeline_goal}}

Task

Generate an actionable, phased launch readiness gate checklist that evaluates all pre-launch dependencies, cross-functional sign-offs, and critical delivery items required to achieve {{target_pipeline_goal}} for {{product_name}} without operational failure.

Method

1. Analyze {{target_icp}} and {{launch_tier}} to define strict governance criteria for pre-launch, launch day, and post-launch phases.
2. Review {{sales_enablement_status}} to construct tactical verification points for pitch decks, demo environments, battlecards, and objection scripts.
3. Formulate asset-readiness checks covering landing pages, legal disclaimers, case studies, and customer-facing technical documentation.
4. Design operational checkpoints evaluating pricing governance, discounting rules, and quote-to-cash workflows based on {{pricing_tier}}.
5. Establish cross-functional sign-off criteria specifying role-based accountability across Product, Sales, Marketing, and Customer Success.
6. Detail emergency triage protocols and contingency checkpoints in case of critical day-one GTM blockers or pipeline drift.
7. Map measurable trailing indicators and cadence checkpoints to safeguard {{target_pipeline_goal}} during the initial rollout window.

Constraints

• MUST categorize every checklist item into clear chronological launch phases (T-14 Days, T-48 Hours, Day 0, Day +7).
• MUST assign an explicit functional owner role and pass/fail verification criteria to each task item.
• MUST NOT include vague advice; write prescriptive, testable verification steps.
• Deliverable MUST focus squarely on launch readiness execution rather than broad strategic theory.

Output format

• Phase-by-phase Markdown tables containing: Checkpoint ID, Action Item, Owner Role, Verification Method, and Go/No-Go Impact.
• Section 1: Pre-Launch Readiness Gates (T-14 to T-2 days, minimum 8 items).
• Section 2: Launch Day Operational Execution (T-0, minimum 6 items).
• Section 3: Post-Launch Pipeline & Adoption Audits (Day +1 to +14, minimum 5 items).

Self-review

• Are all 6 contextual variables explicitly operationalized inside the checklist items?
• Does every checklist point include unambiguous pass/fail criteria for the team?
• Are the checks realistically tailored to the selected {{launch_tier}}?