Features are easy to add. Knowing when not to add them is harder. The case studies below show how I approached those decisions across three very different products.
Read the case studies Contact me
More than a decade spent close to customers, in marketing, customer research, and customer success, as well as two years as a project manager running ten to fifteen client projects at a time with creative and development teams. Now I build the products myself.
6 restaurant clients running
Crewli today
3 products designed, built,
and shipped
10+ years working directly
with customers
Case studies
Live with clients
Restaurant operations platform
Crewli began as a digital replacement for the binder every restaurant already had. Customer conversations revealed a different problem entirely: owners wanted confidence that work had actually happened. That shift changed the product far more than any feature request.
In closed testing
Android habit tracker
Every other habit tracker treats a day you never logged as a zero, which quietly hands out streaks nobody earned. This one treats it as unknown. That single rule decided the data model, the calendar and the business model.
Unlisted by design
Technical fluency for non-engineers
The gap was never learning to code. The gap was learning how software works well enough to make better product decisions. Everything in the curriculum follows that idea.
Open to work
If you're hiring, or you want to talk about anything on this page, the fastest way to reach me is below.