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.

PostHog logoPostHog
Mixpanel logoMixpanel
Slack logoSlack
THE GRIND

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.

THE FLOW
5 steps · 3 toolkits

Your agent runs it end-to-end.

  1. 01
    Identify the launch cohort — users who first saw the feature after ship date
    posthog logo
  2. 02
    Pull adoption — what % of active users engaged week-one
    posthog logo
  3. 03
    Pull D7 retention for the cohort from Mixpanel
    mixpanel logo
  4. 04
    Compare against the pre-launch baseline and the goals you set
  5. 05
    Post a 4-line recap to #product: adoption, retention, verdict, next watch
    slack logo
THE PAYOFF

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.