MY PROCESS
I’ve been designing and building products for more than twenty years: in product studios and SaaS companies, on compliance-heavy platforms, for owner-led businesses and, lately, for myself. If that variety has taught me anything, it’s that the method has to come from the problem. A brand-new idea and an established platform need very different things from a designer, and most of the skill is telling which is which before reaching for a tool. So every project starts with the problem: I bring what it needs and leave out what it doesn’t.
How that plays out
A few situations that come up again and again, and what I reach for in each.
A brand-new idea
Here, learning fast matters more than polish. I get a working prototype into people’s hands within days, then let what they actually do, rather than what they say they’d do, decide what comes next.
Seen in Schedgy
A platform with many sides
Students, schools, agents and host families all want different things from the same product, and guessing between them gets expensive fast. So this is where I slow down: I run discovery with every team involved and map each role and journey before a roadmap gets written.
Seen in Greenheart Exchange
A business running on spreadsheets
Owner-led businesses rarely need a workshop. They need someone who’ll stand in the kitchen, go through the invoices and see where the hours really go, then design and build the system that gives those hours back.
Seen in Shubh
Several teams, one product
Once several teams and brands build on one product, drift becomes a bigger risk than speed. That’s when I build the design system underneath it, accessible to WCAG 2.1, so everyone can move quickly and it still feels like one product.
Seen in Enroller
What doesn’t change
The person using it
Every decision starts with what they’re trying to get done, and what’s quietly getting in their way.
Engineering in the room
I bring developers in from the start and test ideas in code, against what can really be built.
Evidence over opinion
Research and real usage settle the big calls, so the work stays aimed at the right problem.
SKILLS
What I bring across the whole lifecycle: understanding the problem, designing the solution and building it.
End-to-end product design
From data-driven discovery to pixel-perfect, engineering-ready UI, owned across the full journey.
Research & discovery
Turning messy, fuzzy problems into clear direction through structured research and synthesis.
Solution design & full-stack build
Architecting the whole system, then building it myself: data model, integrations, payments and the interface on top.
Automation & AI agents
Taking the manual work out of a business, from invoices read by AI to agents that answer questions and make approved changes.
Design systems & craft
WCAG-compliant systems and hands-on UI craft that engineers can ship without guesswork.
AI-assisted delivery
Using generative AI to research, prototype and build faster, from insight to shipped product.