GTM Sauce

Symmetry · B2C · gym workout tracker

Start each test from a real user problem and A/B test for two weeks

Credited for reaching $160K/month; most tests don't move the needle

Workedexperimentationfeature-development

What they did

Start from a problem, not a solution: What problem am I solving? How do I know it's real? Then list solutions/hypotheses, estimate how much each moves the target metric, define guardrail metrics, and A/B test control vs new version for at least two weeks before analyzing. Maintains 'Evelyn' (Experiment Velocity Engine List) database of experiments sourced from user interviews; product experiments in PostHog, paywall tests in Superwall. Evolved from building what founders wanted (terrible) to building user requests (mediocre) to this.

What happened

Credited as the main reason the app reached $160K/month in a year; most tests don't move the needle
5:35
“First, we built what we wanted. Terrible idea. Second, we built what users wanted, like directly from feedback requests. Mediocre.”
Mauro Botanes
11:24
“How much will each hypothesis move the metric? Are there any guardrail metrics I should watch out?”
Mauro Botanes
11:35
“after at least two weeks of running the experiment, you then analyze the data”
Mauro Botanes
11:42
“this is what we call Evelyn, Experiment Velocity Engine List in your numbers”
Mauro Botanes
13:20
“Also for A-B testing, the payables, we use SuperRule.”
Mauro Botanes

Related topics

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