Background
Sarah Tavel is a general partner at Benchmark. We cover Sarah's insights from the food delivery & space rental sectors, building marketplaces, and the future of the consumer social sector.
Date
July 4, 2020
Episode Number
168
Tags
Venture Capital
Principles & Lessons:
- Liquidity, not GMV, is the foundation of marketplace defensibility — and liquidity quality is shaped as much by trust and experience design as by supply volume. Sarah distinguishes between shallow growth and meaningful liquidity: “Postmates went headstrong into San Francisco… built a lot of GMV… [but] did they build a lot of liquidity?” Liquidity means the marketplace reliably facilitates transactions, which requires more than inventory. GOAT, for instance, added authentication not just to protect users, but to create trust that activated otherwise inert supply. Trust mechanisms (e.g., certifications, reputation, search rankings) are part of the product design that shapes market thickness and retention — they’re not secondary features. The lesson is that defensibility emerges not from gross metrics but from systemic reinforcement of value creation and transaction reliability.
- Network effects are inert until product quality catalyzes them into tipping loops — which must be explicitly designed and reinforced. Tipping isn’t magic; it’s engineered. Sarah defines it as the moment when “the market goes from you having to do all the work… to it actually starts to tip towards you.” But that only happens if the underlying product creates reinforcing loops. She outlines two key types: growth loops (e.g., viral referrals, collaborative carts like Caviar’s) and retention loops (e.g., quality filtering via reputation or badges). The structure of these loops must be discovered, not assumed. It’s not enough to add social features or ratings — the design must produce asymmetry: better actors should get more demand, and the system must get stronger over time.
- Atomic units of supply define market structure — shifting the unit can reconfigure who wins. This is a unifying idea across several examples Sarah gives: Postmates added delivery logistics, Airbnb created new inventory categories, Booking.com lowered take rates to unlock independent hotels. These weren’t just margin plays or product extensions — they redefined what “supply” meant. Sarah emphasizes that “they figured out a different atomic unit of supply, which let them leapfrog the liquidity.” The principle is that markets are structured by their ontology — by what entities are legible and tradable. Redefining the unit of participation can change who can enter, what liquidity looks like, and how power concentrates.
- Starting with hyper-focused, small markets isn’t a concession — it’s the optimal strategy to maximize the probability of network effects. Sarah is emphatic: “we don’t really care about how big the initial market is… there’s actually something really, really right about focusing on something really small.” It’s not just about iteration speed — it’s about increasing the probability that early cohorts converge into usable network density. Pinterest, Uber, Etsy, and Hipcamp all began with tight verticals or geographies. This focus reduces complexity, allows you to shape a specific identity, and — crucially — creates the perception of vitality. “If it doesn’t feel alive, it’s a big problem,” as she echoes Bill Gurley. The lesson is epistemic: local truth matters more than hypothetical total addressable market.
- Accruing benefits and mounting loss are necessary but insufficient for retention — their effectiveness depends on friction asymmetry and switching cost design. Sarah explains that the best products create compounding value for users (“accruing benefits”) and make leaving costly (“mounting loss”). Pinterest’s pinning system deepens value over time: “you’re also leaving part of yourself on Pinterest… a new recipe… a place to go.” But she acknowledges this can fail, as in Evernote’s case — when Notion made switching easy and added collaboration, users left. This reveals that switching costs are not moats unless they are both hard to replicate and hard to bypass. Friction must be asymmetrical: beneficial for users but difficult for rivals to unwind. Without that, even sticky-seeming products are vulnerable.
- Product energy must be channeled toward a core action — otherwise, the system dissipates user effort without strengthening itself. Sarah introduces the idea that every user interaction spends “energy,” and that systems must channel that energy into actions that “create the most value for the system.” Pinterest had many features, but pinning was the core action — it correlated most with retention, enhanced the discovery graph, and embedded user intent. The takeaway is to treat every design decision as a question of systemic reinforcement: does this action amplify compounding effects, deepen user identity, or build value for others? If not, it’s noise. “Everything else is empty calories.” This concept parallels conservation principles — only actions that feed the flywheel are net-positive.
- Digital business design must optimize not just for transaction, but for the reduction of search and coordination costs — which is the deeper value creation layer. Patrick proposes and Sarah affirms that reducing search costs is a central function of marketplaces: “yeah, I absolutely think that whatever you can make easier… you're making a more efficient transaction.” But she makes a further point — reducing friction also improves liquidity quality. That is, it's not only about speed or convenience but about making the right matches more likely. Tools like reputation systems, smart search rankings, or personalized discovery don’t just remove friction — they reconfigure incentives and outcomes. So designing liquidity means designing the epistemic interface — the part where the system helps users know what to do.
- Data is a powerful tool only after product-market fit — before that, over-indexing on metrics can entrench the wrong optimization logic. Sarah describes data use in three stages: (1) early-stage: helpful but potentially misleading, where “data isn’t going to show you the way… it’s about first principles”; (2) product-fit phase: focus on identifying and tracking the one or two metrics that actually correlate with value (e.g. core action, retention); (3) scaling phase: when founder intuition no longer scales, and the organization must “build the muscle of learning how to make decisions with data.” She cautions against ego-driven metrics: “if you end up connecting your ego… to a metric that isn’t actually the most important… it’s so dangerous.” The epistemological point is that data is not knowledge — only structured hypotheses tied to system outcomes can be.
Transcript
‣
‣
‣
‣
‣