How Hedra Hit $10M+ ARR in Months With Zero Outbound

Michael Lingelbach dropped out of his Stanford PhD to build Hedra, a generative video platform that signs enterprise contracts every few days — without a single outbound sales rep. His path from a million free users to eight-figure ARR holds hard-won lessons every founder needs to hear.

Key Facts

• Time to $1M ARR: Five to six months after launch (Michael Lingelbach)
• V2 ARR milestone: Eight-figure run rate shortly after V2 launch (Michael Lingelbach)
• Enterprise deal velocity: Signing a contract every couple of days with zero outbound sales (Michael Lingelbach)
• V1 first-month users: Approximately one million users, majority free (Michael Lingelbach)
• Team size at Series A: 23 people (Michael Lingelbach)

Why Free Users Are a False Signal for AI Apps

Free signups don't prove product-market fit. The people who use something for free are often a completely different group from those willing to pay. Until you put a paywall in front of a real pain point, you don't know what you actually have.

Hedra's V1 launch in June 2024 generated roughly a million users in its first month — a number almost any founder would celebrate. Michael Lingelbach didn't. 'Free users are often a negative signal,' he told host Pablo Srugo. 'The people who are willing to pay for software are sometimes a totally different group than the people who are willing to use it for free.'

The team added features in response to user requests, used a stack-ranked issue system, and grew to $1M ARR within six months. But Lingelbach felt something was missing. He hadn't identified the high-willingness-to-pay ICP inside the sea of free users. He was doing bottoms-up thinking — responding to feedback — without the tops-down thinking of asking what core workflow problem he was actually solving.

His advice for any early-stage founder is direct: put up paywalls early and watch who actually pays. 'I'd rather solve a problem that a few people cared a lot about and were willing to pay a really high amount for,' he said. 'Is this something that people will pay $20 bucks a month for at minimum? Or is this something where you throw up a $5 paywall and they won't?' That question separates real demand from novelty.

"Free users can be really false signal. Just because someone uses it for free doesn't mean it's something that solves a core pain point." — Michael Lingelbach

"The people who are willing to pay for software are sometimes a totally different group than the people who are willing to use it for free." — Michael Lingelbach

The Creator-Seeded Launch Playbook That Beat Paid Influencers

Hedra's viral growth came from giving early access to creators before launch — not from paid influencer deals. The formula: onboard creators manually, let them make real content, and launch simultaneously. Both V1 and V2 used this approach with no influencer payments.

With no marketing budget and no prior launch experience, Lingelbach ran a four-day sprint before V1 — ten hours a day onboarding creators onto the platform, manually adding them to a database and teaching them how to use the tool. 'We didn't pay them or anything,' he said. 'We're gonna launch at this time, make some content.' The result was mass virality on day one.

For V2, the team was more organized — they'd hired a product marketing lead — but the core strategy was identical. 'Our position has been just make something good and then put people on it,' Lingelbach explained. 'They should talk about it if it's good. And if it's not good, don't launch it.' He noted there is an existing playbook of paying a few hundred influencers to retweet a launch, but Hedra deliberately avoided it.

The distinction matters for budget-constrained founders. Paid distribution can generate impressions; authentic creator content generates behavior change. Channels using Hedra — like the AI podcast channel that reached hundreds of millions of views — became proof points that the tool worked, not just ads claiming it did.

"Just make something good and then put people on it. They should talk about it if it's good. And if it's not good, don't launch it." — Michael Lingelbach

• Identify 10-20 creators aligned with your use case before launch day
• Give early access in exchange for organic content — not paid posts
• Coordinate a simultaneous launch window so social signals cluster
• Use your own product to make the launch hype video

When to Kill Features and Rebuild Your V2

If you're asking whether you have product-market fit, you don't. Lingelbach paused growth on a functioning product generating real revenue because it solved a technology need — not a workflow need. The V2 rebuild took months and was the right call.

Hedra V1 was a focused avatar generator. It worked, it monetized, it grew. But Lingelbach kept running into the same problem in sales calls and user interviews — people were using Hedra alongside other tools because it only solved one part of their workflow. 'Being fundamentally just an image to avatar workflow without anything else just was not solving a fundamental need,' he said. 'It was solving a technology need.'

