Launch Recap: Did It Move the Needle?
For a squad that ships on Tuesday and wonders on Friday whether anyone's using it. One prompt pulls adoption and retention for the launch cohort, writes the narrative, and posts to #product — no manual dashboard stitching.
Launches go dark after the demo
The feature ships, the Slack post goes out, and then — nothing. Nobody checks whether it landed until someone asks in the next planning, and by then the cohort is stale.
Adoption data lives in PostHog, retention lives in Mixpanel, nobody opens both
The launch recap never gets written because there's always a new launch
Feature usage drops quietly while the team moves on
Composio collapses all of this into one prompt — here's what that looks like.
Your agent runs it end-to-end.
- 01Identify the launch cohort — users who first saw the feature after ship date
- 02Pull adoption — what % of active users engaged week-one
- 03Pull D7 retention for the cohort from Mixpanel
- 04Compare against the pre-launch baseline and the goals you set
- 05Post a 4-line recap to #product: adoption, retention, verdict, next watch
Every launch gets a verdict
No feature ships into silence. Within a week, the team sees whether adoption and retention moved — and decides whether to double down or fix.
Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.
Catch Up on Slack Since Yesterday
Ask "what happened in Slack yesterday?" and get a consolidated, channel-by-channel recap with links back to the threads.
Read →Daily Morning Brief
One prompt pulls today's calendar, unread Gmail, open GitHub PRs, and overdue Notion tasks into a one-screen brief.
Read →Meeting Prep Sheet
Five minutes before your next call, get a prep sheet — attendees, last email, open Jira, recent Slack.
Read →