Chime
← Back to blog
Playbooks

$400M ARR, under 200 people: Elena Verna's B2B playbook

Lovable's Head of Growth walked through what actually compounds in B2B when AI can clone your feature set in a weekend. Here's what she said.

By Chime · Jun 5, 2026 · 6 min read
Charcoal drawing of a folded diagram sheet with geometric shapes, arrows, and pencil cross-outs

Elena Verna spoke at SaaStr AI a year into her role as Head of Growth at Lovable, right around when the company crossed $400M ARR with fewer than 200 people. The question she put in front of the room: when AI writes 80%+ of your code and anyone can vibe-code your feature set over a weekend, what is actually left to compete on?

Direct answer

Lovable hit $400M ARR with under 200 people by rejecting feature differentiation as a durable moat and leaning hard on brand, data, network effects, and org structure that traditional headcount ratios can't replicate. Head of Growth Elena Verna argues that the companies still building around feature leads are building on borrowed time, and that the next decade of B2B belongs to orgs that ship fast, stay lean, and invest in the moats AI can't clone.

The $2M ARR per employee number is not a coincidence

The math is simple and the implications aren't. Lovable had north of $2M in ARR per employee at $400M. That ratio wasn't possible in the pre-AI org chart, and it didn't happen by accident.

Verna calls their structure "product engineering." The old ratio, one PM to seven engineers to a designer to a marketer, is gone. Everyone does IC work. Everyone ships. No one is purely coordinating.

What makes this stick is that the model only works if the people at the top stay builders. Verna is explicit: she fired herself out of the marketing job, then handed off the growth lead role, and went back to being an individual contributor. That's not a demotion story. It's a deliberate bet that her leverage is higher as a high-powered IC with a stack of agents than as someone running coordination meetings.

The revenue-per-head number is the output of that bet, not the goal. When everyone ships to production, the metric takes care of itself.

Feature differentiation is a short-term lead, not a moat

For the past 15 years, B2B companies built growth engines on top of product advantages. We won because we had better engineers, a better roadmap, faster execution on features. Verna's argument is that this worked because building was expensive and slow. Neither is true anymore.

When 80%+ of your code is written by AI, a feature lead is worth weeks, maybe a few months. Then a competitor with the same AI access closes the gap. You can still get ahead on features. You just cannot build a predictable, compounding growth engine on top of something that erases in a sprint.

The moats Verna says still hold:

  • Hardware. Still genuinely difficult and capital-intensive to build.
  • Network effects. Always hard to create. Once real, they compound on their own.
  • Proprietary data. The kind competitors cannot replicate regardless of how good their models get.
  • Security and compliance. Slow, expensive, and worth it for exactly that reason. The switching cost is real.
  • Brand. "Brand is back, baby" is how Verna put it. When everyone can build the same product, the relationship with the customer is what's left.

Notice what's not on that list. SEO and SEM are absent, and Verna is deliberate about that. When AI-generated content is everywhere and AI is eating the top of the search funnel, channel strategies built on organic and paid search are more fragile than they looked three years ago.

For operators building on LinkedIn, that absence is worth noting. Earned authority is how you build brand without a media budget, and it doesn't evaporate when a competitor matches your feature set.

The flat org is not a culture gimmick

Lovable runs with no internal titles. The reason is structural, not philosophical. When everyone is expected to actually build, titles become noise. The signal is what shipped.

A few mechanics Verna describes that make the velocity real:

  • A #shipped Slack channel where the day's production releases pile up. Multiple ships a day, not a sprint cadence.
  • No separate layers of approval between an idea and production. The IC ships.
  • Leaders who want to stay in leadership need to stay in the work. Coordination without building is not a long-term job at Lovable.

The org design matters for operators outside Lovable too, because it names a problem a lot of teams are quietly carrying. The traditional reward for being a great individual contributor has always been a promotion into management. Management is a different job. Most people were not built for it, and a lot of them know it.

Verna's advice to founders looking for this kind of person: go find the leaders who are quietly miserable in coordination roles and ask if they want to build again. She says a surprising number are ready to say yes, because they see it as a way to fall back in love with the work.

PMF is not a finish line

Even approaching half a billion in revenue, Verna says Lovable is still "on the product market fit treadmill." The category is moving fast enough on both the technology and customer sides that they feel like they have to recapture PMF every month.

This reframes something a lot of growth operators get wrong. PMF is treated as a milestone you cross and then leave behind. You raise the Series B, you scale the team, you shift to execution mode. Verna's point is that in AI-native categories, scale doesn't let you slow down. It raises the stakes on velocity, because the window between "we have PMF" and "the category has moved" is shorter than it used to be.

The same logic applies to content strategy. The signal in comments and engagement tells you whether your angle still fits the moment, and ignoring it is how you get caught flat when the category shifts.

What this means if you're not Lovable

The $400M ARR number is real and the org is genuinely unusual. But most of what Verna is saying translates directly to founders and operators at much smaller scale.

The moats that hold (brand, network, proprietary data) are available to a solo operator. A founder with a strong LinkedIn presence has brand. An operator who shows up consistently in the right comment sections has a network effect in their niche. A consultant who publishes observations from actual client work has proprietary data that a competitor with the same AI access cannot replicate.

The org point translates too. The operators with the highest LinkedIn conversion tend to do the IC work themselves, writing their own comments, building their own lists, staying close to what's working. Delegation without a feedback loop produces coordination overhead, not velocity, regardless of team size.

For a worked example of what lean, high-conviction LinkedIn presence looks like in practice, the breakdown of Kyle Poyar's 107K strategy covers the mechanics in detail. The founder-led brands LinkedIn inbound piece is the complementary frame on why the approach compounds.

Verna's talk is the macro argument. The question for most operators is what it changes about what you do Monday morning. Stop betting on features as your differentiation story, start building the things AI can't clone, and ship something before the week is out.

See what your content is signalling.Get a content audit of your profile, plus a daily feed of the conversations your expertise fits.

Frequently asked

Lovable achieved more than $2M in ARR per employee by rejecting traditional org structures. Every team member does IC work and ships to production directly. There are no internal titles and no layers of approval separating an idea from a production release. The model only works because leaders, including Head of Growth Elena Verna, stay builders rather than pure coordinators.