Oct 2024

Designing a Financial Ecosystem for Web3 Organizations

When I joined Parcel to lead the design efforts, we were riddled with user suggestions and features on our roadmap that were important but would evolve into product/tech debt a few months down the line. We took a step back and built something from the ground up that made our life easier and also helped users build healthier financial workflows.

Summary

The problem:

The industry standard for bulk payments was to maintain a CSV of amounts and addresses, and drop it in their tool of choice and pay.

Users were processing different types of payments (bills, reimbursements, payroll, grants, and airdrops) in the same transaction, which made it difficult for teams to coordinate.

Accountants could not act fast and were frustrated with poor metadata.

We were pre-revenue and found ourselves in a market filled with free tools.

What we built:

We built a compartmentalized spend management app supporting payroll, expense reimbursements, and bill payments. Each module was independent of the others and had features tailor-made for them.

All outgoing transactions, once reviewed, were listed in one place for final signatures and execution.

Accountants with a dedicated role so they had visibility to rich metadata across all their SAFE accounts.

The outcome:

Processed $100m+ in transactions while still in beta.

Reached $50k ARR in a category dominated by free tools.

Improved data accuracy and financial visibility across workflows.

Reduced reliance on external tools for tracking and reconciliation.

Screens

Payroll

A contributor's profile on Parcel.
Payroll processing UI with pay cycle information.

Expense Reimbursements

Requested Expenses page on Parcel.
Add Expense form on Parcel.

Bill Payments

Payments needing approval on Parcel.
A side drawer showing details of a bill payment seeking approval.

Transactions

SAFE transactions page on Parcel.
A side drawer showcasing SAFE transaction details on Parcel.

Bookkeeping

Bookkeeping UI on Parcel.
A side drawer showcasing transactions ready to be synced with QuickBooks.

Extras

Screen recording of a user entering their ENS in wallet address input.

On most apps, the ENS input doesn't reveal the underlying address, or lazily have it as a supporting text in the next line. This conflicts with the user's trust & familiarity with UI elements.

On most apps, the ENS input doesn't reveal the underlying address, or lazily have it as a supporting text in the next line. This conflicts with the user's trust & familiarity with UI elements.

Screen recording of a user navigating errors before making a payment.

Most apps check for errors post user's action and do not have meaningful messages when dealing with multiple errors. Some don't even show you the total before making a transaction.

Most apps check for errors post user's action and do not have meaningful messages when dealing with multiple errors. Some don't even show you the total before making a transaction.