Overview
A launch performance report helps a product marketing manager explain what happened after launch across campaign results, pipeline signals, sales feedback, product feedback, and follow-up actions.
This playbook replaces the launch readout workbook: the spreadsheet-tab pile where goals, metrics, sales notes, product questions, and next steps slowly drift apart. Juno installs a launch report and metrics table so the readout has one durable home.
Use it after a product, feature, offer, or market launch when the team needs a practical answer to "how is it landing?" rather than a wall of screenshots.
Why you should connect launch signals early
Launch day is loud, but the useful read usually arrives in pieces. Campaign engagement may show demand, pipeline movement may lag, sales may hear objections first, and product or customer feedback may reveal whether the promise matched reality.
Atlassian describes a product launch checklist as covering the path from market research through post-launch evaluation, with coordination across teams (Atlassian). That cross-team shape is exactly why a launch readout needs more than campaign metrics.
HubSpot also frames post-launch work around measuring results and adjusting after the launch (HubSpot). Juno turns that adjustment loop into a reusable workspace: measured signals, confidence notes, owner-ready actions, and open questions stay together instead of scattering across meeting notes.
Step-by-step
- 1Confirm the brand or product, launch name, launch date, reporting window, success metrics, and any source notes the team already has.
- 2Set up the installed launch workspace with a working report document and launch metrics table.
- 3Review supplied campaign results, pipeline summaries, sales feedback, customer or product feedback, support themes, and follow-up actions.
- 4Record each useful signal with its period, value, comparison, source note, freshness status, confidence, interpretation, owner, and next action.
- 5Update the launch report with the current readout: what worked, what underperformed, what sales and product teams are hearing, and what should change next.
- 6Refresh the report summary so stakeholders can scan on-track signals, watch items, blockers, missing evidence, and priority follow-up before the next launch review.
Frequently asked questions
Does this replace campaign reporting?
No. Campaign reporting is the parent workflow for channel and campaign performance. This playbook is a focused launch extension because launch state spans campaign results, pipeline signals, sales feedback, product feedback, and follow-up actions.
What sources should I provide?
Bring whatever the team already trusts: campaign exports, CRM summaries, pipeline notes, sales call themes, launch retro notes, customer feedback, support themes, product adoption snapshots, or pasted metric updates.
Can it run without connected tools?
Yes. The default workflow uses Juno's installed document, table, and scheduling capabilities. It can work from pasted metrics, uploaded files, workspace tables, or manual notes without requiring a non-default integration.
How often should I refresh the readout?
Run it once for a bounded launch retro, or weekly during the first few weeks after launch. Weekly refreshes are most useful while campaign response, pipeline creation, sales feedback, and product adoption are still changing.