Every team weighing a multi-vendor marketplace asks "should we build it or buy it?" and prices the wrong thing. The build cost and the licence fee are the visible tip; the mass underwater is integration and, above all, operations — the bill that arrives every month for as long as the marketplace exists. This article costs all three routes honestly in effort terms: building the engine, integrating licensed software, and having it operated for you. If you want the conceptual framing first, the pillar on white-label marketplaces and the Marketplace-as-a-Service explainer set it up; this is the money-and-effort version.
The three routes
There are exactly three ways to end up with a marketplace, and they trade the same three resources — money, time and engineering capacity — in different proportions.
- Build from scratch. Write the ingestion, enrichment, search, cart, split checkout, vendor consoles and monitoring yourself. Maximum control, maximum cost, longest time to live.
- Buy (license) software. Install a marketplace platform under your brand. You skip writing the core engine but own integration, hosting, tuning and operations.
- Managed (Marketplace-as-a-Service). An operator runs everything on your domain. You bring the audience and brand; they bring the machinery and share revenue.
The trap is comparing them on the wrong axis — sticker price — when the axis that decides the outcome is total cost of ownership over several years, most of which is operations.
The iceberg: what each route actually costs
Break the true cost into three layers and the routes separate clearly.
| Cost layer | Build | Buy (license) | Managed |
|---|---|---|---|
| Engine / platform | Multi-quarter build | Licence fee | Included |
| Integration | N/A (you built it) | Heavy — connect vendors, payments, tax | Included |
| Hosting & infra | Yours forever | Yours forever | Included |
| Operations (perpetual) | Yours forever | Yours forever | Included |
| Time to live | Quarters | Months | Weeks |
| Control | Total | High | Moderate |
| You need engineers? | A team | At least some | None |
The row that dominates the decision is operations (perpetual), and it is the one spreadsheets omit because it has no line item. Build and buy both leave it entirely on you; managed absorbs it. That single row is usually larger than the engine and integration combined, because it never ends.
What building really involves
A credible multi-vendor platform is not one project but a dozen. Catalog ingestion from several ecommerce platforms and feeds. Product data enrichment to make messy vendor data searchable. A real search engine with typo tolerance, synonyms, facets and semantics. One cart with per-vendor shipping math. Split checkout that fans one payment into VAT-correct sub-orders. Vendor and operator consoles. Compliance — EU price rules, VAT, consent. Monitoring, deploys, alerting. Each is a specialty; together they are a multi-quarter effort for an experienced team, and the work does not stop at launch because catalogs drift, vendors switch platforms, and payment and tax rules change under you. Building is justifiable when the marketplace is the company. It is rarely justifiable when it is a monetisation channel for an existing brand.
There is a second, quieter cost to building: opportunity. Every engineer-quarter spent on ingestion and checkout plumbing is a quarter not spent on the content, product or community that earns your audience in the first place — the actual source of your advantage. For a media or content brand, redirecting scarce engineering into commerce infrastructure that dozens of teams have already built is rarely the highest-value use of the team, even when they are perfectly capable of building it. Capability is not the same as it being worth their time.
The hidden cost of buying software
Licensing looks like a shortcut because it skips the engine, but it relocates the cost rather than removing it. You still connect every vendor, map their categories, wire payments and tax, tune search for your catalog, host and secure the stack, and — forever — keep it healthy. The licence fee is the small number; the integration and the standing operations team are the large ones. Licensed software is the right call when you have engineers to spare and want deep low-level customisation. It is the wrong call if you chose "buy" specifically to avoid needing an engineering team, because you still do.
The operations layer is not theoretical. Running our marketplace means catalog syncs across two ecommerce platforms plus feeds, enrichment re-runs when data changes, search tuning, per-vendor shipping mirrored from each seller's own shop, split checkout with VAT-correct invoices, plus monitoring, a daily SEO audit and a weekly health sweep. None of that ends after launch — it is the perpetual cost the build-or-buy spreadsheet always leaves out.
A decision framework by team and ambition
Match the route to the resource you are actually short of.
| Your situation | Best route |
|---|---|
| Marketplace is your core product; funded engineering team | Build |
| Have engineers; need deep customization; commerce is strategic | Buy / license |
| Have an audience; no commerce engineering team; want to be live fast | Managed |
| Content or community brand monetising existing traffic | Managed |
| Uncertain demand; want to validate before committing capital | Managed (lowest sunk cost) |
The through-line: if commerce is your product, own the engine; if commerce is a way to monetise an audience you built doing something else, do not spend your scarce engineering and attention rebuilding plumbing that already exists. The revenue mechanics that make the managed share worthwhile are in the business model guide, and whether the model fits your niche at all comes back to the three-ingredient test in niche marketplace ideas.
One more factor belongs in the decision: uncertainty. If you are not yet sure the marketplace will earn its keep, the route with the lowest sunk cost is the one that lets you find out cheaply. Building and licensing both demand large commitments before you learn whether demand converts; a managed arrangement lets you validate with real vendors and real orders first, and scale the bet only if the numbers work. Costing the downside of being wrong — not just the upside of being right — is what separates a sound infrastructure decision from an expensive act of faith.
Key takeaways
- Total cost of ownership, not sticker price, decides it — the engine and licence are the visible tip of a much larger iceberg.
- Operations is the dominant, perpetual cost and the one spreadsheets omit; build and buy leave it on you, managed absorbs it.
- Building is a dozen specialties, justified only when the marketplace is the company itself.
- Licensing relocates cost rather than removing it — you still integrate, host and operate, and still need engineers.
- Match the route to your scarcest resource: own the engine if commerce is your product; go managed if it is a channel for an audience you already have.
Frequently asked questions
Should I build or buy a marketplace platform?
How much does it cost to build a marketplace?
Is licensed marketplace software cheaper than managed?
What is the real total cost of ownership of a marketplace?
Skip the iceberg. Keep the marketplace.
We carry the engine, the integration and the perpetual operations, so your team never has to budget for them — you keep the audience and the revenue share.
Request early access See the live marketplace →