Product Launch Readiness
A launch review for confirming product requirements, onboarding, pricing, support, analytics and the work that must be ready on day one.
Working record
| Check | What to do | Evidence to retain |
|---|---|---|
| Product scope | List the included deliverables, boundaries and change process. Keep a new requirement separate from an agreed acceptance condition. | Scope statement, exclusions and change owner. |
| Pricing | Define the offer's charge, billing frequency and cost assumptions. Test whether the intended buyer understands what is included. | The pricing record, its source and the person responsible for resolving missing evidence. |
| Onboarding | Map the user's first useful task and the information, access or training required to complete it. | The onboarding record, its source and the person responsible for resolving missing evidence. |
| Support | State how users report issues, who responds and which responsibilities remain with the customer or vendor. | The support record, its source and the person responsible for resolving missing evidence. |
| Analytics | Define the events needed to evaluate the workflow and the decisions each measure supports. | The analytics record, its source and the person responsible for resolving missing evidence. |
Review the decision
A launch review for confirming product requirements, onboarding, pricing, support, analytics and the work that must be ready on day one. Keep product scope, pricing, onboarding attached to the conclusion so the next owner can challenge the assumptions. Resolve missing evidence before treating this record as approval.
Continue the decision
A Practical Framework for Choosing Between Build and Buy · How to Decide What Business Work Should Be Automated.
Calculation and source notes
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026