About

How I got here.

I'm a product manager at MindTechSourcing. I work on a workflow platform that helps teams move through high volumes of work without losing track of who did what, when, and why. The part I'm focused on now lets AI agents take on real pieces of that work.

I'm at my best where messy operations meet software. The volumes are high, the requirements keep moving, and there's usually a real gap between what a team needs and what the tool actually does. Closing that gap is the work.

Understand how the work actually happens before you try to change it.

Manufacturing

None of this started with software. My career started on the floor of a manufacturing plant, leading process improvement in soap production. It's more complex than it looks: dozens of transformations, plenty of places for things to quietly go wrong. I introduced Lean when the company had never worked that way, and spent my time in the corners most people skipped, the small losses, the weights that drifted, the adjustments no one had time to chase. That work taught me something I still rely on: you don't fix a process from a desk. You stop, watch how it really runs, and ask the people doing it what actually happens.

Consulting

Consulting came next, and the view widened. Instead of one plant I worked across companies in retail, manufacturing, logistics, and other sectors. I sat close to boards, owners, and shareholders, and learned to think about a business the way they do. I led complex, cross-functional projects and built what sat underneath them: corporate strategy, roadmaps, financial analysis, plans to make a company actually profitable. I got fast at walking into an organization and seeing where it was breaking.

Software

Software came after that, and it came quickly. I moved into a faster environment and almost immediately took over an internal system that handled a high volume of customer requests and complaints, the kind of work that lives or dies on traceability: every request answered, on time, with a record of how. It was my first real contact with technology, and I brought the same operations instinct to it.

I became the product owner for that system and the ones around it, and stepped fully into how product actually gets built, working with a scrum master, a tech lead, and engineers. Together we took the tooling from tens of thousands of cases a month to well over a million handled in total, unified what had been separate tools, and rebuilt the flows around the things that hurt: wasted time, rework, and the failures that turned into penalties. It was also where I first put AI into real production, not demos, with models that classified incoming cases and helped draft responses, designed around how a person and the system would hand work back and forth.

Now

For years I shaped these systems from the operations side, defining what the work on the ground actually needed from them. Then a dedicated product team was formed to turn that internal tooling into a product any team could use, and I came on to lead it. That's the role I have now: not just defining what to build, but owning the product itself, from discovery through to production and across its whole life. It sits inside a broader suite, and the layer I'm building is what lets AI agents take on real parts of the work.


I like building things, and I like taking them apart to see how they work.

Away from the job, I've been doing it since I was a kid assembling PCs, and I do it in public now. This site is mine, code and all, built with Claude and Codex. So is PM-AI-Prompts, an open library of the prompts and workflows I actually use for product work, which I started early in 2026. I share it because what I figure out is more useful to other people than it is sitting on my drive.

My relationship with AI has changed fast. In a matter of months I went from writing good prompts to designing agentic systems, and I use them on real work. The industrial engineer in me doesn't switch off either: I notice the friction in things, the extra step, the process that could be smoother, and I usually can't leave it alone.

There's more in motion. One of the things I'm building is being made end to end with agentic AI, from the product work through to the code. Another is a product I'm about to take ownership of. I'll share both when they're ready.

The problems I care about live where operations, software, and AI meet. If that's what you're building, I'd like to hear about it.