What Are the Disadvantages of Running a Marketplace?

The disadvantages of running a marketplace are structural: you must recruit and retain two sides, stop them trading around you, survive thin take rates after payment and support costs, and staff disputes that a single-vendor shop never sees. Beautiful listing cards do not cancel those forces. We still build and operate marketplaces - seven on our own balance sheet - because the model works when the niche and economics fit. This piece is the counterweight: when it hurts, and when you should build something else.

The chicken-and-egg problem never fully goes away

Buyers want supply. Sellers want demand. Day one you have neither. Manual recruitment, geographic or category narrowing, and concierge matching get you through the cold start - then success resurrects the problem as a scaling shape: new cities, new categories, new seller quality tiers each reopen empty-grid risk.

What does not fix it:

• Spending on brand ads before inventory exists
• Shipping a fifth homepage variant
• Promising both sides “the network” that is not there yet

What reduces it:

• Supply-first sequencing (how to develop a marketplace)
• Tight niches with witnessable offline matchmaking (niche marketplaces)
• Concierge ops until the product earns the right to be self-serve

Chicken-and-egg is not a launch week bug. It is a permanent operating theme. Budget for it.

Leakage: when buyers and sellers cut you out (and what actually reduces it)

Leakage is the deal that starts on your platform and closes on email, WhatsApp or bank transfer - without your fee. High-ticket services and local services are especially prone. If your only value was an introduction, parties will skip the meter once they trust each other.

What actually reduces leakage:

• In-platform payments that are easier than chasing invoices
• Trust artefacts buyers cannot recreate offline (reviews tied to verified jobs, dispute cover, identity checks)
• Workflow value after the intro - messaging, scheduling, documents, payout clarity
• Contractual and product friction that makes off-platform payment annoying without being hostile

What barely works:

• Terms of service alone
• Hiding contact details so aggressively that serious buyers leave
• Raising take rate to “make up for” leakage you have not measured

If your wedge is only lead delivery, expect leakage and price like a lead business - or redesign the product so staying inside is rational. Payments detail: Stripe Connect for marketplaces.

The margin squeeze: take rates vs operating load

Are online marketplaces profitable?

Sometimes - when contribution margin survives card fees, refunds, support minutes and acquisition. Often not, when founders confuse GMV screenshots with profit. A marketplace can grow top-line transaction volume while losing money on every awkward order.

Squeeze mechanics:

• Sellers push take rate down once they have alternatives
• Buyers push for discounts and coupons that come out of your margin
• Payment and payout costs are relatively fixed per transaction
• Support and trust ops scale with conflict, not with your slide deck’s optimism

Revenue model choices that affect this squeeze are covered in how marketplaces make money. The disadvantage framing here is simple: you are taxed by both sides’ expectations and by your own ops.

The support burden nobody budgets

Two-sided complaints multiply. The buyer says the van was dirty; the owner says the renter returned it late. The practitioner says the client no-showed; the client says the listing photos misled them. Your team sits in the middle with payouts, partial refunds and reputation on the line.

Under-budgeted items we see repeatedly:

• Verification and KYC chases
• Payout “where is my money” tickets
• Content moderation and listing quality
• Dispute desk with authority to pause accounts
• Seller success during cold start (still human)

Software reduces repetition. It does not eliminate the desk. After launch, many client platforms need a real care path - our public support tiers start at £495 / £1,850 / £3,450 a month when you want that owned - but the bigger point is organisational: someone must own two-sided fairness or your brand becomes the villain in every screenshot thread.

Is it hard to build a marketplace app?

Building screens is moderate. Building a marketplace business is hard. The app must cover listing, discovery, checkout, payouts, admin and trust flows - payments-heavy UK builds commonly sit in the £30,000-£75,000+ market band, with leaner MVPs lower and deeper programmes higher (marketplace build cost). The harder part remains liquidity, leakage and support, which no template deletes.

When a marketplace is the wrong model (and what to build instead)

Choose a different shape when:

• One side cannot be recruited without fantasy CAC
• Transactions are truly one-off with tiny tickets and heavy support
• A dominant horizontal already owns trust and logistics in your wedge
• You actually need SaaS for one role, not a two-sided meter
• Offline brokers already clear the market and will not move for a 2% convenience gain

Build instead:

• Directory + lead fees - simpler economics, clearer seller expectation
• Single-sided SaaS - charge one role for tools; skip liquidity theatre
• Managed marketplace / concierge - humans match; software assists
• Internal platform - staff operate the desk; customers never see “two sides”

Operating seven platforms on our own balance sheet teaches the downside pattern faster than any slide deck: density and fees either align, or the model eats you. It is a trap when you want network effects as decoration on a thin idea.

Write down the transaction, the first twenty suppliers and who staffs disputes before you fund two-sided software. We recommend marketplace, directory or neither via marketplace development.