An inventory management system for a Fortune 100 food manufacturer: rebuilt around the operators who depend on it every day, not the database underneath.



For Enterprise SaaS & Healthcare teams, CPOs, founders, and product leads who need one accountable senior designer owning research, systems thinking, execution, and handoff.
Selected work
2 case studies
Sole designer, end to end
An inventory management system for a Fortune 100 food manufacturer: rebuilt around the operators who depend on it every day, not the database underneath.



SMS and multichannel campaign management for CEQUENS: designed so that marketers can plan, build, and send campaigns without leaning on a developer.



Approach
Research → Systems → Execution → Handoff
I design complex, high-stakes SaaS products, mostly as the sole designer. Compliance-heavy, multi-stakeholder products for the US market, where getting it wrong is expensive and getting it right is invisible.
Eight-plus years across Enterprise SaaS and Healthcare. Clients have included Tyson Foods, BD, Ontellus, and CEQUENS, two of them Fortune 500.
No agency layers, no account managers. The person you talk to is the person doing the work.
I design how a product thinks and scales, not only how it looks.
Research, systems, execution, handoff: owned end to end.
Compliance-heavy, multi-stakeholder, high-stakes domains.
Process
Three steps, no ceremony
We talk about your product, your constraints, and what you actually need. You ask anything; I tell you honestly whether I’m the right fit.
If it’s a fit, you get a written proposal: the problem as I understand it, the engagement model, the timeline, and exactly what you receive.
Work begins with research and immersion in your domain, then moves through systems thinking to execution and a clean handoff.
The engagement
One offer, scoped up front
I go through your product the way a new customer does, then report where the experience is costing you money. Not where it looks wrong.
Enterprise software rarely fails on craft. It fails on activation that never lands, admins who stall before they can succeed, AI surfaces a buyer cannot verify, and migrations that arrive at the worst possible moment. Those are revenue events, and they are close to invisible from inside the team that built the thing.
Longer engagements exist. Sprints, full product design, embedded partnership. They start here.
FAQ
5 questions
I do. There’s no agency behind the name and no work handed down to juniors. I work as the sole designer on every engagement, owning research, systems thinking, execution, and handoff myself.
Complex, high-stakes SaaS: mostly Enterprise and Healthcare, often compliance-heavy and multi-stakeholder, built for the US market. Recent work includes an inventory management system for a Fortune 100 food manufacturer and a multichannel campaign platform for CEQUENS.
Three steps: an intro call to understand your product and constraints, a written scoped proposal so you know exactly what you’re getting, and then kickoff. No long sales cycle, no ambiguity about scope.
Yes, and it happens often. But it isn’t where an engagement starts. The audit comes first, because embedding without knowing what’s actually wrong is how a retainer turns into hours. If the findings warrant ongoing work, we talk about it then.
Two weeks. It’s fixed scope by design. You get a written proposal before anything starts, so the boundaries are set before you commit, and half the fee is due on booking.
Contact
Available for new engagements
Your product carries the complexity. Your users shouldn’t.
Prefer email? Write to hello@muhh.design. Same person answers either way.