Shree Bhanderi.

Interactive essay / marketplace simulator

Marketplaces are defined by density.

This essay deconstructs marketplace theory through live simulations. The goal is to sharpen the intuition needed to build a liquid, defensible, and durable business.

All models are wrong, some are useful. The numbers are indicative ranges drawn from operator frameworks and public case studies. Use these figures to visualize trade-offs and not to forecast a specific company's future.

Mental model

Atomic network

The smallest dense network that produces a happy transaction.

Local liquidity

Supply and demand only matter where they can actually match.

Lever library

Pricing, trust, matching, and tooling reshape the same system.

Product shape

Uber-like, Faire-like, and Care-like marketplaces need different defaults.

The Seven Moves

1. The Cold Start

Growth only compounds once you achieve a critical mass of early matches.

2. Liquidity

Ignore aggregate supply; the only metric that matters is local fill rate.

3. Take Rate

Your "rake" is more than revenue. It dictates how users behave on the platform.

4. Product Nature

Trust, frequency, and variety determine which growth levers actually work.

5. Business Model

Different structures (B2B vs. C2C) shift the friction from the buyer to the seller.

6. Leakage

High friction and high frequency create a massive incentive for users to take transactions off-platform.

7. Stage

Strategy is seasonal; your tactics must shift as you move from seeding to defending.

Module 1

Simulating the "Chicken and Egg" problem.

The Cold Start is a momentum problem. The same dollar of spend can either build a flywheel or vanish into a void, depending on how quickly you generate early matches.

Can the market produce enough early matches to retain both sides?

The cold-start problem is usually described as a paradox: buyers will not come without suppliers, and suppliers will not list without buyers. The operator version is harsher. Every failed search or empty calendar is a "tax" on your retention. The "Atomic Network" strategy works by shrinking the map: dominate a single neighborhood before trying to win a nation.

Scenario and levers

Start by choosing what kind of marketplace you are trying to seed. The sliders set the initial imbalance and the amount of paid help each side receives before the chart runs.

52-week cohort retention run

This is a cohort retention chart for what happens to a single wave of new customers, not a cumulative signup chart. The buyer and supplier lines show active people still willing to use the marketplace. They fall when too many people fail to match and churn faster than acquisition replaces them.

Active buyersActive suppliersCompleted transactions

Why can the graph go down?

In the simulation, suppliers who get no transactions are less likely to return next week, and buyers who search but cannot find a match also leave. The cold-start problem is visible when active users shrink even though you are still spending on acquisition or subsidies.

Marketplace cold-start simulation over timeWeek 0Week 52Active users and weekly transactions

Subsidy-dependent

54

The marketplace survives, but liquidity is still fragile and subsidy-dependent.

Module 2

The liquidity map.

A healthy average can hide a dying neighborhood. This map reveals why the location of your supply is as critical as the volume of your supply.

Is supply located where demand can actually use it?

Liquidity is the probability that a buyer can find what they want, and that a supplier can get used. The "Average Trap" is the quickest way to miss a failing market. For hyperlocal services like delivery or childcare, supply two miles away might as well be on the moon. The map turns fill rate into a geographic object so you can see why total counts can lie.

Controls

Red means demand cannot find usable nearby supply. Green means the relevant local radius is dense enough to transact.

Right now, 67% of demand lives in cells above the liquidity threshold. Radius changes who can match across nearby cells; distribution changes where supply starts.

Demand-weighted local liquidity

66%Global liquidity
67%Demand above threshold
1 cellMatching radius

Module 3

The take-rate Laffer curve.

The take-rate problem is nonlinear: extracting more can reduce supplier retention, buyer conversion, and ultimately platform revenue.

How much can the platform charge before behavior changes?

Take rate is not a passive accounting choice. A higher rake raises platform revenue per completed transaction, but it can also push suppliers to multi-home, raise buyer-facing prices, or move repeat customers off-platform. Gurley's 'rake too far' argument is that the best take rate is often below the maximum rate the platform can technically impose.

Product-nature sliders

Platform revenue curve

Take rate versus platform revenue curve10%20%30%40%50%optimum 34.5%Platform revenue
15.0%Current take
$718kGMV
8kTransactions
$108kRevenue

At this take rate, GMV is 72% of the maximum simulated GMV. Raising take rate by 5 points changes revenue by $18k and supplier churn is estimated at 21%.

Module 4

The product-nature radar.

Product nature predicts which marketplace patterns transfer. A services marketplace can look more like Care.com than Airbnb even if both are consumer brands.

Which marketplace patterns actually transfer to this product?

The essay's long catalogue of levers only becomes useful after you know what kind of product is being intermediated. Uber and DoorDash are high-frequency, local, time-sensitive, relatively standardized systems. Airbnb is lower-frequency, high-trust, and more heterogeneous. Faire is B2B, financed, and procurement-like. The radar makes those shapes comparable.

