In this article 11 sections
A transaction marketplace needs a buyer journey, a supplier journey and an operating process. Code23’s published marketplace band is £25,000–£60,000, checked 16 October 2026; that is one supplier’s offer, not a market average. Your estimate must separately account for payment design, exceptions, administration and the work of activating supply and demand.
First decide what kind of marketplace you mean#
| Model | Core outcome | Work that changes the budget |
|---|---|---|
| Directory | A person finds a relevant listing | Listing quality, search, moderation and contact |
| Lead or matching service | A suitable request reaches a supplier | Routing, qualification, response handling and operations |
| Transaction marketplace | An exchange is paid for and completed | Payment states, fees, refunds, payouts and disputes |
A directory can be a valid first product if discovery is the problem. It does not prove that people will complete a paid exchange. Conversely, building automated payouts before you have a workable matching process can spend money on the wrong constraint. State the outcome you need to test.
Code23’s pricing page advertises a £25,000–£60,000 marketplace band. We recorded that offer on 16 October 2026. It is not a comparable quote for every business model, and we have not independently audited delivery at those prices. Use it as a supplier reference, then specify your own scope.
Price three working experiences#
The buyer needs to find, evaluate and request or buy something. The supplier needs to join, present availability and fulfil the request. The operator needs to resolve the cases neither side can fix. Each experience can be narrow, but none should be invisible in the estimate.
| Person | First useful journey | Exception to include |
|---|---|---|
| Buyer | Request a suitable appointment and receive confirmation | Provider declines or cancels |
| Provider | Accept a request and see agreed payment status | Availability changes before acceptance |
| Operator | Find the transaction and resolve its status | Payment succeeds but notification fails |
A manual operating step can reduce software scope when it has a named owner and a documented process. That does not make its labour free. Estimate support time and include it in the operating model. See the marketplace launch guide for the first-cohort workflow.
Choose the money flow before implementing it#
Draw who pays, who receives money, when a fee is earned and what happens after cancellation. Connect charge types affect the distribution of funds and handling of refunds and disputes; Stripe’s charge-type documentation is a primary implementation reference. A payment API alone does not settle your business’s responsibilities.
Give the builder concrete examples: a failed payment, a partial refund, a supplier who cannot fulfil, and a payout already sent when an issue is raised. Ask who sees the state, what can be retried and what requires a person. Confirm the configuration with the provider and appropriate advisers where the model needs it.
A worked marketplace budget#
This illustrative model assumes a narrow transaction service with limited categories, one launch market, buyer/provider journeys and administration. Its rate and effort are chosen for demonstration. It excludes acquisition campaigns, complex migration and specialist regulatory work.
| Workstream | Team-days | Calculated delivery cost |
|---|---|---|
| Discovery and operating model | 6 | £4,500 |
| UX and interface design | 8 | £6,000 |
| Buyer, provider, admin and payments engineering | 44 | £33,000 |
| QA, transaction and accessibility checks | 12 | £9,000 |
| Release and handover | 5 | £3,750 |
| Total | 75 | £56,250 |
An illustrative 15% reserve produces £64,687.50 before tax and external one-off charges. Twelve months at an assumed £800 monthly running cost add £9,600. That yields £74,287.50 for this model’s build-and-operation envelope. It is higher than some advertised build prices because it includes an explicit reserve and operating year; the underlying scopes may also differ.
All worksheet inputs are illustrative assumptions chosen to show the arithmetic. They are not market rates, measured project averages or a quotation. Replace them with your team’s estimate. A team-day is one person’s working day: 40 team-days does not automatically mean eight elapsed weeks.
Separate software cost from marketplace economics#
A platform can launch technically and still have no useful supply. Budget separately for recruiting providers, qualifying listings, reaching buyers and supporting early transactions. A provider account is not proof of availability, and a buyer signup is not a completed exchange.
As an illustrative unit-economics exercise, a £100 completed transaction at a 15% platform fee creates £15 of gross platform revenue before payment costs, refunds, incentives and variable support. It does not create £100 of platform revenue. Write each deduction explicitly and use actual provider pricing when forecasting.
If every transaction needs 20 minutes of staff work, include that labour. Manual operations can be a sensible learning tool, but hiding them makes the software appear more economically complete than the business is.
The scope choices with the largest consequences#
- Booking versus immediate purchase: matching and acceptance introduce states beyond checkout.
- One geography versus many: currencies, provider availability and operating processes can differ.
- Single seller versus basket: multiple sellers in one order change fulfilment and money handling.
- Managed versus self-service supply: who checks listings, onboards providers and resolves errors?
- Simple availability versus live scheduling: calendars and concurrent bookings need explicit conflict rules.
Make the first release narrow enough that you can observe where exchanges fail. Add sophistication in response to evidence. The extra feature that increases listing count may be less valuable than fixing why an accepted request never becomes a completed job.
What to request in a marketplace proposal#
Attach the transaction map, user roles, operating rules and payment assumptions to your software development brief. Request separate estimates for initial implementation, unknown integrations and operating support. Define what evidence will demonstrate that a transaction, cancellation and refund work in the test environment.
Ask each supplier to separate one-off delivery, external charges and ongoing operations. Request the currency, tax treatment, payment schedule, support period and exclusions in writing. A contingency is a reserve against named uncertainty; it is not an extra feature budget. Keep acquisition spend separate so you can see whether the product is affordable to build and affordable to operate.
Agree a small pilot release and a named decision owner. Before inviting more users, check that support can find a transaction, explain its status and make the permitted correction without editing a database by hand.
Build your own budget#
Adjust the assumptions to see the arithmetic. These starting values reproduce the illustrative model above; they are not a quotation. The reserve applies to delivery effort, before external one-off costs. All amounts exclude tax.
- Delivery effort
- £56,250
- Delivery reserve
- £8,437.50
- External one-off costs
- £0
- Launch allowance
- £64,687.50
- Operating period
- £9,600
- Combined planning envelope
- £74,287.50
Your inputs are saved in this browser when storage is available. Reset restores this example. Nothing is submitted to us. Team-days describe effort, not elapsed delivery time.
Put this guide to work#
Frequently asked questions#
Is a marketplace more expensive than a normal app?
It can be, because several parties and transaction states need coordination. But a narrow directory may be simpler than a complex single-company app. Compare the actual journeys, integrations and operating responsibilities rather than the category name.
Can I launch without taking payments on the platform?
You can test a directory or lead service without platform checkout if that fits the offer and operating model. Be clear about what it proves: introductions or demand, rather than a complete platform-managed transaction. Plan how you will observe outcomes after the introduction.
Do I need automated matching from day one?
Not necessarily. A staff member can match early requests if the process is manageable, transparent and recorded. Capture why a match was made and whether it completed. Those observations can inform automation once you understand the rules.
Are payment processing fees part of the development quote?
Usually they need a separate line in the operating model, but confirm the agreement. Provider, country, payment method and configuration affect charges. Use current provider terms for your scenario instead of copying a generic percentage from a marketplace article.
How much does it cost to attract the first users?
The software estimate cannot answer that. Build a separate acquisition plan for each side, stating the channel, effort, incentives and expected completed transactions. Test a narrow segment before projecting a large market from cheap signups.
Should the first version include reviews and messaging?
Include them only if they resolve a specific trust or coordination need in the first journey. A controlled introduction or staff-managed update may work initially. If reviews or messaging are included, scope moderation, reporting and access to personal information too.
Sources and methodology#
This guide combines editorial analysis with the linked primary sources. Decision frameworks, worksheets and worked examples are our own; examples are illustrative unless explicitly identified as supplier claims or published research. We have not conducted original interviews, comparative supplier testing or a controlled experiment for this article.
- Code23: published pricing bands ↗
Supplier-advertised ranges checked 16 October 2026. These are not observed transaction prices or an industry average.
Accessed 16 October 2026 - Stripe: design a marketplace ↗
Primary documentation for marketplace payment architecture. Commercial, tax and legal responsibilities depend on the business and configuration.
Accessed 16 October 2026 - Stripe: choose a charge type ↗
Explains how Connect charge models affect the flow of funds, refunds and disputes.
Accessed 16 October 2026
Source check: 16 October 2026. Platform documentation can change. Published as part of our editorial collection.
Expanded 16 October 2026 with practical decision material, downloads and topic-specific answers. Supplier and platform claims are identified by their linked sources.
MVP Build Editorial. “How much does a marketplace MVP cost?.” MVP Build, 9 September 2026.
https://mvpbuild.xyz/marketplaces/how-much-does-a-marketplace-mvp-cost/