Product GTM · 18 launches in 21 months. Cadence, not project.
A B2B communications platform. The PMM seat shipped 18 launches in 21 months at Tier 1 or Tier 2 impact, absorbed a launch mid-flight after the GTM owner walked, and landed AI SDR at #18 Product of the Day on Product Hunt. The monthly report tempo never broke.
Voice AI launch playbook
Five launches in this case were voice-AI or agent products: AI Voice Agent (Nov 2024), AIVA Actions (Apr 2025), AI SDR (Sep 2025, #18 Product of the Day), Outbound AI Voice Agent (Jan 2026), and the Holiday Agent in prep. The pattern below transfers to any agent-product company. The numbers above are JustCall's. The shape is portable.
Pattern: launch the agent against the highest-anxiety buyer concern (compliance, hallucination, "will it sound human"), not the highest-novelty feature. Position the workflow it removes, not the AI it adds. Ship the legal disclosure into the hero copy so the buyer's first read is "consent, not magic." Track adoption per workflow, not per seat.
What it was
One PMM seat. Two Tier 1 engines (Sales Dialer and AIVA). A monthly report tempo the rest of marketing, sales, and CS calibrated against. The brief was simple. Do not let launches become events. Make them a cadence the org can plan around.
The diff
Before: launches that shipped when the product team was ready and produced a hellobar plus a blog post. No flight pattern. No downstream CRO read.
After: a one-month flight pattern. MRD, LP, one-pager in month one. Launch assets and enablement in month two. A measured CRO or revenue number in the quarter after. The Sales Dialer relaunch (Sep–Oct 2024), AIVA Actions (Jul 2025), and AI SDR Product Hunt (Oct–Nov 2025) all follow the same shape.
What I actually did
- Sales Dialer relaunch, Sep–Oct 2024. MRD, LP, video, blog, emails, pricing copy on web and in-app, UX copy for dialer modes, two enablement sessions. Downstream A/B in Dec 2024: Auto Dialer +44% leads, Power Dialer +55%, Predictive +28% (self-reported, monthly PMM report).
- AIVA Actions, Tier 1, Jul 2025. Launch email cadence pulled a 51% open rate against a 30% newsletter baseline. Pricing change communicated same cycle. Sales and CS enablement same month.
- AIVA Customer Webinar series fed the Actions launch: 200+ registrations, 125 attendees, 29 qualified leads, 24 qualified deals, 4 won, $2K MRR plus a $1K implementation package. First AIVA deliverable with revenue attribution.
- Other 2025 lifts on the same report tempo. Workflows GA (160+ beta customers, ~400 workflows, ~25,000 calls). SMS Analytics launch email 45.2% open, 4.4% CR. SMS Bundles $67K+ MRR Jun–Sep. Build with AI LP 175+ submissions. AI SDR Product Hunt hit #18 Product of the Day.
- SMS Inbox, Mar 2026. The GTM owner left. Absorbed the launch. Shipped 4 preview emails, 3 in-app banners, a What's New blog, 4 LP refresh drafts, 11 help articles, a CS FAQ, and rewrote the LP hero away from the "automation created the problem" frame into a buyer-first one. 200+ preview opt-ins before formal release.
What stayed honest
Every metric in this case is self-reported and lives in a monthly PMM report. The reports are available on request under a hiring-stage NDA. The losses are on the same record: launches that produced no measurable downstream are not in the diff card, and the comms work that did not move a number is not dressed up as work that did. The Mar 2026 absorption is the stress test. The cadence held. That is the part that is not a metric.
What it became, in substrate
routines/launch-flight-pattern. MRD/LP/one-pager month one, launch + enablement month two, CRO read quarter after.routines/monthly-pmm-report. the report tempo as a planning instrument, not a recap.patterns/absorb-without-breaking-cadence. owner-departure protocol for in-flight launches.skills/launch-email-cadence. preview, announce, follow-up sequence calibrated against the newsletter baseline.
Like what you read? Book 30 minutes.
Pick a slot →