TL;DR
Elena Verna’s insight flips conventional growth wisdom on its head: build retention first, then acquisition. This framework breaks down the value loop, expansion revenue, and network effects in an order that actually works for early-stage products.
Elena Verna advises Miro, Amplitude, and MongoDB on how to grow their products. She’s seen the data from companies that have scaled to hundreds of millions in revenue. And her insight is so simple it sounds wrong: most startups are optimizing for the wrong metric.
They’re obsessed with acquisition. How many signups this month? How many new users? How do we grow the logo base?
Elena’s framework flips this on its head: retention is the growth lever. Not after acquisition. Not alongside it. Before it. First.
Here’s why this matters to you if you’re building a product-led company, or even if you’re not: the companies that win at growth have nailed their retention loop first. Everything else is spray-and-pray until that’s tight.
Why Does Retention Come Before Acquisition?
Let me illustrate with a simple math problem.
Company A: 500 signups/month, 2% retention (churn 98%). Month 4, they have ~500 users. Month 12, they have ~500 users. No growth. Just wheel-spinning.
Company B: 100 signups/month, 40% month-on-month retention. Month 4, they have ~250 users. Month 12, they have ~500+ users. Linear growth from a tiny fraction of the acquisition budget.
This isn’t metaphorical. This is how the math works. If your retention is broken, more acquisition is just pouring water into a leaky bucket. It’s exhausting and pointless.
Elena’s insight: the best growth loops are built in the product itself. Not in your marketing. Not in your sales strategy. In how the product creates habits.
What Are Elena’s Three Layers of Growth?
Elena’s retention-first thinking breaks down into three layers:
Layer 1: The Value Loop (Habit Formation)
This is the moment between ‘user signs up’ and ‘user comes back without being asked’.
For Miro, it’s: you create a whiteboard, invite a mate, they respond in real-time, you see value instantly. Habit formed. You use it next week without thinking.
For Amplitude, it’s: you log in to track one metric, you see the pattern, you build a dashboard, you check it daily. Habit formed.
Elena calls this the value loop. It’s the smallest unit of product delight that creates a reason to return.
Most teams don’t think about this obsessively. They build a feature, ship it, assume users will see the value. That’s backwards. You need to design the value loop first. Then build features around it.
Layer 2: Expansion Revenue (Usage-Based Growth)
Once retention is solid, Elena’s framework says you earn expansion revenue by making the product more valuable as users use it more.
For Miro: more boards, more team members, more integrations. Each expansion is a natural ask because users are already in the habit of using the product.
For Amplitude: more properties tracked, more custom events, more dashboards. Again, it’s not a sales pitch. It’s a natural progression because the user is already deriving value.
This is where ‘product-led growth’ gets interesting. You’re not selling expansion. You’re observing where users naturally hit the limits of the free product and offering them a way to go deeper. The product itself triggers the upgrade conversation.
Layer 3: Network Effects (The Leverage Moment)
This is where it gets exponential. Once retention is tight and expansion is happening, users invite other users because using the product with others is better than using it alone.
For Miro: a whiteboard is useless solo. You invite a mate. They see the value. They invite someone else. Network growth accelerates.
For Amplitude: you want your teammates seeing the same metrics. You invite them. They see the power of the platform. They might upgrade.
Network effects don’t happen by accident. But they do happen naturally if layers 1 and 2 are solid. You don’t need a referral program. The product sells itself because using it with others is demonstrably better.
How Do You Apply This at Early-Stage With Almost No Data?
Here’s the tension: Elena’s framework assumes you have thousands of users and months of cohort data. Most early-stage companies don’t. You have 100 users and a prayer.
But you can start applying the framework immediately, even with tiny numbers.
Start with the value loop. Don’t measure anything yet. Just watch five users. Really watch them. Do they see the value in their first session? Do they come back day 2? Do they invite someone else? Don’t assume. Sit next to them.
If you can’t get five users to exhibit the value loop behaviour in their first week, your product isn’t ready yet. Fix that before you worry about acquisition.
Once you have 20 users where 50%+ are coming back in week 2, you know the value loop is working. Now think about expansion. What’s the natural next step for power users? What does a ‘power user’ even look like in your product?
At 100 users with 40% week-on-month retention, you can start looking for expansion signals. Are users hitting limits? Are they asking for features that point toward expansion? This informs your pricing model.
You don’t need perfect data. You need directional signals. Is retention trending up or down? Are power users clustering around certain features? Are you hearing unprompted expansion requests from users?
Which Metrics Should You Track?
Elena focuses on a few metrics religiously. When you’re early, track the same three:
Week-1 retention: Do new users come back in their first week? If less than 25%, your value loop is broken.
Month-on-month retention by cohort: Of the users from 8 weeks ago, how many are still active? If less than 30%, you’re churning faster than you’re growing.
Expansion rate among power users: Of your top 20% most active users, what % are paying for a higher tier or using paid features? If it’s below 30%, your expansion loop isn’t clicking.
Everything else is noise until these three are moving in the right direction.
When Does Elena’s Framework Not Apply?
Elena’s framework is built on the assumption of a self-serve product with clear value in the first session. It works beautifully for Miro, Amplitude, Notion, Slack, Figma.
But what if you’re building a B2B SaaS sales tool that requires a 30-minute onboarding call to see value? What if you’re building something that’s genuinely complex?
The framework doesn’t break. But you need to adapt it. Your value loop might happen in week 2 instead of day 1. Your expansion might be driven by a sales rep instead of self-serve. Your network effects might come from integrations instead of peer invites.
The underlying principle holds: retention first, expansion second, network effects third. The timeline and distribution channel might shift, but the sequence doesn’t.
Why This Wins in Competitive Markets
Acquisition costs are going up. CAC is getting more expensive across every channel. The companies winning now aren’t the ones with the biggest marketing budgets. They’re the ones with the tightest retention loops.
If your retention is 50% month-on-month and you’re growing 5% MoM organically, you can outrun a company spending 3x more on acquisition because their retention is 20%.
Elena’s framework gives you the roadmap. It’s not about being clever with marketing. It’s about building a product that users don’t want to leave.
Frequently Asked Questions
How do you measure the value loop if users are early and data is sparse?
Watch qualitatively before you measure quantitatively. Sit with five new users. Ask them: Did you see value in your first session? Would you come back tomorrow? Would you recommend this to someone? Their answers tell you if the value loop is working before you have any retention cohorts.
Can you have strong month-on-month retention without network effects?
Yes, absolutely. Retention and network effects are separate layers. A single-player app can have great retention if it solves a real problem. Network effects compound that retention, but they’re not required for PMF. Strong retention alone is already a strong signal.
At what user count should you start worrying about expansion revenue?
When you have 30%+ of users coming back consistently in month 2. At that point, you can start observing where power users naturally hit limitations. Expansion revenue at 10-20 users is premature. Wait until the core value loop is proven.
How long does it usually take to see network effects if the product is collaborative?
It depends on the collaboration trigger. If inviting others is built into the core flow (like Miro), you might see network growth signals in months 2-3. If it’s optional, you might not see real network effects until you have thousands of active users. Make collaboration effortless, not optional.