kaedax

Marketplace · 720-hour cycle

Marketplaces engineered
for liquidity.

kaedax builds two-sided marketplaces — services, goods, B2B procurement — in a fixed 30-day (720-hour) cycle. Marketplace engineering is liquidity engineering: supply onboarding that doesn't leak, matching that converts, payments with escrow and splits, and the trust systems that keep both sides from going around you.

ops.atrium.market/liquidity

Fill rate

78%

+14 wow

Time to match

3.1h

p50

Escrow held

$214k

auto-recon

Dispute rate

0.8%

p50 36h close

RequestBuyerMatchesEscrowStatus
CNC fabrication · 40 uVolta Labs4 quotes$12.4k matched
Industrial designFern Goods2 quotes quoting
PCB assembly · 500 uKestrel IoT6 quotes$28.0k in escrow
Injection moldBough Co1 quote thin supply
Packaging runPulse Snacks5 quotes$6.2k delivered
connect payouts ✓ · kyc queue 2 · supply alerts armed · recon clean
representative build · web console + mobile · anonymized under NDA
Try atrium — live marketplace-ops demo

[ §01 ] the problems we're hired for

Where marketplaces builds
actually go wrong.

01

The cold-start problem is an engineering problem too

Chicken-and-egg is strategy, but supply onboarding friction, empty-state design, and single-player utility are engineering. We build the surfaces that make a thin marketplace useful at day one, so your supply acquisition spend isn't wasted on a leaky funnel.

02

Marketplace payments are nothing like checkout

Escrow, split payouts, refunds across two parties, KYC on sellers, marketplace-of-record liability — getting this wrong is existential. We build on Stripe Connect or equivalent rails with reconciliation jobs from day one.

03

Disintermediation eats your take rate

The moment both sides trust each other, they're motivated to go around you. The defense is engineered: in-platform value (escrow, insurance, dispute resolution, scheduling) that makes leaving costlier than your fee.

04

Trust systems are the product

Reviews that resist manipulation, verification flows, dispute resolution with evidence trails — the unsexy systems that decide whether transaction #10,000 happens. They're in our first spec, not your post-launch backlog.

[ §02 ] what ships

One cycle.
Production, not prototype.

The shapes of marketplaces work that fit a 720-hour cycle. Every build ships with runbooks, monitoring, and 30–60 days of post-launch on-call.

Seller KYC Escrow & splits Dispute evidence trails Review integrity
[01]

Two-sided platforms

Buyer and seller surfaces, onboarding funnels for both sides, empty-state-aware UX.

[02]

Matching & discovery

Search, filters, ranking, and recommendation surfaces tuned for conversion on thin supply.

[03]

Marketplace payments

Escrow, split payouts, refunds, seller KYC — on Stripe Connect rails with reconciliation jobs.

[04]

Trust & dispute systems

Reviews, verification, dispute workflows with evidence trails — the moat against disintermediation.

[ §03 ] proof

all case studies →

Escrow, KYC, payouts — the scary parts were done by week two. We spent the rest of the cycle on matching, which is the part that actually wins the market.

Oskar Lindqvist

Oskar Lindqvist

Founder · home-services marketplace, Nordics

[ §04 ] questions

Marketplaces founders
ask us first.

01

How much does it cost to build a marketplace?

+

Market quotes for two-sided marketplace MVPs run $50,000–$250,000 over 3–6 months, with payments and trust systems driving the spread. kaedax prices per fixed 720-hour cycle, shared on the scope call. One cycle ships both sides plus payments.

02

How do you handle marketplace payments, escrow, and payouts?

+

Stripe Connect or equivalent rails: escrow, split payouts, two-party refunds, seller KYC, and reconciliation jobs from day one. Marketplace payments are a different discipline from checkout, and we treat them that way.

03

Can you build for the cold-start phase?

+

Yes — empty-state design, single-player utility, and low-friction supply onboarding are engineering choices we make deliberately. Our ATRIUM engagement shipped a marketplace built for thin-liquidity day one.

04

How do you prevent users from going around the platform?

+

Disintermediation defense is engineered: escrow, dispute resolution, scheduling, and insurance live in-platform so leaving costs more than your take rate. We design those hooks into the first transaction flow.

05

Is 30 days enough for a two-sided platform?

+

One cycle ships a focused marketplace: both sides, matching, payments, and core trust systems. Deep verticalized features (logistics, insurance, financing) typically land in a second cycle — we map this on the scope call.

Fits a cycle,
or we say so.

A 15-minute scope call with a kaedax founder and the engineer who'd lead your build. We either fit your marketplaces product into 720 hours, or we tell you why not — same call.