Select or configure

Frequent, local, perishable, standardized dispatch.

Implications

Invest heavily in

  • identity verification, escrow, guarantees, and dispute resolution
  • city-by-city density targets and under-served-zone incentives
  • algorithmic dispatch, dynamic pricing, and ETA guarantees

Closest analog

  • Uber: Frequent, local, perishable, standardized dispatch.

Key tension

  • compliance slows expansion but can become a moat once mastered

Biggest differences versus Faire

Locality: 75 ptsAOV: 64 ptsRelationship: 62 pts

Shape explorer

Uber product-nature radarFrequencyAOVUniquenessTime sensitivityTrust needLocalityFulfillmentRegulationRelationshipStandardizationUberComparison

Module 5

The business-model lens.

Business model is the transaction architecture: who brings supply, who owns demand, who pays, who has power, and which side is hardest to move.

What transaction architecture are we really designing?

Product nature tells you what is being exchanged. Business model tells you who is exchanging it and where power sits. A C2C resale marketplace, a B2B procurement marketplace, and a B2B2C delivery network can all be 'marketplaces,' but they have different hard sides, sales motions, trust burdens, take-rate headroom, and leakage risks.

Choose the architecture

C2C marketplaces coordinate many individuals on both sides. Supply is often unique or lightly professionalized, so search, reputation, and trust do much of the work.

Operator read

Hard side

Usually supply quality

Monetization

Seller fee, buyer protection fee, listing fee, or ads

Core question

Can enough trustworthy long-tail supply be made discoverable?

Biggest difference versus B2B

Sales cycle length differs by 62 points. This is where copied playbooks are most likely to break.

C2C value flow

Supply sideIndividual sellers
Platform roleTrust and discovery layer
Demand sideIndividual buyers

Compare C2C vs B2B

C2CB2B
Local density dependency46 / 38
Leakage pressure48 / 62
Platform price control38 / 44
Sales cycle length24 / 86
Supplier fragmentation92 / 74
Trust burden66 / 82

C2C playbook

  • Two-sided reputation and dispute resolution
  • Search, filters, collections, and saved alerts
  • Low-friction listing tools and buyer protection

Key tension

  • Too much friction kills listing volume; too little trust kills conversion.
  • Examples: eBay, Vinted, Poshmark, Craigslist

Module 6

The disintermediation risk calculator.

Leakage pressure rises when absolute fees are large, relationships repeat, and parties need to meet or communicate off-platform.

Will matched participants keep paying through the platform?

Leakage is the moment the platform creates a match but loses the transaction. Hagiu and Wright's framework is useful because it does not rely on vibes. If the fee dollars are meaningful, the same buyer and supplier are likely to repeat, and the work requires off-platform contact, the incentive to leave becomes structural. Babysitting, tutoring, home services, and care work all sit in the danger zone.

Risk inputs

Estimated leakage pressure

Moderate risk: invest in carrots

54

Score is based on Hagiu and Wright's three leakage drivers. It should be read as directional.

Leakage risk case-study scatter plotLow feeHigh feeRepeatCare.comWagHandyAirbnbUberUpworkFiverrFaireYou

Carrots that fit

  • insurance, guarantees, financing, and dispute resolution that justify the fee
  • multi-session scheduling, loyalty status, and saved relationship management
  • in-app messaging, location/status updates, and post-transaction support

Sticks that fit

  • conversion fees for taking a matched relationship off-platform
  • payment lock-in for ongoing work and off-platform policy prompts
  • contact-info redaction and messaging moderation before booking

Module 7

The marketplace stage diagnostic.

A marketplace stage is a pattern across fill rate, retention, growth, and multi-homing. Misdiagnosing the stage usually leads to the wrong lever.

What stage are we really in, and what should change next?

The same metric means different things at different maturity stages. In cold start, low fill rate is expected and the task is finding a small network that works. At tipping, the task is removing subsidy crutches and strengthening retention. At the ceiling, adding more supply may not help because the bottleneck has moved to product quality, trust, category expansion, or defensibility.

Self-assessment inputs

Diagnosis

Estimated stage

Traction

66% confidence
Cold start
Traction
Tipping
Escape velocity
Ceiling
Moat

What to do now

  • Instrument fill-rate by cell/category
  • Build trust and onboarding loops
  • Tighten the core interaction

What to stop doing

  • Adding categories that dilute liquidity
  • Treating aggregate fill rate as a single truth

Watch for next

  • Repeat fill rate and returning cohorts improving
  • Supply growth that follows demand rather than subsidies

Source backbone

What the essay is built from.

The simulations translate these sources into adjustable mental models. The source links are included so the simplifications remain inspectable.