What I Believe

Technology should serve the business model, not be the business model. I don't start with tools — I start with problems. If the answer is a spreadsheet, I'll tell you. If it's a custom system, I'll build it. But I'll never sell you technology for the sake of technology.

The best system is the one you don't have to build. I use open-source tools, existing integrations, and off-the-shelf solutions where they fit. I only write custom code when nothing else will. Every piece of tech you deploy is another thing you have to maintain — so I keep the footprint small.

A well-structured database isn't a nice-to-have — it's the backbone of everything that comes after. Automation, reporting, AI, internal tools — all of it depends on clean, connected, reliable data. Enter it once, use it everywhere, trust it completely.

If your systems only work when I'm around, I've failed. Everything I build is designed to be maintained by your team — not a team of engineers. If a non-technical operator can't understand it, it's too complicated.

Most consultants see software problems. I see business problems. That's because I've been the one dealing with late shipments at 2am, not the one reading about supply chain in a case study. That perspective changes what I build and how I prioritize.

AI is a tool, not a strategy. I deploy it where it eliminates real work — data entry, classification, pattern detection, decision support. Not where it sounds impressive in a board meeting.