At what seat size does your NRR reach escape velocity?
Crunching data from 1,785,478 users to identify the exact point where retention starts to skyrocket
Hey, Ruchin here! š Welcome back to Toplyne Labs - Edition #4
A weekly digest that covers unique insights on what makes PLG businesses tick, what signals make for the best PQLs, what sales teams get right, what they get wrong, and the meaning of lifeā¦ Go figure š¤·š»āāļø
This week we crunched data from 1,785,478 teams across various categories of PLG tooling to find the exact point where Net Retention Rates (NRR) begin to hit escape velocity.
How many seats do teams/accounts need to get to, for network effects to kick into high gear?
Disclaimer: While this analysis spans over 1.8M users, it also captures a breadth of behavior across various categories of PLG products (Devtools, Creative tools, Communications, etc.). We encourage you to use these insights directionally and thematically.
Letās look at the data.
Get your accounts to 10 or more seats
You know whatās better than an annual contract? A perpetual contract š¤©
If youāre a PLG sales or account management team, you have one job - get your accounts to 10 seats or more and you have yourself a lifelong customer.
Across inherently collaborative tools (unlike single-player tools), the value prop strengthens and grows with every subsequent user you add to your team. And often thereās a direct correlation between the # of users and long-term retention rates.
But at what point do retention rates inflect?
The answer - 10 seats
Land andā¦ *crickets*
Collaborative tools - especially ones that have virality built into them can land and expand. While just ālandā may get you many feet in many doors, what separates the best from the rest is the expansion motion. (Think: Datadog, Cloudflare, Snowflake, AWS)
Beyond the tipping point of 10 users, these teams become your largest drivers of NRR.
How do you nudge smaller teams into teams of 10+?
Youād do this by
Step 1: Identifying network effects - By measuring expansion intent through collaborative product usage events triggered by smaller teams
Jane invited 3 users to view her project
Jon referred 2 team members
Jill left a comment on Jackās document
Step 2: Sales-assist - Identifying hand-raisers who have shown intent within your free tier to offer a product expert/specialist touch to grow smaller teams into teams of 10+.
All while walking the thin line between a great user experience and sales - because letās face it, not everybody wants to talk to sales
Step 3: Top-down sales - With enough users in a team finding value from your product and showing intent, a sales pitch to the decision maker is a no-brainer
āHey Jess - we were looking into your teamās activity and turns out 6 out of 15 members are power users of our product. Especially Jon and Jane šš» Do you think centralized billing and dedicated customer success would make sense?ā
All of that sounds great in theory, but how the hell do I implement this?