Building the Product

I'm a solo technical founder. How do I MVP a two-sided marketplace when I need both buyers and sellers before it works at all?

A starting point

Don't build the marketplace, fake one side and hand-run the match. Pick the harder-to-get side (usually supply), recruit a tiny concentrated pool manually, and stitch demand to them with spreadsheets, DMs, and yourself as the matching engine. This chicken-and-egg problem is solved with a narrow niche and human hustle, not code: launch in one city or one category so liquidity feels real. This is a starting point, automate only the steps that break under repetition.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 2 link-checked

Read

✍️ Essay
✓ Link checked Free Intermediate

Why we picked it This is the canonical answer to your exact fear: you do not need both sides at scale, you need one tiny network that works. Chen (ex-Uber growth, now a16z) argues you win by nailing the smallest self-sustaining group first (one campus, one office, 5pm at one train station), then repeating it. As a solo founder, that reframes an impossible two-sided launch into one winnable, hand-run pocket of density.

The Atomic Network

From Lenny's Newsletter by Andrew Chen about 15 min read

  • Stop trying to fill a whole market. Pick the smallest group where the product is genuinely useful even with almost nobody else on it, and make that one network dense before expanding.
  • Early on, momentum beats scalability: launch stripped down, obsess over one atomic network, and only worry about repeatability once the first one clearly works.
  • Solving one side first is a feature, not a compromise: a working atomic network is what actually pulls the other side in, instead of you begging both sides at once.
Open lennysnewsletter.com →
📖 Book
✓ Link checked Paid Intermediate

Why we picked it If the essay is the sketch, this is the full map for getting a network-effect product off zero. Chen draws on his Uber years and interviews with the teams behind Airbnb, Tinder, Uber, Slack, and more to lay out a stage-by-stage playbook: cold start, tipping point, escape velocity, and the ceiling. For a solo founder staring at an empty marketplace, it is the most complete single reference on the exact problem you are describing.

The Cold Start Problem: How to Start and Scale Network Effects

From HarperBusiness by Andrew Chen about 368 pages

  • The 'hard side' of your marketplace (usually supply, the sellers) is the side you must win first and design the whole early product around.
  • Networks grow one atomic network at a time, so treat each city or niche as its own launch that has to reach density before you move on.
  • Getting to zero-to-one is a different job from scaling: the tactics that seed a cold network are not the ones that grow it later, and the book separates them stage by stage.
Open amazon.com →
✍️ Essay
Free Beginner

Why we picked it The permission slip to recruit users by hand, do things manually, and deliver 'insanely great' experiences to your first few customers. The cheapest, most honest way to validate demand is to go get it one person at a time.

Do Things That Don't Scale

From paulgraham.com by Paul Graham ~15 min read

  • Recruit your first users manually, don't wait for them to come.
  • A tiny group of users who love you beats a big group who like you.
  • Manual, unscalable effort early is a feature, not a failure.
Open paulgraham.com →

People also ask

What actually counts as an MVP, and what's the smallest one I can get away with? An MVP is the least you can build (or fake) to test your single riskiest assumption, not a shrunken version of your dream product. Ask 'what's the ... Beginner 3 resources → How do I decide which features to cut from v1? Cut everything that doesn't help you learn whether people want the core thing. Pick the one workflow your earliest, most desperate customers need a... Beginner 3 resources → How long should building an MVP take? Weeks, not months. If your MVP will take more than 4-8 weeks, your scope is wrong, not your timeline. Airbnb, Stripe, and Twitch all launched narro... Beginner 3 resources → Should I build an MVP at all, or can I validate without one? If you haven't talked to ~20-30 potential customers yet, don't build anything, you're not validating, you're procrastinating in code. A concierge M... Beginner 3 resources → How do I get my first users for the MVP? Recruit them by hand, one conversation at a time, this is the whole point of an early startup. Go to where your users already are, DM them, email t... Beginner 2 resources → What's the difference between an MVP and just a cheap, half-finished product? An MVP is a learning tool with a clear hypothesis attached; a cheap product is just a bad product. The point isn't to spend less money, it's to buy... Intermediate 2 resources →