The Myth of the Magic Number: How to Actually Find Your Product's Activation Moment

Advocates: Lauryn Isford (Head of Growth at Airtable) -- Led growth at Airtable during its rapid scaling phase and previously worked on user growth at Facebook, giving her direct experience with both consumer and B2B activation metrics.

For multi-player B2B products, individual user activation is not enough. A user who creates an Airtable base alone has not truly activated -- the product's value comes from team collaboration. You need to measure whether a workspace is activated, not just a user.

Airtable's core activation metric was W4MUA: week 4 multi-user active, meaning at least two users working together in the fourth week. Only about 5-15% of signups ever reached it. Isford argues this is a feature, not a bug:

"I would much prefer to pick a more specific, more precise metric that maybe only 5% of users reach, but know that those 5% of users will be with us for the long haul, and if we could get that 5% even to 6% or 7%, it would have huge downstream effects on long-term metrics for the business."

Lauryn Isford

▶ 00:26:38

Crucially, Airtable did not rely on a single metric. They tracked user-level metrics (W2A, W4A by persona) alongside workspace-level metrics (W4MUA, build rate), so experiments could reveal which dimension of activation they were moving.

On stability:

"Having stability in north star metric for at least six months feels like table stakes to me and that's for the reasons that I cited before, for building momentum, for building domain expertise."

Lauryn Isford

▶ 00:36:36

But she also warns against over-fetishizing the perfect metric. Airtable's growth org itself pivoted its north star from revenue to user growth when the biggest opportunity shifted.

Advocates: Hila Qu (Growth Strategist, Reforge / GitLab) -- Led the PLG motion at GitLab and authored two of the most popular posts ever published in Lenny's Newsletter on product-led growth.

Hila Qu challenges the "single magic moment" framing. Not every product has a dramatic eureka experience. For many products -- especially complex B2B tools -- activation is a series of small value experiences that build confidence.

"Think about all the ways you can reduce time to value. It doesn't need to be this big aha moment in the first five minutes, but at least give them some mini aha moments."

Hila Qu

▶ 00:22:07

The practical implication: if your product takes days or weeks to deliver its full value (as many enterprise tools do), you cannot wait for the big moment. Design your onboarding to deliver small wins quickly -- a successful import, a useful dashboard, a time-saving automation -- that build momentum toward deeper activation.

But Qu identifies a gap most teams overlook. Even after users hit the aha moment, there is a large distance between that experience and the decision to pay:

"Between this kind of activation usage, aha moment to this conversion moment, actually there's a big gap. And what is the gap? How you can understand the gap, how you can guide people around that journey is basically you need to have a very good grasp of data."

Hila Qu

▶ 00:23:03

One practical technique: give users a "warm start" with sample data or pre-built templates so they can experience value immediately rather than staring at a blank screen.

Advocates: Sean Ellis (Author of Hacking Growth, GrowthHackers) -- Coined the term "growth hacking," invented the most widely used PMF survey, was head of growth at Dropbox and on the founding team of LogMeIn ($4B exit).

Sean Ellis draws a critical distinction: your activation metric should describe an experience, not a usage count. "Used the product 100 times" correlates with retention, but you cannot design onboarding around it.

"I don't think there's necessarily one exact right answer of what is that aha moment. There might be two or three different things. I think it's that intentionality about picking something that's experience-based."

Sean Ellis

▶ 01:03:41

The test is simple: can you design an onboarding experience that gets users to this metric in their first session? If not, the metric is too far down the funnel.

"I do see some companies that are like, 'Well, the activation moment should be, they've used it a hundred times.' That's going to correlate to long-term retention, but it's just not very actionable."

Sean Ellis

▶ 01:03:41

Ellis also makes a broader point about retention: it is almost always a function of onboarding to the right user experience, not tactical retention hacks. At a mobile security company, Ellis moved the PMF score from 7% to 40% in two weeks -- not by changing the product, but by repositioning on antivirus and redesigning onboarding so the first action was setting up virus protection:

"We streamlined onboarding so that the first thing that they did after signing up for the product was to set up the antivirus and then get a message 'you're now protected from viruses.' The next cohort of people that we surveyed were at 40% saying they'd be very disappointed without the product."

Sean Ellis

▶ 00:11:38

Advocates: Ben Williams (VP of Product at Snyk) -- Built Snyk's growth organization from scratch, transforming it from an ad hoc effort into a structured PLG juggernaut with dedicated acquisition, activation, and monetization teams.

Ben Williams offers the most structured framework. Activation is not one moment but three sequential milestones that a team must hit:

"Activation is indicative of the team forming a habit around the usage of Snyk. And when I say the usage, I actually mean deriving core value, which is ultimately fixing vulnerabilities. It's not just logging in. It's not even just finding vulnerabilities, it's fixing vulnerabilities."

Ben Williams

▶ 01:19:28

The setup moment is when the user completes the necessary configuration (connecting a repo). The aha moment is when the user first glimpses value (seeing a vulnerability detected). The habit moment is when the behavior becomes recurring (fixing vulnerabilities regularly). At Snyk, the habit moment became the formal activation metric: "F30D" -- a team fixing a vulnerability within 30 days of team creation.

"In the activation process, we have set up moments, aha moments and habit moments and our habit moments that we define as a team being activated, it's related to fixing vulnerabilities within 30 days of team creation."

Ben Williams

▶ 01:20:17

Williams then reverse-engineered the activation funnel, working backward from the habit moment to find which aha and setup moments reliably preceded it:

"We then worked back to figure out that's the habit moment. That's what we see as activation, but there's a set of steps that teams need to get there. So what's the aha moment before that? What's the setup moment and what are the individual steps that the team needs to go through to reach that set up moment?"

Ben Williams

▶ 01:22:19

One surprising finding: a single fix within 30 days was sufficient. Teams that fixed more than once in the first 30 days were not significantly more likely to retain than those who fixed once. The threshold was binary, not proportional.