I turn complex product problems
into structured,
shippable systems.
Senior Product Designer and Web Developer specializing in fintech, cross-border payments, and enterprise platforms.
Object-Oriented UX (OOUX) and the ORCA methodology give every product I design a structural backbone before a single wireframe is drawn. Then I build it in code. Most designers do one of these. I do both.
← Replace with real artifact
Hero Image Brief — 1200×480px, PNG/WebPExport a clean ORCA map from Figma or Miro for CrossBorda or Zuniq. Dark background (#0D0D0D), gold (#D4AF37) node labels and relationship lines, 4 object nodes (Beneficiary · Transaction · KYC Document · Payout Corridor) connected by directional arrows. No whiteboard photo — export as a crisp vector graphic or high-DPI screenshot. This is the single artifact that proves the methodology in one glance.
Structure first. Screens second.
Design is an architecture problem first.
Most product failures aren't design failures — they're structural failures. A screen that looks right but sits on a broken object model will confuse users and break engineers.
Before I sketch a single screen, I map the system: every object, every relationship, every state, every action. This gives design, engineering, and product a shared structural language — so nothing gets lost in handoff and nothing breaks at scale.
Then I implement what I design. React, Next.js, WordPress, custom CMS — I take systems from whiteboard to working product.
Read the full approachObjects
The core entities in the system — named before any screen is drawn.
Every product has a handful of objects that everything else revolves around. For CrossBorda, that was Beneficiary, Transaction, KYC Document, and Payout Corridor. Naming objects first eliminates entire classes of navigation and layout debates.
Relationships
How objects connect to each other.
A Wallet belongs to a User. A Transaction references a Corridor and a Beneficiary. Mapping these before design prevents the structural mistakes that only show up in engineering — when it's expensive to fix.
Calls to Action
What can be done to each object — CTAs emerge from structure.
Initiate Transfer, Verify Identity, Submit Attempt. When CTAs are derived from objects and relationships, every button has a home. Nothing floats. Nothing is duplicated. The information architecture writes itself.
Attributes
The data each object carries — attributes define UI states.
KYC Status, Balance, Completion %. Listing attributes per object reveals every possible UI state before design begins. You can't design a component properly until you know what states it needs to handle.
← Image Brief: 760×420px
ORCA map from CrossBorda or Zuniq. Objects as nodes (dark background, gold labels), directional arrows showing relationships, attribute list beneath each node. Export from Figma or Miro at 2× as PNG/WebP. Caption: "ORCA map — CrossBorda, 2024."
Three capabilities. One integrated practice.
Product Design
Structured experiences for complex systems.
- —End-to-end product design (Web, Mobile, TV)
- —System architecture before wireframes
- —Complex flows: payments, KYC, onboarding
- —UX strategy & interaction design
Web Development
I ship code, not just specs.
- —React & Next.js frontend development
- —WordPress (Elementor, headless, custom CMS)
- —Performance optimization
- —Low-code prototyping & API integrations
Systems Architecture
Design decisions with business consequences.
- —Object mapping for product clarity
- —Fintech systems & payment flow design
- —Information architecture at scale
- —Cross-platform design systems
“I approach product design as a system, not a screen.”
Most designers think in pages. I think in flows, states, and edge cases — because that's where products actually break. Every decision I make holds three things simultaneously: user needs, business goals, and technical constraints.
I don't design in isolation. I don't hand off and hope. I build — because implementation reveals what design alone cannot.
Selective availability. Specific expertise.
Enterprise & Fintech Clients
Building a complex payment system, KYC flow, or multi-platform product? I bring structured systems methodology + production code to your most difficult design problems.
Discuss a ProjectConference & Event Organizers
I speak on systems-first product design, fintech UX, and the design-to-code practice. Every talk is grounded in real shipped products — not slides about theory.
Check AvailabilityDesign Leadership
Evaluating for a Head of Design or fractional design lead role? Review the full case studies and methodology before reaching out.
See the WorkI take 2–3 projects per quarter. Currently available for Q3 2026.
Let's build something that scales.
Whether you need a design partner for a complex product, a speaker for your next event, or a collaborator who bridges design and engineering — start here.