Skip to main content
Industry · Marketplaces & platforms

Two sides. One trust layer.

PYJ Advisory for marketplaces and platforms. Supply-side onboarding, demand-side discovery, dispute resolution that doesn't burn out the founders. Built on Sharetribe, Mirakl, or hand-coded — whichever fits the take rate.

Supplier feed12 onboardinglive
Demand pipeline87 active buyerstoday
Disputes3 open · 1 escalated36h
Payouts£42k clearedFri
Ratings94% above 4.530d
KYC2 stalled at verifyaction
Operator console · liveBoth sides, one screen.

Supply, demand, trust, payout — routed by SLA, owned by a human, audit-trailed. The founder steps in only when escalation needs them.

Suppliers live214
GMV (30d)£186k
Disputes open3
Marketplaces B2B · gig · services · two-sided · KYC-ready9d → 36h Typical dispute resolution200+ Suppliers onboarded on one platform100% Stripe Connect, audited payouts
By marketplace type

Three flavours of the same instrument.

Same trust layer, different shape. Pick the marketplace type closest to yours — each has a deep page with the sector-specific stack, proof, and how we measure.

The marketplace stack

Verify, match, resolve. On rails.

Onboarding, discovery, disputes, payouts, ratings, knowledge — running across both sides of the platform without the founder being the trust layer in person.

01 · Supply onboarding

Verify, contract, payout-ready in days.

ID checks, bank verification, contract signed, Stripe Connect account live — measured in days, not weeks. New suppliers ship their first listing the week they apply.

  • Onfido or Stripe Identity
  • Stripe Connect onboarding
  • Contract & T&Cs flow
  • Stalled-applicant nudges
02 · Demand discovery

Search, match, book — on the platform's terms.

Buyers find the right supplier through your funnel, not Google's. Search, filters, match logic — tuned for your category, not a generic e-commerce template.

  • Algolia or custom search
  • Category-tuned filters
  • Match-and-book flow
  • On-platform messaging
03 · Trust & disputes

Resolve before review-bombs.

Open a ticket, escalate to mediation, refund or release escrow — all from one queue. Disputes get triaged before they become Trustpilot one-stars.

  • Zendesk or custom workflow
  • SLA & escalation tiers
  • Evidence & comms log
  • Refund / escrow controls
04 · Payouts & escrow

Stripe Connect, on schedule, audited.

Funds held in escrow, released on milestone or completion, payouts batched on a schedule. Reconciliation that an accountant could sign without flinching.

  • Stripe Connect or Modulr
  • Escrow & milestone release
  • Scheduled payout runs
  • Reconciliation export
05 · Ratings & reviews

Real, moderated, attributable.

Reviews tied to verified transactions, moderated for abuse, surfaced in supplier ranking. Trust signals that reflect the work, not the loudest voice.

  • Transaction-linked reviews
  • Moderation queue
  • Trustpilot or custom
  • Supplier ranking signal
06 · BrainBase

Operator playbook in one place.

Dispute SOPs, regulatory FAQ, supplier comms templates, ops runbooks — searchable from the console. New ops hires answer correctly on day one.

  • Dispute SOPs
  • Regulatory & KYC FAQ
  • Supplier comms templates
  • Ops runbooks
Sample engagement

The B2B marketplace that cut disputes from nine days to thirty-six hours.

Two hundred suppliers. Two founders. Disputes living in a Gmail label.

A B2B marketplace with 200+ verified suppliers ran trust on the founders' inboxes — every dispute pinged both phones, escalations were a forwarded email, refunds happened by Slack DM. Resolution took an average of nine days; suppliers were churning on the back of it. Three-week build: a routed dispute queue with SLA tiers, evidence upload, in-app messaging, and Stripe Connect refund / release controls — plus a BrainBase of dispute SOPs the ops hire could search. First quarter live: average resolution down to 36 hours, supplier churn down a third.

How we measure: resolution time tracked from first ticket open to final state (refund, release, or close), measured against the prior 90-day Gmail-label baseline reconstructed from thread timestamps; supplier churn measured as suppliers inactive 60+ days against the prior cohort.

9d → 36havg dispute resolution
−33%supplier churn (60d inactive)
200+verified suppliers live
Adjacent industries

Different shape of the same problem.

If your work isn't exactly this, the nearest sectors share the rhythm. Or browse every industry we build for.

Build the trust layer.

Bring the take rate, the supplier count, and the dispute queue. That's the brief.