open territory
The build you need does not exist yet. Put a bounty on it.
The catalogue only holds what someone already finished. The wanted board is the other direction: you describe the job, verified merchants claim it, and escrow holds the money until you accept delivery. Same rails, opposite order.
STEP 1
Nail the scope
One sentence a merchant can quote against.
STEP 2
State the bounty
A range is fine. No range means no claims.
STEP 3
Nail it to the board
Escrow opens only when you accept a claim.
Post a bounty
Three steps. Nothing leaves this device until you nail it to the board.
Posts here are held on this device for the prototype. Claims do not move money — escrow opens only after you accept a claim.
3 open bounties
wanted
Invoicing and dunning module for a B2B SaaS
Needs proration, retries, and a customer-facing billing portal. Happy to buy something battle-tested rather than build it.
- Bounty
- $3k – $6k
- Stack
- TypeScript / Postgres
- Posted by
- @ridgeline.io
- Age
- 2 days ago
wanted
Warehouse picking app with offline sync
Barcode scanning, conflict resolution, works on cheap Android handhelds. Will pay for full IP transfer.
- Bounty
- $8k – $15k
- Stack
- React / TypeScript
- Posted by
- @nordfulfil
- Age
- 5 days ago
wanted
Deterministic backtesting engine
Anything that replays tick data reproducibly. Certified builds only.
- Bounty
- $10k+
- Stack
- Rust / Python
- Posted by
- @quietalpha
- Age
- 1 week ago
Claims are ranked by merchant record, not by who clicked first. How verification tiers work.