Expertise

Marketplaces and Multi-sided Platforms

Marketplace product design coordinates buyers, suppliers, partners and operators around different information, risks, incentives and responsibilities.

  • Marketplace design
  • Multi-sided platforms
  • Transaction modelling

Different platforms coordinate different forms of value

A marketplace is an operating model expressed through several products. The buyer, supplier, partner and operator do not experience one neutral transaction. Each sees different information, takes different risks and wants a different outcome.

Marketplace product design succeeds when those separate experiences still produce one coherent commitment. Tcules models the participants, exchange, rules and operating responsibilities before designing the surfaces around them.

Each marketplace type exchanges a different form of value, which changes where the product model becomes difficult.

How marketplace subdomains coordinate value
Product subdomainWhat is exchangedWhere the product model becomes difficult

Goods and retail marketplaces

product, payment and fulfilment

catalogue truth, seller quality, returns and fraud

Service marketplaces

availability, expertise and an agreed service

qualification, matching, scope change and completion evidence

B2B networks and exchanges

capacity, inventory, data or commercial opportunity

organisation identity, negotiated terms, approvals and integration

Labour and talent platforms

work, availability and compensation

eligibility, fit, scheduling, performance and worker protections

Property, mobility and asset platforms

time-bound access to a scarce asset

availability, condition, deposit, hand-over and incident recovery

Content or attention platforms

contribution, distribution and audience

moderation, recommendation, rights, incentives and creator control

A shared grammar for transactional marketplaces

A transactional marketplace can be modelled as a chain of commitments. Content, attention and some network platforms need a different exchange grammar even when participant authority remains the governing concern.

Eligibility -> discovery -> match -> negotiation -> commitment -> fulfilment -> settlement -> reputation or dispute

Each participant has a view of that chain. The platform has another: it sets eligibility and visibility rules, records state, controls some remedies and decides which evidence can change trust. The product should expose the shared transaction without pretending that every participant has equal authority.

  1. 01

    Who can see the information before commitment?

    The answer defines what each participant can know before they take risk.

  2. 02

    Who can change price, scope, timing or eligibility?

    The answer clarifies where authority sits before and after negotiation.

  3. 03

    What makes an acceptance binding?

    The answer separates exploration from commitment.

  4. 04

    What can be cancelled, reversed or disputed?

    The answer exposes the recovery paths that the interface and operations must support.

  5. 05

    Which evidence can the platform verify?

    The answer determines what trust, reputation and remedy decisions can safely rely on.

  6. 06

    Who acts when automation cannot resolve the exception?

    The answer connects product state to human operating responsibility.

  7. 07

    What remains true if one participant disappears?

    The answer protects the shared transaction model from depending on one participant's continued presence.

Liquidity is not only a search problem

Discovery can bring two sides together, but a platform also needs enough qualified supply, useful demand, credible information and confidence in what follows the match. Ranking that optimises clicks while ignoring fulfilment quality can move a short-term metric and weaken the exchange.

Tcules treats search, recommendation, onboarding, trust and operations as connected decisions. The useful diagnostic is not How do we increase conversion? alone. It is Which participant must make which commitment, on what evidence, and what happens if the exchange fails?

The EU Digital Services Act (opens in a new tab) makes seller traceability, ad transparency and protection from deceptive interface patterns material product concerns for covered platforms. The FTC's consumer reviews and testimonials rule (opens in a new tab) addresses fake and deceptive reviews. Tcules' design implication is that reputation should remain connected to bounded evidence rather than operate as decorative social proof. Applicability and compliance remain client-owned legal questions.

AI changes matching, moderation and delegated action

Where AI can help

AI can classify supply, enrich listings, rank matches, detect risk, summarise negotiation and prepare operational action.

Where product authority must stay explicit

AI can also amplify opaque rules, disadvantage one side or execute beyond a participant's intent.

The product needs to distinguish a signal from a rule, a recommendation from a commitment and a prepared action from an executed one. Participants should be able to inspect material inputs, correct relevant data and reach a human route when automated decisions affect access, money or reputation.

How the work comes together

Tcules can lead participant research, product and transaction modelling, workflow and interface design, prototyping, design-system work and agreed implementation. The engagement can begin with one broken transition, such as seller onboarding, matching, fulfilment exception or dispute, and still preserve the whole transaction model.

Representative method demonstrator

For a service marketplace, Tcules would model one booking differently for the customer, provider and operator. The visual would show what each can see and change at quote, commitment, delivery and dispute; the shared ledger would retain who changed terms and why. This demonstrates the method and is not presented as a Tcules client case.

Proof boundary

Related paths

Continue into adjacent service and expertise material.

Bring the participants and transaction

Start with the participants, exchange, rules and operating responsibilities before designing the marketplace surfaces around them.