Why Retention Beats Acquisition in Marketplaces — And How to Build a Growth Model That Reflects That

Dan Hockenmaier, Head of Strategy and Analytics at Faire and former Director of Growth at Thumbtack, was interviewed on Lenny's Podcast about marketplace growth strategy and growth modeling. He covered how to build a growth model from scratch, why retention is more important than

·4 min read·Source: Lenny's Newsletter

What Happened

Dan Hockenmaier, Head of Strategy and Analytics at Faire and former Director of Growth at Thumbtack, was interviewed on Lenny's Podcast about marketplace growth strategy and growth modeling. He covered how to build a growth model from scratch, why retention is more important than acquisition, how to measure marketplace health, and when it makes sense to layer SaaS tools onto a marketplace. The conversation draws on his direct experience scaling two major marketplaces and teaching growth frameworks at Reforge.

Why It Matters

Most early-stage marketplace founders treat growth as an acquisition problem — more supply, more demand, more spend. Dan's framework flips this. He argues that a growth model forces you to see your marketplace as a system of interconnected inputs, not isolated campaigns. The deeper signal here is structural: if your retention is broken, acquisition spend accelerates your burn without building a real business. Marketplaces that win do so because both sides keep coming back — not because they constantly re-recruit them, and operators increasingly rely on AI tools for online sellers to strengthen those retention loops on both sides.

Marketplace Insight

Supply: Adding more suppliers to a leaky marketplace doesn't improve liquidity — it adds cost. Suppliers who don't transact quickly become disengaged and leave, which quietly degrades your supply quality over time. Retention on the supply side is as important as recruitment.


Demand: Demand is frequently under-resourced in early marketplaces. Founders often assume demand will follow supply. Dan's framing challenges this — demand-side retention determines whether the marketplace has real PMF or just novelty.


Liquidity: A growth model helps you identify where liquidity is actually breaking down. Is the issue match rate? Repeat purchase rate? Time-to-first-transaction? Without a model, founders optimize for vanity metrics instead of the real bottleneck.


Trust: Early user experience drives retention, which drives trust. If a buyer's first transaction goes poorly, no amount of supply-side investment recovers that. The first interaction is a trust-setting event, not just a conversion event.


Growth: Sustainable marketplace growth compounds through retained users, not just new ones. A model that accounts for retention makes this visible — and makes the cost of poor retention undeniable.


Onboarding: The early user experience is the highest-leverage retention intervention available. Founders who treat onboarding as a logistics problem miss its role as the primary driver of whether users return at all.


Monetization: Dan's work at Reforge on the monetization track points to a key insight — SaaS tools layered onto a marketplace can increase supplier stickiness and switching costs. This is a monetization move, but it also serves retention. Timing matters: adding SaaS too early distracts from liquidity; too late and you've missed the lock-in window. Understanding marketplace launch best practices can help founders sequence these decisions more effectively from the start.

What This Means for Marketplace Founders

Non-technical founders often avoid building growth models because they assume it requires data infrastructure or engineering support. It doesn't — at early stage, a growth model can be a spreadsheet that maps your key inputs: new supply added, supply activation rate, supply retention, new demand, demand repeat rate, and match rate. The act of building it — even crudely — forces you to identify which lever actually moves your business. Without it, you're making resourcing decisions based on intuition rather than system logic. The other implication is prioritization: if your retention is below benchmark, fixing it should come before scaling acquisition spend. Spending to acquire users into a broken experience is one of the most common and costly mistakes in early marketplace building, and applies equally whether you're following community marketplace best practices or running a purely transactional model.

Actionable Takeaways

  • Build a basic growth model in a spreadsheet before scaling any channel. Map: new users acquired → activation rate → retention rate → repeat transaction rate. This shows you where the real leak is.
  • Audit your early user experience on both sides separately. Ask: does a new supplier get their first transaction within a defined window? Does a new buyer return within 30 days? If not, fix that before increasing supply or demand volume.
  • Don't neglect demand. Identify your demand-side retention rate explicitly. If you don't know it, measure it before your next supply push.
  • Treat the first transaction as a trust event, not just a conversion. Design onboarding and matching to maximize the quality of the first interaction — not just its speed.
  • If you're considering adding SaaS tools for your supply side, evaluate it as a retention and switching-cost mechanism first, not a revenue line. Ask: will this make suppliers more dependent on the platform before you add it?
  • If your marketplace operates in a fragmented B2B category, Dan's framework suggests this is a structural advantage — fragmentation means suppliers need aggregation more. Use this to justify supply-side investment early.
  • Source: Lenny's Newsletter