Designing a unified Web3 ecosystem from zero to 500K+ users.
Overview
I joined Haven1 at day zero to lead product design strategy from a blank canvas to a full blockchain ecosystem. I stayed hands-on designing core apps while simultaneously building the design function. This included hiring and mentoring designers, establishing internal processes, and creating a scalable design system that unified 7 products.
- Lead Product Designer
- 0 -> 1 -> Scale
- 2 PMs
- 12 Engineers
- 3 Designers & 1 QA
- Product Design - Visual & Interaction
- User Research
- Product Strategy & Prioritizations
Impact
In two years, Haven1 grew from zero to 500,000+ wallets with over 100,000+ fully KYC'd users, a rare feat in DeFi. Design played a central role in making that level of trust feel achievable for everyday users, not just crypto natives.
Over $2B lost to DeFi hacks and scams in 2023
These weren't edge cases. Hacks, scams, and bad UX cost people real money. Those responsible rarely faced any consequences. For anyone trying to build something trustworthy in that space, the first challenge wasn't the technology. It was earning trust the industry had already burned. So we built Haven1 from the ground up to feel different. Starting with the foundation.
Mixin Network
$200M
Multichain
$210M
Kyber Network
$54.7M
One system, 7 products
The early screens got us moving, but they were built fast. Inputs, buttons, and layouts varied just enough to feel off across products. So we built the system from tokens up. Color, typography, spacing defined at the base level, never hardcoded. Components built on top. Every screen after that built on top of those components. It was a trust decision as much as an efficiency one. In a space where users are already skeptical, consistency isn't just a design value. It's a signal.
The foundation covered everything. A full color token system across brand, neutral, and semantic values. A single typeface applied consistently across all products. A custom icon set. A component library used across 7 products.
Built lean, built right
The goal was never a perfect system. It was a system that worked without hand-holding. At the time I was the only designer, onboarding a new hire, and working closely with engineering.
That included providing the initial JSON token structure so tokens translated into code without misinterpretation. In a startup, resources are tight. Building it right the first time was the only option.
Building around the user journey
There weren't many references for what we were building. A permissioned DeFi portal with verified apps, KYC'd users, and a deliberate onboarding path didn't really exist yet. So we started from first principles.
As the ecosystem grew, so did the Portal. The flat nav became grouped by user intent. Overview, Trade, Earn, Others. Nested navigation was added for products like Stake. The hApp Store gave users a way to discover and filter verified third-party apps alongside native protocols.
The layout isn't decorative. Every decision, the nav order, the hero nudge toward Bridge, the hApp Store placement, reflects how a user actually moves through the ecosystem. Design and product aligned on that from day one.
What it added up to
The best feedback wasn't in a report. It was in how people talked about the product.
Over two years, Haven1 grew from zero to 500,000+ wallets. More than 230,000 of them fully KYC'd, a rare number in a space where most users avoid any kind of identity verification. 7 products shipped. One design system holding all of it together.
Those numbers didn't happen despite the design constraints. They happened with three designers, no process playbook, and a lot of decisions made in real time.
Looking back
Building this much with a small team is what I'm most proud of. Not because it was hard, but because the work held up. If I started over I'd reach for an existing token framework like Tailwind instead of building from scratch. The outcome would be the same, but faster. What I wouldn't change is the decision to build systematically from day one. In a space defined by chaos, that was the right call.