Return to homepage
Read next case study

ENUM8 — Global Business Accounts, Fiat and Crypto

Context

Enum8 gives businesses global accounts that treat bank rails and crypto as one system: multi-currency wallets, crypto addresses, conversions, and transfers over SEPA, SWIFT and Tron. I designed the entire product and the marketing website solo, from mid-November to the end of December, through the holidays. The product is live; access is account-gated, screens are published with the client's permission.

My service

A full fintech product designed in 4 weeks. One designer end-to-end.

Year

2025

The Constraint

Six weeks for everything: information architecture, every flow, every state, the design foundation, and the public website. No existing designs to build on.  At that pace, every decision had to be made once and hold.

Decision 1 — Split onboarding at the first screen

Business accounts need KYB-grade signup: company fields, roles, compliance checkboxes. Personal users bounce off forms like that. I branched the flow at the entry point: a light personal signup, a six-field business path, and error states designed upfront for both, plus passwordless entry via magic link and a full reset flow. Unhappy paths were part of the spec, not a patch after launch.
One entry point, two paths: the account-type choice, the light personal signup, and the KYB-grade business form with errors designed upfront.

Decision 2 — One transfer model across all rails

Users think "I sent money", not "I used SWIFT". A SEPA wire, a SWIFT payment and a USDT transfer on Tron live in one transaction history with one status language: Created, Processing, On hold, Completed, Failed. Crypto transfers read with the same clarity as bank wires, which is where trust in a product like this is actually won.

Three rails, one status language: Created, Processing, On hold, Completed, Failed.

Decision 3 — Wallets as cards, not rows

A business on Enum8 holds euros, dollars and USDT side by side, and the first question on every visit is "where is my money and in what". A table answers that through reading; cards answer it through recognition. Each wallet is a card led by its currency mark, so a mixed fiat-and-crypto balance scans in a glance, and crypto wallets sit next to bank accounts as equals, not as a separate exotic tab. The wallet section became the home screen logic: recognize, then act.

Wallets as cards: a mixed fiat-and-crypto balance reads in a glance.

The rest of the surface

The three decisions above set the system; the rest of the product ran on it. The same six weeks covered crypto address management, fiat-to-crypto conversions, the full transfer creation flow, and profile with security settings, all built from the same components with the same state discipline.

Same system, more surfaces: crypto addresses, conversions, transfer creation, profile and security.

Outcome

Shipped on deadline: live product, public website, developer-ready Figma with components and documented states. Designed to be built without the designer in the room.

Return to homepage
Read next case study