Controls engineer turned software builder. 22 years building systems that work, now building the software that runs the businesses that build them.
Connect on LinkedIn
The Story
From the Shop Floor to the Software
I started in controls engineering at 18 — wiring panels, programming PLCs, commissioning systems across small integrators, mid-sized OEMs, and a multi-billion dollar global electronics manufacturer. Over 22 years I watched the best technical people drown in administrative work: quoting, emailing, status updates, rework. The Builder's Trap.
The answer was never more headcount. It was systems. So I started building them — AI-powered workflows that sit between the tools we already use. Proposals in hours instead of days. Automated follow-ups. Knowledge that stays in the system even when people don't.
Today I run a solo consulting practice with team-level output. I built the software that runs my own business first, and it is still the one I use every day. Now I build the same kind of thing for other SIs, OEMs, and machine builders.
Philosophy
What I Believe
Just Ask
The fastest way to get AI working is to talk to it like a person. No prompt engineering, no complex setups. Just ask, see what happens, refine.
Layers Not Leaps
You don't need to automate everything at once. Start with context, then data, then intelligence, then automation. Each layer compounds on the last.
Build for Scale & Security
Every system should be built to hand off. Document it, secure it, make it repeatable. One-off hacks are technical debt disguised as progress.
Systems, Not Labor
The answer to too much work is never more people. It's better systems. Encode the pattern once, let it run forever.