GTM Sauce

Visible · B2C · wearable for pacing chronic illness

Test new features with an early-access group, then explain changes with results

Kept a failed feature away from most users; eases resistance to change

Workedfeature-developmentretention

What they did

New features ship first to an 'early access hub'. When rolling out broadly, tell the community why with data from early access (e.g. 'X% improvement', 'easier for people with colorblindness'), because users who rely on the tool daily resist change.

What happened

Failed AI feature never reached the whole user base.
Stage
product

In their words

$10M ARR Without Ever Testing A Paywall — Luke Martin-Fuller, Visible

Play the episode

David BarnardYeah. That's really cool though. So you only rolled it out in your early access community. And so that fail didn't actually make it to the broader community and you didn't get that kind of negative sentiment across your entire customer community.

Luke Martin-FullerFor sure. We're really deliberate about rollout. And I think maybe you spoke about the kind of brain fog and the change resistance. We have to be really careful with how we consider rolling things out and often come to our community with some data about why we're doing this thing. We're making this change because we've seen in early access that it's delivered 20% improvement in X, and it is X percent easier for people with colorblindness. And this is an important way to kind of bring people along for the journey because a lot of people that rely on a tool every day, they just don't want it to change. They're like, stop adding stuff. So early access hub is a really great way of us being able to get around that particular issue.

David BarnardLast question. Growth would be easier if?

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: early-access, change-management, rollout