DeliverMoney down. Work up.
Clients post a task and deposit the budget up front. A short list of vetted builders answers with working software — no interviews, no proposal piles. Every finalist is paid, and the pool pays out exactly as published.
Tasks that fit: Voice & chat assistants · AI agents & automation · API integrations · MVP rescue · UI from a design · Bug fixes
Four steps. Nothing else.
Post
Describe the outcome. We shape it into a spec with acceptance tests — you approve it.
Fund
Deposit the budget. The split is published up front — every finalist gets a guaranteed share.
Build
Vetted builders work independently, in sandboxes, under aliases. Every answer goes to everyone.
Get paid
Work is scored against the published tests; the pool pays out as published. Paid work transfers. Unpaid stays yours.
One budget, every finalist paid.
Example task · deposited before it goes live · 3 finalists, all paid
Pay to own: the client gets rights only to the deliveries they pay for. Everything else stays with its builder. The split is frozen the moment building starts.
Clients prove with money.
Builders prove with work.
Buy results, not promises
- Several working implementations for one fixed budget.
- Zero proposals to read, zero screening calls to run.
- Cost known on day zero — the split never changes mid-task.
- Compare tested results side by side, then take the strongest builder into production.
Ship first, talk never
- Qualify with work you've already shipped — never with an interview.
- The money is on the table before you begin — your finalist share is guaranteed.
- Unpaid work can't be used by the client. It stays yours.
- Win, and the client can take you straight into production. Still no interview.
Fair, by construction.
Deposit before work
No funded pool, no task. Prizes are cash in escrow, not promises.
Rules frozen at launch
Requirements, tests, deadline and split are locked once building starts. Every clarification goes to every builder.
Pay to own
Rights transfer only with payment. Unpaid submissions belong to their builders.
No silent exits
Client goes quiet? The pool still pays out under the published split.
Judged blind
Builders compete under aliases against a rubric published with the task. Names come after scores.
Results on a deadline
Judging has its own deadline, published with the task. No months of silence.
You'll ask these anyway.
Q–01Why pay several builders instead of hiring one?
Because early technical decisions are expensive to reverse. For one fixed budget you get several independently built, tested approaches — then you commit. Every finalist is paid for real work delivered; the strongest result takes the largest share.
Q–02Do I have to manage the builders?
No. We shape your goal into a spec with acceptance tests before anything is funded, coordinate the finalists while they build, and hand you the results as one side-by-side comparison. A question asked by one builder is answered for all of them.
Q–03Do I own all the code?
You own what you pay for. The winning submission transfers with payment and handoff — code, tests, deployment instructions, docs. During judging you get an evaluation licence: run it, test it, nothing more. Non-winning submissions stay with their builders; if you want one, you can buy it separately.
Q–04Will builders see my customer data?
No. Building happens in isolated sandboxes on synthetic or sanitized data, with keys we issue. Production access only exists in the controlled handoff — after you've chosen.
Q–05How is the work judged?
Against a rubric published with the task and frozen when building starts: automated acceptance tests carry the most weight, then technical review, then fit to your goal. Builders compete under aliases. Payouts follow the published score — and you always choose which solution goes to production.
Q–06What does it cost the client?
The pool you fund goes to builders — all of it. Our fee is added on top and shown before you deposit a cent. Checking whether your task fits costs nothing.
Q–07I'm a builder. What if I don't win?
You still get paid — every finalist has a guaranteed share, published before you accept the task. Your submission stays yours, and your scored track record is what brings the next, better-paid invitation.
Q–08How do builders qualify?
With work, not talk: shipped products, public repos, or one short qualification task. Verified once, then you're eligible for invitations. No calls, no CVs, no cover letters.
Doors open July 20.
Everywhere, all at once. Join the list — first funded tasks and first payouts happen launch week. Hiring? Your first task gets a free feasibility review before launch.