Challenge
Financial products fail when trust, workflow, and business architecture are designed as separate layers. EQTY needed a modular operating system that could hold high-trust financial experiences without burying operators in complexity.
SaaS Products
EQTY
A modular fintech operating system, from strategy to architecture
- Role
- Founding design partner
- Timeline
- Ongoing
- Engagement
- Product strategy and experience architecture
Approach
- 01
Joined as founding design partner — shaping product strategy and experience architecture together, not handing over screens after the system was already decided.
- 02
Mapped the operating system as modules: how money, people, and decisions move, and where trust has to be visible in the interface.
- 03
Designed workflows for operators who need clarity under load — fewer dead ends, clearer states, and language that matches how finance teams actually work.
- 04
Kept the visual system quiet so the architecture could carry the product: hierarchy, restraint, and a structure that can grow without a redesign every quarter.
Outcome
Strategy in the product
Experience architecture is part of the operating system, not a coat of paint applied after the modules were locked.
Trust as a design problem
High-trust financial work is treated as workflow and language, not as a marketing claim.
A system that can extend
A modular structure so new financial surfaces can join the OS without fracturing the operator experience.
Frames
Have a similar challenge?
Start a conversation.
Next — Growing With Kid: A parenting community built around one clear job