How Michel Tricot Raised $185M Before Finding Revenue Model | Airbyte

How Michel Tricot Raised $185M Before Finding Revenue Model | Airbyte

Episode 18 · March 2, 2026

Bottom Line Up Front

Michel Tricot, co-founder of Airbyte, raised $185 million and achieved a unicorn valuation before fully cracking monetization. This episode reveals how he built a community-driven open-source data infrastructure company that hit $1M ARR in just 4 months after launching their enterprise product. Learn about pivoting during COVID, the 'Magic Wand' framework for idea validation, and the critical difference between project market fit and product market fit.

Key Facts

Total Funding Raised:
$185 million(Michel Tricot)
Time to $1M ARR:
4 months(SME product launch)
Customer Discovery Calls:
200+ calls across different ideas(Michel Tricot)
User Growth Period:
Thousands of new users weekly in 2021(Michel Tricot)
Launch Date:
November 2020(Airbyte open source)

What if you could raise $185 million with zero revenue? Michel Tricot did exactly that by building an open-source community so strong it overwhelmed his engineering team.

Key Facts

  • Total Funding Raised: $185 million (Michel Tricot)
  • Time to $1M ARR: 4 months (SME product launch)
  • Customer Discovery Calls: 200+ calls across different ideas (Michel Tricot)
  • User Growth Period: Thousands of new users weekly in 2021 (Michel Tricot)
  • Launch Date: November 2020 (Airbyte open source)

The COVID Pivot That Changed Everything

Michel Tricot pivoted Airbyte from a failed marketing attribution product to data infrastructure after COVID killed marketing budgets, using customer discovery to find the real problem.

When COVID hit in March 2020, Michel Tricot faced every founder's nightmare. His marketing attribution startup had just launched, gaining decent traction with design partners, but suddenly every marketing team's budget was frozen. Companies went from 'growth at all costs' to survival mode overnight.

Rather than persist with a dying market, Tricot made a crucial decision. He took a walk with his co-founder and asked the hard question: 'Are we actually building a product that is so vital for them that even when COVID hit, our product is still necessary?' The answer was no.

This led to three months of intensive customer discovery. Tricot and his team conducted over 200 calls across different ideas, from fintech to healthcare data tokenization. They explored everything, but kept returning to the same problem: data integration was broken everywhere they looked.

"Every founder wants to have an explosion when they release. But what really happened is that we launched the product maybe a month before COVID hit... every single marketing team across the US, they just got no budget anymore, like frozen budget, and they were basically all laid off." — Michel Tricot
"I don't care about this type of funnel metric. What matters is just, are people paying us at the end of the day? And are we actually building a product that is so vital for them that even when COVID hit, our product is still necessary? And that was not the case." — Michel Tricot
  • Marketing teams lost budgets overnight when COVID hit
  • Conducted 200+ customer discovery calls across multiple ideas
  • Every conversation led back to data integration problems
  • Team included three exceptional engineers from previous company

The Magic Wand Framework for Idea Validation

Tricot developed the 'Magic Wand' framework, asking potential customers what their ideal solution would be if they had unlimited power, revealing deeper needs beyond tactical problems.

During their extensive customer discovery phase, Tricot developed what he calls the 'Magic Wand' framework. Instead of getting stuck in tactical problems people were facing, he would ask a simple but powerful question: 'If you had all the power in the world and you could make a wish, what would it be?'

This approach helped separate surface-level complaints from fundamental needs. Tricot found that people could easily describe tactical issues, but the magic wand question revealed the transformational outcome they really wanted. The key signal was whether someone could rephrase his proposed solution in their own words - indicating genuine understanding and interest.

The framework extends beyond customer discovery. Airbyte continues using it internally for product decisions. As Tricot explains, it's about understanding the feeling and interpretation behind customer needs, not just the functional requirements.

"If you had all the power in the world and you could make a wish, what would it be? And in general, that's always what guided us in terms of was it a good idea? Was it not a good idea?" — Michel Tricot
"I think for me it was, was the person in front of me able to rephrase what I said with their own words... that is so important that people just want to continue to talk to you. Just to understand, is this solution going to just solve my deep problem?" — Michel Tricot

Building Community Through Open Source Strategy

Airbyte launched as open source in November 2020 to solve the 'build vs buy' dilemma, removing barriers for engineers who needed data integration solutions but wanted control.

Tricot chose open source for a strategic reason: it eliminates the psychological barrier of the 'build vs buy' decision. When engineers need to move data from Salesforce to Snowflake, they typically search Google for scripts or cheap solutions to start quickly. Open source removes both the build burden and the buying friction.

The team focused heavily on vanity metrics initially - GitHub stars, contributors, and community size. While Tricot didn't care about being popular, he understood these metrics create trust signals. 'If there is one star, yeah, whatever, it's just some random guy that is building that thing. It's never going to be maintained,' he explains.

Their go-to-market strategy targeted individual contributors, not executives. They engaged data engineering communities on Reddit and Hacker News, gave demos to community groups, and built a Slack community to capture interested users. This approach worked because they were solving a universal pain point that every data professional faced.

Never miss a founder's PMF story

Subscribe to The PMF Show
"Open source is very good when it comes to the build versus buy because, in a way, it removes the build, but it also removes the buy. So as an engineer, you just take open source, you don't have to build, you don't have to buy, but you get the value out of it." — Michel Tricot
"We're very focused on vanity metrics on GitHub... I don't care about how many stars I have, but I know that whenever I look at a project... I look at these numbers... because I want to see that this is a real project." — Michel Tricot
  • Open source removes both 'build' and 'buy' barriers for engineers
  • Focused on GitHub stars and contributors as trust signals
  • Targeted individual contributors, not executives or directors
  • Built Slack community to maintain engagement beyond initial posts

