Complex systems
I've worked across warehouse operations, ERP/WMS, robotics, and distribution — enterprise environments where the business needs, the technology, and the people all had to stay aligned.

Because at the end of the day, it’s never really about the system. It’s about the people who have to live inside it.
I ask a lot of questions. Not because I don’t know what I’m doing — because the real problem is rarely the one people describe first.
I watch what people say, what they don’t say, and where the friction actually is. That takes time. But it’s usually the only way to see what’s really going on.
My soft skills are what make my hard skills useful.
Once I understand the people and the problem, figuring out what actually needs to change — technology, process, or just how everyone’s working together — is the easy part.
Whether or not I’ve had the title, I’ve always ended up playing the same role — the orchestra director. Developers, business people, leadership, clients — everyone’s playing their part. My job is understanding how those parts fit together, keeping the group moving toward the same outcome, and hearing something’s off before anyone else does — adjusting early enough that the audience never even knows there was a problem.
I believe you can be kind and still hold people accountable. You can listen and still make decisions. You can trust your team and still get deep into the work when something needs to be understood or fixed.
I've worked across warehouse operations, ERP/WMS, robotics, and distribution — enterprise environments where the business needs, the technology, and the people all had to stay aligned.
I've led and contributed to product, ecommerce, and customer experience work across organizations, where the technology had to solve a real business problem — not just ship features.
I've built long-term client relationships, led teams, coordinated across functions, and helped move complex work forward by building trust and getting to the real issue.
The industries and technologies keep changing. What doesn’t: understand the people, understand the problem, then build what actually helps.
I’ve spent my career building. From automated workflows, websites, custom software solutions, and AI agents, just to name a few. I’ve used AI to research, organize, write, analyze, and work more efficiently, across roles, companies, and my own projects along the way.
The point isn’t to use AI because it’s new, or because everyone says you should. A lot of AI adoption right now makes work harder, not easier: more tools, more noise, no real benefit. My job, with AI or with anything else, is figuring out where it actually helps: saving time, saving money, or just making the work better. Usually it’s some combination of all three.
For small businesses especially, that matters. Technology that once required large teams and large budgets is becoming more accessible. I see that as an opportunity to help smaller organizations compete, experiment, and build capabilities they may not have had before.
The tools keep changing. The goal doesn’t: create something that makes people’s work or lives a little better.
I’ve been interested in technology for as long as I can remember. Over time, I learned how to take that, along with a love for figuring out how things work, and apply it to how businesses actually run.
From there, the roles changed: business analysis, product, consulting, operations, leadership, and eventually building my own company, and building things on my own too.
The titles mattered less than the pattern. Each step pulled me closer to the place where people, business, technology, and execution actually meet.
I’ve worked inside large organizations, consulting environments, digital businesses, operations teams, and my own ventures. Different settings, different problems. But the same need to understand what is really happening and help people move forward.
If this sounds like you, let’s connect. I’m always curious what we could build together.