Casey Winters on Why Marketplace Founders Play the Wrong Game Early On

Your Software Is Not Your Product

Most marketplace founders get this backwards from day one. They build elegant software. They obsess over UI polish. They pitch investors on features.

Casey Winters has seen this movie end badly too many times. At Grubhub, Pinterest, and Eventbrite, he learned that in marketplaces, the product isn't your platform—it's the supply.

The product in a marketplace is the supply, not your software. The software has to work to connect you to supply, but if supply doesn't do a good job, they're going to blame the marketplace because you recommended that person.

— Casey Winters

Translation: you can manually cobble together a terrible product experience as long as you're showing demand more selection than they knew existed and giving supply more customers than they had before. Grubhub's early product was "embarrassingly bad," but it indexed restaurant menus on Google and showed consumers way more delivery options than Yelp could. That was enough.

Tony Hsu at DoorDash delivered meals himself for a year. He wasn't validating software—he was validating liquidity. The only metrics that matter early: conversion rate between supply and demand, enough transactions that supply sticks around, and enough quality that demand comes back.

The Acquisition Loop You Need Before Launch

Winters won't invest in a marketplace unless the founder has already cracked the code on sustainable acquisition advantage. Not a hunch. Not a plan to "figure it out later." A real, proprietary loop.

He breaks down the usual suspects: sales (only works with fast payback), virality (asymptotes quickly after initial spike), paid (degrades over time unless network effects kick in), and content loops. The winners use unique data from supply to attract demand at near-zero marginal cost.

Grubhub aggregated restaurant menu data and owned SEO for food delivery searches. Fair, a B2B marketplace Winters advises, built free workflow software for brands to onboard existing retailers—then cross-sold those boutiques to other brands, slashing acquisition costs. Power, a clinical trials marketplace, created hyper-specific informational pages for people searching alternative treatments, matching them with pharma companies desperate for trial participants.

What I'm looking for is what is that data advantage or that acquisition loop that feels proprietary so that you're not going to just spend an incredible amount of money acquiring both supply and demand.

— Casey Winters

In 2024, you can't just raise a billion dollars every quarter and light it on fire in paid channels. Winters looks for founders who bake growth loops into the product hypothesis itself—not as a post-PMF bolt-on, but as part of the core unlock.

Why SaaS-to-Marketplace Transitions Almost Always Fail

The narrative sounds seductive: build a SaaS tool for supply, get tons of users, flip a switch and become a marketplace by adding demand. Winters calls this out as founder fantasy.

"Name an example in the last 10 years where that's actually worked," he says. The problem isn't strategic—it's cultural and operational. You've built a company optimized to service supply. Your team knows how to build SaaS features, not acquire demand. Your metrics, hiring, and roadmap all reinforce the wrong game.

At Eventbrite, Winters spent three and a half years as CPO trying to shift from a ticketing tool (where event creators brought their own audiences) to a true marketplace driving discovery. Even with a separate consumer business unit insulated from the SaaS team, progress was glacial. Eventbrite went from driving zero demand to roughly 30%—but cross-side network effects don't really kick in until you're past 50%.

The types of things they know how to build, the types of customer development they're used to doing are sometimes antithetical to building a marketplace. So what we did at Eventbrite for a few years is we actually created a separate business unit for the consumer team so they would not get sucked into the day-to-day trials and tribulations of the SaaS business.

— Casey Winters

The talent mismatch is real. Scaling a SaaS product requires different instincts than going zero-to-one on consumer discovery, search, and recommendation engines. You need ML teams, engagement loops, and data you haven't been collecting. It's a full reboot, not an expansion.

Liquidity Over LTV: Knowing What Game You're Playing

In 2013, the Grubhub marketing team panicked. Postmates and DoorDash were torching cash on AdWords, blowing up unit economics. Grubhub had been disciplined—six-month payback periods, soon to go public. Should they stretch to 12 months just to compete?

Winters had to remind them: those competitors weren't playing the profitability game. They were playing the liquidity game. DoorDash had drivers and restaurants sitting idle. Every dollar spent filling that idle capacity was an investment in proving the model, not optimizing LTV.

Grubhub raised $80 million before going public. DoorDash raised billions and lost money on every order early on. Both strategies can work—but only if you're honest about which game you're in and what the win condition is.

For early-stage marketplaces, the win condition is liquidity: high enough conversion between supply and demand, enough repeat usage, and a scalable way to pour fuel on the fire. Vanity metrics and polished dashboards don't matter. Neither does your beautifully designed app if nobody's transacting.

Pinterest faced a similar trap when international growth stalled. The US market was so big that every experiment optimizing domestic traffic by 1% felt more rewarding than taking Brazil from zero to one. CEO Ben Silbermann forced a hard reset: every team's goals would only count if they moved the needle in five non-US countries. US growth slowed. International took off.

The forcing function worked because leadership made the new game explicit. If you're stuck optimizing the old game, you'll never build escape velocity in the new one.