Reimbursement for Onchain Teams
Reimbursement for DAOs, built as a thin layer on top of Parcel's existing payroll, payments, and bookkeeping, turning an improvised Discord-and-spreadsheet process into one connected request-approve-pay loop.
PROJECT DETAILS
Industry
Web3 : Parcel Inc
Role
Product Designer
Team
1 designer (me), 1 PM, 3 engineers
Outcome
Shipped as a new module on the platform, helped land 3 new clients and a ~20% revenue lift
Read full case study here
Overview
Parcel is a finance platform for on-chain orgs; expense management was the fourth module after payroll, payments, and bookkeeping.
Reimbursing a DAO contributor meant a receipt dropped in Discord, a spreadsheet in someone's head, and a manual multisig send.
Fine at five people, broken at fifty: the request, approval, and payment lived in three disconnected places.
Contributors fronted their own money, then heard nothing: seen, approved, paid this month or next?
Spent in dollars but paid in crypto, the hand-done conversion drifted by payout time and left people short.
The approach
Sole designer; 1 PM, 3 engineers; 3-week core release, then phased delivery.
The key move: this wasn't a new product. Contributor identities, money rails, and categorization already existed, so expense management only had to compose them.
Built the smallest surface that still reads as one product, in the same sidebar as the rest.
Designed for two different questions: the contributor's "where's my money?" and the treasurer's "what needs me now?"
Locked the fiat-to-token conversion at submission, so the contributor's number is a promise, not a moving target.
The Solution
Treasurer side organized by stage: submitted, reviewed, approved, ready to pay, history, with count badges surfacing the backlog.
Approve and pay kept as separate verbs and separate records, so a public-chain payment has an honest reason attached.
Batched payouts default at the month-end run, broken down per token with a warning when a balance can't cover its share; Parcel covered gas so the cheap path was the efficient path.
A treasurer can file an expense for someone, but the contributor stays the author of record and no one can add-and-clear alone.
Contributor side is deliberately smaller: a status ledger that closes the black hole, report-only with no self-approval, and a withdraw escape hatch.
The result
Shipped expense management as a new module on Parcel.
Helped land 3 new clients and a roughly 20% revenue lift.
Next: receipt scanning (OCR) to pre-fill from uploads, then a contributor mobile app where the status ledger becomes the thing they live in.
