GTM Sauce

Burner · B2C · second phone number app

Use paywall tools so the product team can launch tests without engineers

From 1-2 paywall tests a month to several times that; about 1 in 4-5 wins

Workedexperimentationpaywall

What they did

Added technology so paywall tests are shipped by the product team rather than gated on engineering. Velocity went from one or two paywall tests a month to a multiple of that; the bottleneck is now analytics and data maturity. Plan to extend to onboarding and win-back/cancellation flows.

What happened

Multiple times more paywall tests per month; one winner per four or five tests.
Stage
mature

In their words

Pivots, Funding, and Building Apps That Last – Greg Cohn, Burner

Play the episode

David BarnardYeah. All right. What was your biggest win of the past year?

Greg CohnBiggest win in the past year, I mean, aside from launching premium full stop was definitely adding technology to increase our paywall testing speed. We're always a very test-driven company, but we were shipping one or two paywall tests a month and we're able to do a multiple of that today. And it's very interesting because the velocity is now on the product team, not gated by the engineering team. And probably the speed to results is mostly gated by analytics now and maturing of data, as opposed to how fast can we ship features or excuse me, tests. But it's still true that we don't always know the ones that are going to win. There's one winner for every four or five that we do.

David BarnardYeah, yeah. Paywall velocity. It's been a big topic over the last couple of years. And I just like Sarah. I mean, we've seen a lot of apps do really well. You just wouldn't think that moment would have as big of impact as it does, but it does forever...

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

Tags: paywall-testing, test-velocity, no-code-paywalls