When Success Becomes a Problem: Community Overwhelm

Airbyte's community grew so rapidly in summer 2021 that their 10-person team couldn't build products anymore, spending all time reviewing contributions and answering questions from thousands of weekly new users.

Success came with an unexpected challenge. By summer 2021, Airbyte's community exploded almost overnight. With only ten people on the team, they suddenly couldn't continue product development because the community demands were overwhelming. Thousands of new users joined weekly, all asking questions and requesting features.

The problem intensified when Airbyte released their Connector Development Kit (CDK) in April 2021, making it easy for anyone to build connectors. Contributions flooded in, requiring constant review of pull requests and fixes. The team became victims of their own success.

Three factors drove this explosion: a viral Hacker News post sharing their fundraising slides, the CDK release enabling easy contributions, and their Series A funding providing credibility. Users felt confident betting on Airbyte because the team was funded and would be around long-term.

"We actually hit a good problem to have but we hit a massive wall over the summer of 2021. Where the team was very small. We had, what? Maybe ten people in the team and suddenly we were unable to build any type of product. The community just blew up overnight." — Michel Tricot
"Everyone was using it. Everyone was asking us questions. There was a lot of feature asks. There was a lot of contribution on the connector side. So we had to review all these PRs. We had to review all these fixes and we just couldn't continue to work on the product anymore." — Michel Tricot

Project Market Fit vs Product Market Fit: The Revenue Reality

Airbyte had strong project market fit with their open source tool but needed to build product market fit through paid offerings, launching cloud hosting and self-managed enterprise versions.

Tricot learned the crucial distinction between project market fit and product market fit. While Airbyte had massive usage and community engagement, they needed to prove people would pay for enhanced versions of their solution.

In 2022, they started building their cloud product, which launched in early 2023. This fully-hosted version grew well, reaching $1M ARR within the first year. However, some large users resisted cloud because they didn't want Airbyte to see their data, preferring the control that open source provided.

This feedback led to their self-managed enterprise (SME) product - a paid version with enterprise features that customers could deploy on-premises. The SME product hit $1M ARR in just four months, despite being 'very bare bones' at launch.

"Project market fit and product market fit are two different things and that's when we started to build the cloud product that we released at the beginning of 2023." — Michel Tricot
"At the beginning of 2024, the product was very bare bones, and yet we were able to generate a pretty good amount of revenue in very little time... if you're solving a real pain, people will adopt your solution even if it's incomplete." — Michel Tricot
  • Cloud product reached $1M ARR within first year of launch
  • Enterprise customers wanted data sovereignty, not cloud hosting
  • SME product hit $1M ARR in just 4 months with minimal features
  • Later killed SME for a simpler product offering better sovereignty

Managing Unicorn Expectations Without Revenue Pressure

Tricot handled the $1B+ valuation pragmatically by focusing on solving real problems at scale, spending efficiently, and working with investors experienced in open source business models.

Despite raising $185 million and achieving unicorn status, Tricot never celebrated the valuation milestone. His pragmatic approach focused on fundamentals: solving real problems for a massive market. 'Every single company in the world needs to do something with data. It doesn't matter what industry they're in, they all have the same problem,' he explains.

The key was working with investors who understood open source businesses. Partners like Accel, Benchmark, Thrive, Coatue, and Altimeter had all invested in successful open source companies before. They understood the typical lag between community growth and revenue generation, followed by rapid monetization.

Tricot's strategy was spending efficiently while having enough capital to discover product-market fit over time. With strong brand awareness and community engagement, he believed reaching the valuation was inevitable - it would just take time. The infrastructure nature of the product and standard status in the industry provided long-term confidence.

"I'm very pragmatic. Which is, yes, it's great. You have a big valuation, but I never celebrated having a big valuation. I never called myself a unicorn company because I do not care about that. What I know, though, is the problem we're solving is real, and it's just going to continue to grow." — Michel Tricot
"The investors we're working with are also very familiar with open source... They know that there is a bit of a lag when you have revenue, but then you have the hockey stick." — Michel Tricot

Airbyte Product Timeline and ARR Achievement

ProductLaunch DateTime to $1M ARRKey Features
Open SourceNovember 2020No direct revenueCommunity-driven, free data integration
CloudEarly 2023Within first yearFully hosted, managed service
Self-Managed EnterpriseLate 20234 monthsOn-premises deployment, enterprise features

Frequently Asked Questions

How did Michel Tricot raise $185 million before having significant revenue?

Tricot built massive community engagement and usage through open source, demonstrating strong project market fit. Investors understood the open source business model timeline, where community growth precedes monetization, and believed in the universal need for data integration solutions.

What is the Magic Wand framework for startup validation?

The Magic Wand framework asks potential customers: 'If you had all the power in the world and you could make a wish, what would it be?' This reveals transformational needs beyond tactical problems and helps validate whether customers truly understand and desire your proposed solution.

Why did Airbyte choose open source over a traditional SaaS model?

Open source eliminated the 'build vs buy' dilemma for engineers who needed data integration. It removed both the development burden and procurement friction, allowing engineers to adopt Airbyte immediately while maintaining full control over their data pipelines.

What's the difference between project market fit and product market fit?

Project market fit means people use your free solution extensively, while product market fit means they'll pay for enhanced versions. Airbyte had strong project market fit with their open source tool but needed to prove product market fit through paid cloud and enterprise offerings.

Michel Tricot's journey with Airbyte demonstrates that massive funding success can come from solving universal problems through community-driven open source strategies. The key is focusing on real customer pain over perfect products. Listen to the full conversation on The Product Market Fit Show for more insights on building infrastructure startups.

Want more founder stories like this?

Subscribe to The Product Market Fit Show for weekly episodes.

Subscribe Now