GTM Sauce

Built With Science · B2C · science-based fitness coaching app

Release new features quietly, and announce only once usage proves them

Founder says it gives cleaner reads than email-hyped launches; no numbers

Workedfeature-development

What they did

Previously announced every feature by email to all members, which inflated the engagement metrics they wanted to measure. Now: tell a beta pool (~100 long-time former course members plus ~1,000 beta testers) about the feature, collect feedback and iterate, then release it publicly with no announcement and watch the metrics. Only once there is signal it adds value do they announce it.

What happened

Cleaner learning from releases.
“this often inflates a lot of the engagement metrics that you obviously want to measure when you launch a new feature. So we've actually taken the opposite approach where we'll roll out a new feature, we won't say anything, and we'll just see how the metrics do on its own.”
Ethan Ethier
“the beta pool is what we're telling them about the feature. We want them to test it, we want feedback, then we're iterating on that feedback, then we're quietly launching it”
Ethan Ethier

Get tactics like this every Monday

New tactics from the week's founder interviews, each linked to where it was said.

More from this episode