He made the call to stop shipping features and rebuild from the ground up — a V2 with asset management, multi-model support, image generation, and a Figma-like studio UX. Growth slowed. 'That was the kind of hard call I had to make,' Lingelbach said. 'It's worth sacrificing a little bit of growth now to build something that's going to grow a lot more in the future.' He credits a quote from another founder for crystallizing the decision: 'If you are asking whether or not you have product market fit, you don't have product market fit.'

The rebuild was messy — a co-founder departure, shifting MVP goalposts, engineers building while designs changed. But the V2 launch drove an immediate jump to eight-figure ARR and triggered inbound enterprise contracts the day after launch. The plateau was worth it.

"If you are asking whether or not you have product market fit, you don't have product market fit." — Michael Lingelbach

"I felt like there was an insurmountable gap between solving the technology need and the workflow need without me just doing a lot more work." — Michael Lingelbach

The Prosumer-to-Enterprise GTM That Closes Deals Without Outbound

Hedra's enterprise pipeline runs entirely on inbound. The prosumer product creates category awareness; enterprises discover it through their own employees using it. With a clear content-creation use case, enterprise deals close without a sales team reaching out first.

Lingelbach's original thesis was a prosumer-to-enterprise wedge: build something creators love, then offer a professional-grade version that companies will pay for. 'You really want to find a product or a market where there's people that are using you casually, but then there's a professional upsell version of that,' he said. Social media content and corporate podcasting gave Hedra exactly that dual audience.

Today, Hedra signs enterprise contracts every couple of days — all inbound. Lingelbach is only now hiring its first account executives, because the volume of inbound calls has exceeded what he can personally handle. The GTM motion is product-led at the top of the funnel, with sales layered in to close and expand deals that are already warm.

The key to making this work was choosing use cases with a natural professional tier. Faceless TikTok channels and brand marketing content live on the same workflow — one pays $20/month, the other signs six-figure contracts. Building a single platform that serves both without forcing either group to compromise is what makes the wedge defensible.

"We sign an enterprise contract every couple days now, pretty big ones too, and that's without outbound sales." — Michael Lingelbach

"You really want to find a product or a market where there's people that are using you casually, but then there's a professional upsell version of that." — Michael Lingelbach

• Choose a market with casual and professional versions of the same workflow
• Let the prosumer product generate enterprise awareness organically
• Hire AEs only after inbound volume exceeds founder bandwidth
• Price to match professional pain — not consumer novelty

Early Hiring: What the First 10 People Should Look Like

Seed-stage teams need a product-visionary founder, anchoring engineering and research leads, a strong full-stack engineer, a designer, and — critically — a talent lead. Hiring vibes-only without process costs months of compounding speed.

Lingelbach's early hiring was 'very vibes based and quite messy' by his own admission. He didn't know what an ATS was, hadn't run an interview loop, and underestimated how hard it is to recruit when you have no money or track record. The lesson he now gives founders is specific: bring in a talent lead earlier than feels necessary.

'People should consider bringing on a talent person if you're venture-backed really early on,' he said. 'It can really become a full-time job, even at the early stage.' He recently hired a head of talent from Niantic and credits it with materially improving how he spends his time. The same logic applies to product marketing and eventually sales — hire the function before you need it, not after you're drowning.

On ideal team composition: the best early hires have done a Series A-to-C stint — they've built on greenfield systems and know high-growth culture, but haven't gotten comfortable at scale. 'Ideally they were there at the beginning, but have that, like, are basically two-timers,' Lingelbach said. Fresh graduates are often what you get early, but experienced operators who've seen a hypergrowth company are what anchor the team.

"I'd say on that sort of budget, it's good to get to a team of 10. You can't have hands-off people in an early stage startup. It just does not work." — Michael Lingelbach

"Had I figured out how to accelerate hiring earlier, we would probably be where we are in at least half the time." — Michael Lingelbach

Hedra V1 vs V2: Product Strategy Comparison