Freelance & contractor platforms · P2P marketplaces · Trust & Safety leaders
The dispute queue is a court you never wanted to run
Upwork-class platforms adjudicate thousands of work disputes with support agents: slow, inconsistent, expensive — and structurally conflicted, because the judge profits from the transactions it rules on. Outsource the judgment; keep the customers.
Every marketplace that stands between a buyer and a provider ends up running an amateur court. Support agents with macros decide whether a logo "met the spec," whether three weeks late voids a fee, whether a half-built site is worth half the money. Fully loaded, each ticket costs dollars to tens of dollars, outcomes vary by agent and time of day, and every ruling exposes the platform: the venue taking a cut of the transaction is deciding who keeps the money.
In the EU, the DSA now obliges platforms to engage with certified out-of-court dispute settlement bodies — and to pay for them, case by case, at human-body prices (our analysis of Article 21). Recourse is built to be the AI-native venue ruling at machine cost, with humans exactly where they belong: on the escalation ladder, on our side of the fence.
Worked example — the missed trade show
A $2,400 site build with a hard July 1 deadline tied to the client's trade-show launch. Mid-project the buyer adds scope ("a careers page and gated downloads — should be quick, right?"); the provider flags the added time, then goes quiet and delivers 60% of the site three weeks late. Buyer demands a full refund; provider points at the scope creep. Your best support agent would spend an hour on this and still get second-guessed.
Ruling: provider 65% / buyer 35%. The deadline was binding and its purpose known (MC-3); three weeks of silence compounds it (MC-7); the buyer's mid-project additions carry part of the fault (MC-4); and the buyer keeps a deployed, usable partial build, so pays for value retained (MC-8, SD-4). Split: ~$840 releases to the provider, ~$1,560 returns to the buyer — with the reasoning trace attached for both parties to read.
What the platform gets
- Cost: $4 list per automated verdict against a $5–15 BPO-ticket anchor — before counting escalations, make-goods, and close-the-ticket refunds your agents hand out to end conversations.
- Consistency: the same doctrine, every time, published in advance. Disputants can read the rules before they file — and most stop filing the hopeless ones.
- Distance: "the independent venue ruled" is a materially better customer conversation than "we decided to side with the other party." Your brand stops being the defendant.
- Proof before commitment: a 30-day shadow pilot runs our verdicts silently beside your team on your live queue — you get the agreement, speed, and cost report; we get measured, not trusted.
Integrate
// One clause in your ToS names the venue. One endpoint takes the queue:
POST /disputes // your order terms + message thread + deliverable, as-is
// Draft verdicts inside Zendesk via our sidebar app during the shadow pilot.
// Escrow release executes via signed webhook to your PSP or escrow partner.