Marketplaces Do Not Start as Marketplaces

The clean marketplace pitch is almost always the same.

There are sellers on one side. Buyers on the other. The platform sits in the middle, takes a fee, and gets stronger as both sides grow. The slide looks obvious because it skips the only part that matters.

Why would either side show up first?

Andrew Chen popularized this as the cold start problem, and it is not academic. Sellers do not want to list products into an empty room. Buyers do not want to browse a marketplace with weak supply. Brands do not want to pay for access to creators until the creators can move real demand. Creators will sign up for free all day, but that does not mean the other side has a reason to spend money.

That tension kills more marketplace products than bad code does.

I have seen this shape a few times. One founder already had a real business. It was not a pure software platform. It involved physical products, relationships, curation, and a lot of operational work that did not look clean in a venture pitch. But it gave the company something most marketplaces would kill for: access to both sides of the market.

There were buyers. There were suppliers. There was actual demand. The work was messy, but the mess was evidence.

Investors wanted something cleaner. Less physical business. More platform. More like Etsy or Faire. More software margin, more marketplace language, more scalable narrative. The direction sounded bigger, but it pulled the product away from the people who were already buying.

That is the dangerous part of taking marketplace advice from people evaluating a pitch instead of operating the business. They may push you toward the version of the company they would like to fund, then never fund the painful transition they helped create.

The product work becomes confused because the business gets confused. Instead of turning the existing operation into software one proven workflow at a time, the team starts building a marketplace for customers who have not asked for it yet. Merchant onboarding. Buyer discovery. Admin tooling. Payments. Search. Profiles. Inventory. Messaging. Every piece may be reasonable in isolation. Together, they can become a very expensive theory.

The theory usually sounds like this: if we build the platform, the market will organize itself.

Usually it will not.

The famous marketplace stories make this easy to forget because we remember the scaled version, not the awkward first version.

Airbnb did not begin as a global lodging marketplace with infinite inventory and polished trust systems. It began with air mattresses, conferences, city-by-city urgency, and founders doing work that had no business existing in a scalable platform. When listings in New York looked bad, the founders went to hosts, rented a camera, and took better photos themselves. That was not a feature. It was a manual intervention into the supply side of the market.

But it solved a real marketplace problem. Travelers did not trust weak listings. Hosts did not know how to merchandise their own homes. Better photos made the supply more legible, which made buyers more willing to book, which made hosting more worthwhile. The unscalable work created the conditions for the scalable marketplace.

Uber had a different version of the same problem. A ride-hailing marketplace is worthless if riders open the app and see no cars. It is also worthless if drivers wait around with no rides. Early Uber did not solve that by launching a universal transportation platform on day one. It started with a narrow, premium black-car use case, in one city, where the supply could be recruited and the experience could be controlled.

That focus mattered. The company did not need every rider, every driver, and every trip type at the start. It needed enough reliable supply in a dense market to make the app feel real. The early marketplace was not broad. It was constrained, operational, and local. Only later did the product expand into cheaper rides, more drivers, more cities, and a more general transportation network.

The lesson is not that every founder should copy Airbnb or Uber. Most should not. The lesson is that even the iconic marketplaces did not cold start by acting like fully liquid platforms. They found a narrow pocket of demand, made the supply side better by hand, and used manual work to create trust before software could carry the load.

Another founder I worked with had the same problem in influencer marketing. Signing up influencers was easy because it cost them nothing and offered upside. The supply side looked healthy in the dashboard. The demand side was a different story. Brands did not want to pay just because the marketplace existed. They needed trust, proof, campaign support, quality control, and confidence that the work would produce a business result.

The software could register interest. It could not manufacture demand.

I saw a similar pattern in advertising. The pure marketplace model struggled. The service business worked better because the founders could make the match, manage the work, learn the buyer’s objections, and turn vague interest into actual revenue. It was less elegant, but it was closer to money.

This is why the “unscalable” work matters. Manual matching is not a failure of product strategy. Concierge onboarding is not automatically a lack of ambition. A founder making calls, curating supply, walking buyers through options, and handling the awkward middle is often doing the most important product research in the company.

That work tells you what the platform should become.

It shows which buyers are real, which sellers are worth recruiting, where trust breaks, what needs to be guaranteed, what can be automated, and where the business actually earns its take rate. It also shows whether the marketplace should exist at all. Sometimes the better company is a service business with software leverage. Sometimes the marketplace is a later stage of the operation, not the starting point.

Founders get into trouble when they treat manual work as something to hide from investors. The better move is to understand it deeply enough to explain why it is an advantage. The service layer can be the wedge. The buyer relationships can be the demand engine. The curated supply can be the moat before the marketplace has enough liquidity to stand on its own.

Code still matters. The architecture has to support different users, permissions, payments, workflows, and operational control. But the architecture should follow the cold start strategy, not replace it. Building seller portals and buyer discovery before you know how the first valuable transactions happen is just a polished way to avoid the hard part.

Marketplaces are not hard because there are two sides.

They are hard because both sides are waiting for proof, and early proof usually comes from a founder doing the work the platform is supposed to make disappear.