Solution guide

Marketplaces: start with the hardest side, and start small.

A marketplace connects people who offer something with people who want it. The software is rarely the hard part. The hard part is getting both sides to show up, trust each other and come back. That shapes how a marketplace should be planned.

The chicken-and-egg question comes first

Buyers will not come to an empty marketplace and sellers will not list where there are no buyers. Before any design work, decide how you will get the first of each:

  • Which side is scarcer? Usually supply. Start there, with a small group you can recruit personally.
  • What narrow niche can you serve completely? Better to be the obvious choice in one category or district than a thin presence everywhere.
  • Why would either side use you instead of what they do today? If that answer is vague, software will not fix it.

A marketplace that works in one small corner can expand. One that is spread thin from day one rarely recovers.

Start with a concierge version

The most reliable way to learn is to do part of the work by hand. Match buyers and sellers yourself, take payment manually and use simple forms, while watching what people actually do. Then automate what repeats.

  • It tests demand before you pay for a full platform.
  • It shows which features matter, and which only sounded important.
  • It makes the later software smaller, cheaper and better aimed.

What a first release usually contains

  • Seller onboarding — a profile or listing, with the information buyers need to decide.
  • Discovery — browsing and search that suit your niche, not a generic catalogue.
  • A booking, enquiry or purchase step that is simple and clear for the buyer.
  • Payment and, if needed, payouts to sellers.
  • Messages or a way to ask questions before and after.
  • An admin view for you to review listings, help users and resolve problems.

Reviews, recommendations, advanced search and mobile apps are valuable, and usually come after the basic exchange works.

Decisions that shape the whole product

  • How do you earn? Commission, subscription, listing fees or a mix. It affects payments, pricing pages and who feels the cost.
  • How does money move? If you collect payment and pass it on, you handle other people's funds, which can carry regulatory implications. Many marketplaces use a payment provider's features for splitting payments between parties; take professional advice on how to structure it.
  • How is trust built? Identity checks, reviews, clear policies, and a way to resolve disputes fairly.
  • What stops people from going around you? If the platform adds real value after the first match — payment protection, scheduling, reputation — they have a reason to stay.
  • Who is responsible for what? Terms between you, sellers and buyers should be written with advice, not copied.

Hong Kong marketplace details

  • Bilingual listings. Sellers will write in English, Chinese or both. Search, titles and descriptions should work across the two.
  • Local payment methods. Buyers may expect more than cards. Support depends on your provider and on how your account is set up.
  • Delivery and cross-border trade. If goods move, decide how delivery, returns and any cross-border steps are handled, and who bears each cost.
  • Personal data on both sides. Buyers' and sellers' details need careful handling; plan for the Personal Data (Privacy) Ordinance from the start.

Why marketplaces are bigger than they look

Marketplaces are larger than they look because they are really two or three products at once: a seller product, a buyer product and an admin product. Payments and payouts, search, messaging and trust features each add weight. A narrow, manual-first version is a fraction of the size of a full platform.

For a first sense of scale, use the cost estimator and the technology stack selector, which includes a marketplace project type.

Signs you are ready to automate

Resist building matching, payouts and messaging until the manual version shows you need them. Useful signals are:

  • The same transaction repeats with different people, and you perform identical steps each time.
  • You are the bottleneck — introductions or payments wait for you.
  • Buyers and sellers ask for the same missing feature, unprompted.
  • You can describe the rule that makes a good match in a sentence.

If you cannot yet describe the steps clearly by hand, software will only automate the confusion.

Frequently asked questions

Should we build the whole platform first?

Almost never. A smaller, partly manual version tests whether both sides really want what you offer, and it makes the eventual platform far better aimed.

Can the platform handle payments to sellers?

Yes, usually through a payment provider's features for splitting and paying out. Holding other people's money can have regulatory implications, so we would plan the structure with you and recommend professional advice.

How do we stop buyers and sellers going around the platform?

By offering something worth staying for after the first introduction — secure payment, easy scheduling, reputation, dispute handling. Rules alone rarely work; value does.

Do we need a mobile app?

Not at first. A good mobile web experience reaches everyone, and an app can follow if usage justifies it.

How long and how much?

It depends heavily on scope. A narrow first version is a modest project; a full marketplace is a large one. The estimator gives an indicative range and a scoping conversation makes it firmer.

Thinking about a marketplace?

Tell us who the two sides are and how you would get the first of each. We will help you plan a first version small enough to learn from.

Request a project quote