Marketplace landing page: solving the chicken-and-egg problem before launch

A standard landing page only has one visitor to convince: the person who's about to buy, sign up, or request a quote. A marketplace has two, with opposite expectations — the seller wants an audience before listing an offer, the buyer wants choice before coming back regularly — and neither wants to be first on an empty platform. This deadlock has a name in economics: Bernard Caillaud and Bruno Jullien formalized it in a landmark 2003 study published in the RAND Journal of Economics, titled "Chicken & Egg: Competition among Intermediation Service Providers" (see the study on Google Scholar), which shows that an intermediary's value depends directly on how many users are already present on the other side. A marketplace landing page can't simply reuse the principles of a standard product landing page — it has to solve this deadlock before trying to convert anyone.

Why a marketplace can't rely on a single landing page

The most common instinct is to build one page that addresses "sellers and buyers" with a section for each. The result dilutes both messages: the seller looking for a concrete reason to list an offer lands on arguments meant for buyers, and vice versa. The message match principle — making the page match exactly the intent that brought the visitor there — applies here with an extra constraint: the two intents can't coexist on the same page without one crowding out the other. Two separate landing pages, each with its own promise, its own form, and its own social proof, will almost always outperform a single page trying to please everyone.

Which side to target first: the single-player mode strategy

Before deciding which side to court first, you have to accept that one of them will be alone for a while. The most reliable tactic is to give that first side value independently of the other's presence — what practitioners in the field call "single-player mode": a booking management tool useful to a restaurant even without a diner coming through the platform, an online catalog useful to a tradesperson even without a buyer coming through the marketplace. The landing page should then sell that immediate value rather than a promise of traffic that doesn't exist yet. It's the same logic as a SaaS waitlist landing page: convince on a real, verifiable benefit available today, not on a hypothetical audience tomorrow.

Building one landing page per side instead of a single page

• The demand-side page highlights choice, ease of matching, and reassurance on the quality of the offer — even when that offer is still limited. It should be honest about what's available today rather than implying a catalog that doesn't exist yet.
• The supply-side page highlights the concrete gain for the seller or provider (visibility, time saved, new customers) and should address the question they're implicitly asking — "why join before there are any buyers?" — rather than ignore it.
• Two different CTAs: "Find a [provider/product]" on one side, "Become a partner" or "List your offer" on the other — never a generic "Join the marketplace" button that tells neither audience what they get.
• Two sets of testimonials, when they exist: a seller won't recognize themselves in a satisfied buyer's review, and vice versa.

Faking social proof before liquidity exists

Before both sides feed each other naturally, the landing page has to compensate for the lack of organic social proof with a deliberate manual-curation approach: reaching out directly to a couple dozen quality providers before the public launch instead of waiting for spontaneous signups, and announcing a narrow launch (one city, one sector, one specific category) rather than an empty nationwide footprint. A narrow but dense market converts better than a wide but empty one, for the same reason a counter set too low produces the opposite of the social proof it's meant to create: it's better to show 15 qualified providers in a single city than 3 spread across the whole country.

The form: filtering rather than maximizing signups on the supply side

Most landing pages benefit from trimming their form to the bare minimum to maximize completion rate, a principle covered in our article on how many form fields actually convert. The supply-side form of a marketplace is the exception: at this stage, the priority isn't signup volume but the quality of what the first buyers will actually see. A multi-step form that asks for work samples, a coverage area, or indicative pricing acts as a first filter — and the added friction is justified as long as it protects the credibility of the offer shown to the very first buyer visitors.

The mistakes that kill the network effect before it starts

• Launching too broad geographically — announcing nationwide coverage on day one spreads a still-thin offer over a territory too vast for it to feel sufficient anywhere.
• Courting both sides with equal intensity from the start — without one side already solid, the promise made to the second one rings hollow.
• Offering no value if the other side is empty — without a single-player mode, the first signup has no reason to stick around while liquidity builds.
• Hiding the real level of liquidity — a buyer who finds an empty catalog after signing up loses trust for good; it's better to honestly announce a limited selection than promise a choice that doesn't exist.
• Copying a standard product landing page structure — a young marketplace needs transparency about its stage of development more than a polished sales page that papers over the lack of liquidity.

In practice with LanderKit templates

The SaaS Waitlist template fits well for a pre-launch marketplace's demand-side page: a minimal capture form, a counter that grows with signups, and a focus on the problem solved rather than a still-empty catalog (demo at /demo/saas-waitlist). On the supply side, the Coach Consultant template, built around an application funnel ahead of a discovery call, adapts naturally into a screening form for the first sellers or providers (demo at /demo/coach-consultant). Both ship as ready-to-deploy React/Next.js source code, at €89 on their own, or bundled with the other 8 templates in the full €229 bundle — enough to get both sides of a marketplace live without a custom build. Once both pages are live, the main metric to track isn't traffic but the signup ratio between the two sides, adjusted through an A/B test of the message and acquisition intensity on whichever side is lagging.