Case study · Cross-border payments
Syro
A Web3 invoicing and cross-border payments platform built for speed, clarity, and global trust.
Personal note
I was the sole designer on Syro while the team chased a hard product thesis: make cross-border invoicing feel as normal as email—fiat and crypto in the same workflow, compliance included, without turning the UI into a trading terminal.
The short version: we had no template to copy. I built a desktop-first 0→1 platform—200+ screens, a design system, and flows that let small businesses move money without memorizing how blockchains settle.
01
Understanding the landscape
What made Syro different
Syro wasn’t just another invoicing app—it had to bridge the worlds of traditional finance and Web3. That meant designing a platform that felt familiar to small businesses while supporting advanced crypto functionality behind the scenes.
What kept surfacing in research — People didn’t want “crypto features”; they wanted invoices paid on time with less spreadsheet archaeology.
- Cross-border complexity — Businesses needed a faster, clearer way to send/receive payments internationally.
- Non-standard crypto invoicing — Traditional invoice tools didn’t support crypto assets, chain settlement, or multi-currency contracts.
- Compliance & trust — KYC, KYB, and AML requirements had to be woven into the experience without adding friction.
- Mixed payment reality — Many invoices combined fiat and crypto, requiring flexible tracking models.
- Zero-to-one desktop MVP — With no existing baseline, every workflow, pattern, and system had to be created from scratch.
02
Defining the core problem
Where users struggled
During research, patterns emerged around how difficult it was for small teams to manage cross-border invoicing:
- Fragmented tools — Users juggled spreadsheets, wallets, banking apps, and manual calculations.
- Unclear money flow — People lacked visibility into wallet balances, incoming/outgoing payments, and invoice status.
- Crypto confusion — Most users didn’t understand chains, tokens, or settlement behavior.
- Regulatory overload — Compliance flows were intimidating, unclear, or overly rigid.
- No existing standards — There was no template for crypto invoicing; the UX needed to define best practices.
These insights shaped the core design direction: simplify the interface, clarify financial flows, and hide complexity behind intuitive patterns.
03
Designing a clearer experience
What I focused on
My goal was to create a desktop platform that felt powerful, modern, and trustworthy—while making complex processes feel simple.
- Dashboard clarity — Surfaced wallet balances, transactions, and invoices immediately on login.
- Atomic design system — Built a modular system enabling 200+ production-ready screens.
- Compliance by design — Integrated KYC, KYB, and AML flows that balanced security with smooth onboarding.
- Cross-currency flexibility — Enabled invoices in both fiat and crypto, with partial, recurring, and mixed payments.
- Lean collaboration — As the sole designer, worked daily with founders and developers to shape product direction and iterate quickly.
04
Results & impact
Crypto-friendly invoicing
The final experience delivered one of the first platforms that seamlessly blended Web2 simplicity with Web3 financial infrastructure.
- 200+ production screens — A fully functional 0→1 invoicing platform ready for alpha launch.
- Instant financial visibility — Users immediately understood wallet balances, transactions, and invoice activity.
- Regulatory confidence — KYC, KYB, and AML built directly into the experience.
- Cross-border speed — Enabled global payments using stablecoins, drastically reducing friction.
- Scalable foundations — The design system supported future features, subscription layers, and advanced workflow automation.
Early feedback showed users were able to send invoices faster, understand their financial picture more clearly, and onboard into crypto invoicing with far less confusion.