See exactly what you'll receive
This is an illustrative example of a Launch Review. Yours will be tailored entirely to your product, but the shape, clarity and honesty are the same.
sample-launch-review.pdf
Launch Review
Acme, pre-launch Launch Review
Overall verdict
Ready for beta once two launch blockers are resolved
Top three priorities
- 1Guarantee account creation when a payment succeeds, or reverse the charge.
- 2Require ownership transfer before the final workspace owner can leave.
- 3Warn on concurrent edits instead of silently overwriting them.
Launch Blockers
- Payment can succeed while account provisioning fails silently, leaving a paying customer locked out with no clear recovery.
- The final workspace owner can remove themselves, leaving the workspace with no one able to manage it (detailed below).
Product Decisions
- No defined behaviour for existing drafts when a customer downgrades their plan.
- Trial length is enforced in the interface but not on the server, so it can be extended from the client.
Undefined Behaviours
- Concurrent edits to the same record overwrite each other with no warning.
- Refreshing during multi-step onboarding discards everything entered so far.
- Changing timezone mid-session leaves scheduled items showing the previous time.
UX Friction
- Error messages are technical ("422 Unprocessable Entity") rather than human and actionable.
- The empty dashboard offers no guidance on what to do first.
What is already working well
- The core create, edit and share flow is solid and genuinely pleasant to use.
- Sign-up is fast and the first screen sets clear expectations.
Detailed finding
The final workspace owner can remove themselves
- What we observed
- The product allows the final owner to leave or delete their account while they are the only owner of the workspace.
- Why it matters
- The workspace becomes orphaned, with nobody able to manage billing, permissions or recovery.
- Recommended behaviour
- Require ownership transfer to another member before the final owner can leave.
Priority
Critical
Impact
High
Effort
Low
Recommended next steps
Resolve the two launch blockers, decide the downgrade and concurrency behaviours, then run a closed beta of 20–30 users before opening public sign-ups. Everything else can safely follow.
How to read your report
Three principles shape every report we send.
Prioritised, not exhaustive
We lead with what matters most. Launch blockers sit at the top; nice-to-knows sit at the bottom. You always know what to resolve first.
Specific and actionable
Every finding describes what I observed, why it matters and the behaviour I recommend, with no vague 'improve UX' advice you can't act on.
An honest launch call
I tell you plainly whether you're ready to launch, ready after a few fixes, or not yet, and what would change my mind.
Before you launch
Let's do one more check.
Give yourself the peace of mind that comes from knowing an experienced pair of eyes has taken one more thoughtful look before your users do.