Playbook · Signal motion
Product launch: the 30-day post-launch motion
Product launches create predictable cross-functional pain. The team is exhausted, the metrics conversation is contested, and the VP Product is fielding 'how's it going?' questions from the board. Outreach that names the post-launch reality (not the launch itself) lands.
01The signal
Summary
Product launches create predictable cross-functional pain. The team is exhausted, the metrics conversation is contested, and the VP Product is fielding 'how's it going?' questions from the board. Outreach that names the post-launch reality (not the launch itself) lands.
02Cadence
The step-by-step rhythm we use to run this play. Skipping steps usually loses more than it saves — the asymmetric spacing is part of why it works.
Day 14
email
Anchor on launch + name a specific post-launch operational reality (feedback fragmentation, attribution confusion, metric definition fight)
Day 21
linkedin
Share something useful about post-launch metrics
Day 28
email
Curious tone — what's the unexpected user behavior you've seen?
Day 42
email
Break-up email
03Expected outcome
Outcome: 16-23% reply rate. Question-first openers ('how's it tracking?') outperform value-first by ~30%.
Success metric: Reply with a specific post-launch observation — the start of a real conversation.
04Anti-patterns · do not run this when
- Do not congratulate generically — every other vendor does this
- Do not send within 7 days of launch — too noisy
- Do not pivot to product pitch on first reply — the relationship is still forming
Playbook entry · ships as-of {date('M Y')}. Operator-written, no theory inflation. If you've run this play and the numbers don't match yours — or the rhythm needs a tweak — write to [email protected] and we'll revise.
Signal-anchored outbound, no theater
Run this play on every account in your CRM.
Connect a CRM. Mama detects the trigger, scores the fit, and drafts the first message in the rhythm above. Free up to 100 accounts. No card.