Service

UI/UX design.

Interface and interaction design grounded in 20+ years across complex software and fintech products.

What it is

UI/UX design is the design of how a digital product works and how it feels to use. I cover both: UX — information architecture, user flows and wireframes that make complex tasks simple — and UI — the visual interface, components and interaction states. Grounded in 20+ years building banking software and leading product teams, the work is made for how products are actually built and used, balancing user needs, business goals and engineering reality.

Who it's for

For product teams, startups and software companies — especially in finance and fintech — that need complex interfaces made clear and usable. Suited to founders and product managers who want a designer fluent in both user experience and the realities of delivery.

Process
01
Research & flows
We map users, tasks and the flows that matter, framing the core problems.
02
Wireframes & IA
Structure and low-fidelity screens validate logic before visual design.
03
UI & components
A consistent interface with a reusable component and interaction system.
04
Prototype & handoff
Interactive prototype and dev-ready specs, with support through build.
Deliverables
User flowsWireframesUI screensComponent systemInteractive prototypeDev handoff
Selected work

FAQ

What is the difference between UI and UX?

UX (user experience) is how a product is structured and how easily people accomplish their goals — research, flows and wireframes. UI (user interface) is the visual layer they touch — layout, components, colour and interaction states. I design both as one process, so structure and surface reinforce each other.

Do you design for fintech and complex software?

Yes — that is the core background. With 20+ years in IT and 100+ banking-software projects, I'm at home with regulated, data-dense interfaces and the constraints of real engineering teams, turning complexity into something clear and usable.

Do you deliver a design system?

Where the product needs one, yes — a reusable set of components, patterns and interaction rules so the interface stays consistent as it grows and is faster for engineers to build.