How much does it cost to build a marketplace?

A marketplace has no list price: its cost depends mostly on three decisions made before the first line of code. The revenue model (taking a commission means split payments), how much of the work stays manual at launch, and how many distinct journeys exist between buyers, sellers and your own team. On top of the build come running costs that grow with volume, payment fees first.

This article does not quote a price range. The ranges you find online mix scopes that cannot be compared, from a simple listings site to a full multi-vendor marketplace with payouts, disputes and mobile apps. Instead, it breaks down the cost drivers, puts numbers on the ones that are public (payment fees), and gives you the questions that lead to a figure you can rely on.

Where the money goes

A marketplace is software with three audiences: buyers, sellers (or service providers) and your operations team. Each component below comes in a simple or a full version, and the gap between the two explains most of the difference between quotes.

Two components are consistently underestimated. The back office first: it is where your team spends its day (approving, refunding, arbitrating), and it often takes as much work as the customer-facing side. Then failure paths: a declined card, a seller who cancels, a buyer who disputes, a payout blocked because a document is missing. The happy path is quick to build; exceptions are where the money goes.

Split payments: the line that changes everything

As soon as the platform takes a commission on money that flows through it, it is handling funds on behalf of others, which is a regulated payment activity in the EU and many other jurisdictions (see how to build a two-sided marketplace). The usual answer is a licensed payment provider built for platforms. Take Stripe Connect, whose pricing is public. Stripe offers two models:

Sources: Stripe's support page on monetising Connect for the US figures and its Connect pricing page for France for the euro figures, both checked on 3 November 2026. An account counts as active in any month in which a payout reaches its bank account. Instant payouts cost 1% of volume on top, and cross-border payouts start at 0.25%. For card processing in the euro area, the French pricing page lists 1.5% + €0.25 for standard European cards and 2.8% + €0.25 for premium cards; check the page for your own country, as rates differ.

An illustrative calculation using those published euro-area rates: a platform that processes 1,000 card payments of €100 in a month, all on standard cards, and pays €1,000 to each of 100 sellers in a single monthly payout, under the model where it controls seller pricing.

This is not a quote. Rates change, can be negotiated at volume, and depend on card mix. What it shows is twofold. Payment fees are a variable cost that tracks your gross transaction volume and must be built into your commission. And the Connect model is chosen together with your revenue model, not after it.

On the build side, split payments are never "just a Stripe integration". You need seller onboarding and follow-up on missing verification, commission calculation, payouts at the right moment, partial refunds, chargebacks and accounting reconciliation. It is often the heaviest part of version one.

Costs that start on launch day

Development is only part of the bill. A live marketplace generates recurring costs you should know before you set your commission.

• Payment fees, detailed above, proportional to volume.
• Hosting and third-party services: database, document storage, email and SMS delivery, maps if search is location-based.
• Staff time: profile vetting, moderation, support, dispute handling. A "manual first" launch deliberately shifts cost from development to this line.
• Maintenance: security updates, changes in third-party APIs (payments, maps), fixes. See the running costs of a custom application.
• Compliance: in the EU, annual reporting of seller income to tax authorities under the DAC7 rules, as implemented for instance in French tax guidance; updates to your terms; data protection requests. Building the report export into the admin panel costs little at design time and a lot to retrofit.

Cutting the upfront cost without making it fragile

Four levers reduce the initial build without creating dangerous debt.

1. Manual first: the team handles matching, profile vetting and follow-ups by hand for the first weeks. Software automates only what becomes painful at real volume.
2. Hosted onboarding from your payment provider for seller sign-up and verification, instead of a custom branded flow. You can replace it later.
3. One scope: one category, one area, one transaction type. Every extra category brings its own fields, rules and edge cases.
4. A responsive web app before any native app, until one side genuinely needs it in the field.

What you cannot cut: account security, the regulatory setup for payments and personal data protection. Shortcuts there are paid back later, with interest.

Off-the-shelf or custom

Several vendors sell configurable marketplace software on a subscription. To test demand with a standard model (listings, booking, a commission on each sale), that is often the cheapest way to start. Custom development pays off when your transaction does not fit the standard: quotes before payment, multi-stage jobs, commissions that vary by category, integration with your existing systems, or a platform that is itself your main business asset. In that last case ownership matters: with a development partner, rights to the code are defined case by case in the contract.

Three ways to pay for the build

Total cost does not say how it is spread over time. For custom development, three arrangements exist:

• Fixed price: agreed before any code is written, on a written scope. It needs a stable scope, which is why validating it on a prototype helps.
• Subscription: you do not pay for the build, only a monthly fee that covers hosting, maintenance and improvements; the studio remains publisher and operator of the software. The 36-month comparison is in subscription or upfront build.
• Time and materials: you pay for hours worked. LPR Studio does not work this way, but you will see it in many quotes.

How to get a figure you can trust

Before comparing quotes, ask every vendor the same questions and get written answers:

• Are split payments included, with payouts, partial refunds and chargeback handling?
• Which Connect model (or equivalent) is planned, and who pays the fees?
• Does seller verification use hosted onboarding or a custom flow?
• Does the back office cover moderation, disputes and tax exports?
• What happens when a seller cancels or a payment fails?
• What are the running costs, hosting and third-party services included?

The full method for putting several quotes into one grid is in how to compare software development quotes.

Where to start

A reliable price needs a scope that everyone sees the same way. That is what a prototype is for: buyer, seller and admin journeys with realistic data, presented in a video call within 5 working days, free of charge. Once validated, it serves as the specification for a fixed price or a subscription. If your project is about booking a single business rather than running a marketplace, building a custom booking platform is a simpler and cheaper problem.