Estuary is a right-time data company building infrastructure that delivers both streaming and batch capabilities — so companies can move and transform data at whatever latency their use case demands, from millisecond-level real-time pipelines to traditional batch analytics. With a growing enterprise customer base and NRR at 150%, Estuary is expanding beyond its PLG roots to go upmarket. In a recent episode of BUILDERS, we sat down with David Yaffe, Co-Founder and CEO of Estuary, to learn how the company was built from internal tooling his previous team couldn't source externally, why they deliberately priced to leave money on the table, and how AI is collapsing the historical divide between the two buyer personas that defined the data infrastructure market for a decade.
Topics Discussed:
How Estuary was built from internal infrastructure David's team couldn't find anywhere else
Why the early GTM deliberately led with a use case that undervalued the product — and why that was the right call
How Estuary hit 150% NRR without a CSM team
The pricing decision to actively lower prices to unlock larger use cases
How AI has reshaped Estuary's ICP by removing the divide between software engineers and data engineers
How to identify tire-kickers early and stop wasting cycles on deals that won't close
GTM Lessons For B2B Founders:
Lead with the most repeatable sale, not the most impressive one. Estuary's early motion focused entirely on the analytics use case — moving data from source to warehouse. David was explicit that this undersold the platform: it's a batch workflow that didn't touch Estuary's real technical differentiation in streaming. He pursued it anyway because it was legible, budgeted, and repeatable. The modern data stack wave meant buyers already had line items for it. For founders with technically deep products, the instinct to lead with full capability is usually wrong early. Find the use case that maps to an existing budget category and build volume there first.
Your first buyer doesn't need to be your best buyer — design for internal spread. Estuary routinely lands with a marketing or analytics team that has zero interest in streaming or low-latency data. What converts those small deals into meaningful revenue is what happens after: that team hears about an internal use case that does require real-time data, and they become the internal evangelist. David described this as a core part of how NRR compounds. The implication: make sure your product is legible enough that a non-technical champion can describe its value to a team they've never worked with.
Price to accelerate adoption, not to extract maximum value upfront. Estuary has deliberately kept prices below what the market might bear, and has lowered prices at least once specifically to stimulate larger use cases — accepting a short-term revenue hit to do it. David's reasoning: customers who feel they're getting a fair deal don't build internal replacements or evaluate alternatives. At scale, he described watching usage hit a ceiling and wanting to get ahead of the moment when a customer thinks the platform is too expensive. Founders building usage-based or expansion-driven businesses should ask whether their pricing is a growth accelerant or a growth ceiling.
//
Sponsors: Front Lines — We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. www.FrontLines.io
The Global Talent Co. — We help tech startups find, vet, hire, pay, and retain amazing marketing talent that costs 50-70% less than the US & Europe. www.GlobalTalent.co
//
Don't Miss: New Podcast Series — How I Hire Senior GTM leaders share the tactical hiring frameworks they use to build winning revenue teams. Hosted by Andy Mowat, who scaled 4 unicorns from $10M to $100M+ ARR and launched Whispered to help executives find their next role.
Subscribe here: https://open.spotify.com/show/53yCHlPfLSMFimtv0riPyM
Otros episodios de "BUILDERS"



No te pierdas ningún episodio de “BUILDERS”. Síguelo en la aplicación gratuita de GetPodcast.








