Escrow by default

Milestone escrow: money held until work is delivered

Every milestone is funded into escrow before work begins, and the money is released only when you accept the deliverable. Buyers never pay into the void; vetted consultants and firms never chase an invoice.

The problem

Payment puts both sides at risk.

On most engagements someone has to go first — and whoever does carries all the risk. Escrow removes that asymmetry by holding the money in the middle until the work is accepted.

01

Pay up front, hope for the best

Releasing budget before any deliverable lands means trusting a stranger with your money — and losing all leverage if the work never arrives.

02

Deliver first, chase payment later

Consultants and firms ship the work, then wait — invoicing, reminding, and absorbing the risk that payment slips or never comes at all.

03

No neutral place to hold the money

Without a trusted middle, every disagreement over scope or quality becomes one party's word against the other's — with the funds already spent or still owed.

How it works

Funded up front, released on acceptance.

When a contract starts, tokens for each milestone lock into escrow. The work proceeds milestone by milestone, and the money moves only when you accept each deliverable — never before.

Milestones are funded into escrow before work begins
Payment is held in escrow and released only when each milestone is accepted
Disbursement happens milestone by milestone — never one lump sum

Where escrow sits in the engagement lifecycle →

Escrow · Q3 Data MigrationIllustrative

1,200tokens locked · ~$4,188

Locked

Delivered

Review

Release

✓Milestone 1 · Schema audit300

✓Milestone 2 · Migration scripts450

·Milestone 3 · Cutover & QA450

Why it holds

Built in Switzerland, enforced in code.

Escrow is not a promise written in a contract — it is how the platform works. Payment is held in escrow and released only when each milestone is accepted, so neither side has to take the other on trust.