I help teams launch faster by fixing misalignment between product, design, and engineering. Fewer delays. Less rework. Better outcomes.
Handwave
First biometric payments app. Palm scanning UX with no existing patterns.
Certified, award-nominated designer helping teams ship better products
For 10 years, I've joined early-stage teams at their most chaotic stage. From first rough concept and messy backlog to first paying customers and real usage. I help teams ship and land their first customers.
I use AI copilots across discovery, UX writing, and QA to shorten iteration cycles, catch edge cases earlier, and turn vague requirements into build-ready tickets.
Earned in 2026: AI Product Management certification by Product Faculty and UX certification by Nielsen Norman Group.
At early stage, there's usually no product manager. No clear process. The founder becomes strategy, PM, QA, and support. By default.
Founder
Hired a designer. Product is covered.
Dev
Half the decisions are not made. I cannot build this.
Designer
I designed what you asked for.
Founder
Then who owns this?
Everyone did their job. Nothing shipped the way it should. Early stage teams don't need more handoffs. They need someone who owns product clarity end-to-end.
Here's what actually happens.
Had an MVP but no clear path to a complete product. Joined to own it end-to-end - feature definition, full UX including palm scanning (no patterns existed), and the process to take ideas from concept to shipped.
WordPress MVP, growing merchant base, replatforming coming. Joined to lead end-to-end product design from scratch through implementation.
Joined an 18-year-old reinsurance governance system built around workarounds, not real decisions. Stepped in mid-sprint, mapped stakeholder workflows, and led an end-to-end redesign without breaking critical routines. Improved task completion by 80%.
Most founders think they need UX. They need product structure.
A typical designer stops at the file. I redesign, validate against real edge cases, align with engineering, and hand over something that is ready to build.
Before pixels, we define trade-offs: what matters most, what we're not building, and why. Scope, priorities, and decision logic are clear before anyone opens Figma.
A designer escalates open questions. I resolve data gaps, logic issues, and edge cases before development begins, so you're not answering implementation questions at midnight.
A designer delivers a file. I stay through sprint, QA, and launch, working closely with engineering, resolving edge cases, adjusting details in real-time, and making priority calls when trade-offs appear.
Two ways, depending on what you need.
6-12 week sprints to ship specific features or products from concept to launch
Who is This For?
Ongoing product ownership—I become your head of product without the full-time cost
Who is This For?
