15 years finding where the real problem is — before recommending a fix.
A decade at Intel, and a decade building things on the side. Same method, different scale.
I spent 15 years at Intel, starting as a software engineer and ending as an Engineering Director leading teams across the US, Mexico, Costa Rica, Malaysia, and India. Along the way I learned one thing that mattered more than any technology: most inefficiency isn't caused by a lack of tools. It's caused by nobody having mapped out where the process actually breaks down.
I've spent that same decade building things on the side — a travel deal tracker, an AI meal-planning app, a school communication portal, tools that keep content and project data in sync. Different domains, same underlying pattern: find where work is manual, scattered, or repeated by hand, and design a system that removes the friction.
Why I do this now
Small and mid-size businesses are being told constantly that they need AI. Most of that advice comes from people who've never run a P&L, negotiated with a vendor, or had to explain a decision to a team of twelve. I've done all three. I know when AI is the right tool, and — just as importantly — when it isn't.
How I work
- I start with your business, not with a technology stack.
- I look for the few changes that matter, not a long list of "nice to haves."
- I build and integrate the systems myself, so recommendations don't stall.
Based in Phoenix, AZ — working with businesses locally and remotely.