Assembly
Contributor payouts with a paper trail
Client identities and brand marks are anonymised. Names, logos and interfaces shown are not real companies or real projects.
- Sector
- Distributed organisations
- Location
- Dubai, UAE
- Year
- 2026
- Kickoff to production
- 13 weeks
Operations software for a distributed organisation paying 214 contributors across nine countries without a payroll department.
Contributors submitted hours in a chat channel and were paid by whoever held the wallet that week. Nobody could say what a workstream had cost, and two people were paid twice in the same month.
Approved by a role, not a friend
Every submission is approved against a role with the trail stored beside the payout, so an approval survives the approver leaving.
One run, one batch
Approved work becomes a single payout batch with duplicate detection, so the same hours cannot be paid twice.
Cost per workstream, visible
Spend rolls up by workstream and month, which gave the organisation its first honest budget conversation.
Payout day went from a multi-day scramble to a short review, and duplicate payments stopped entirely.
What changed
- Payout review
- Minutes
- Contributors paid monthly
- 214
- Since launch
- Zero duplicates
- Next.js
- Postgres
- Temporal
- Vercel
- Safe
Tell us what's slowing you down.
Fifteen questions, one screen at a time, and a verdict at the end. No call needed to get it.