I help businesses run better through smarter systems, stronger execution, and tools that actually work.
I've spent the last decade building and running businesses where execution is the product. Not the strategy deck, not the vision. The actual daily work of making something operate well.
The problems I'm drawn to involve real complexity: multiple locations, multiple systems, people and process that have to work together under pressure. The kind of operation where one weak link costs you trust, revenue, or both.
That's where I do my best work: bringing structure to what's messy, building systems that hold, and raising the standard of how the whole thing runs.
Across different industries, different contexts, and different problems, the through-line is the same: bring structure to messy operations, raise the standard, and build things that last.
Co-Founder · Active
Fieldwork is what I'm building now.
Most small and mid-sized businesses are leaving significant operational capacity on the table, not because they lack ambition, but because nobody on their team has had time to figure out what AI can actually do for their specific operation. That gap is real, and it's growing.
Fieldwork is an AI-forward operations practice. We embed as a business's AI function: auditing workflows, building automations and tools, and making sure the business is capturing the leverage that's available to it right now.
Early days. Taking meetings. If your business has real operational complexity and you're not sure where AI fits, or you've tried it and it hasn't stuck, that's exactly what we're built for.
Owner & Operator
Brought in to run a struggling operation. Saw what it could become, bought it, and rebuilt it.
It's a multi-site, people-heavy business that runs seasonally, which means every system, every hire, and every customer interaction has to work inside a compressed window. There's no room to fix things mid-season.
The goal was never just to grow it. It was to build something that ran well without constant intervention, and that would last. This business exists to provide a safe, positive, genuinely educational environment for kids in the community. Nothing our competitors offer comes close to that standard. That mattered as much as the operational work.
Founder & Operator
Acquired the property, led the renovation, and built the operating system behind it.
Arena House is a private event venue. We haven't invested in marketing. We haven't needed to. The product does the work: over 250 inbound inquiries in 2026 alone, all organic.
Owner & Operator
Eighteen units across multiple properties. The systems problem here is the same as everywhere else: communication, maintenance, payments, turnover, vendor coordination. Without clear process it becomes reactive and expensive. Built the systems to make it run lean.
Not the most interesting operational story, but a consistent one. It compounds quietly in the background while everything else moves.
Advisor & Systems Builder
Came in as an advisor and got to work on the infrastructure.
Website, registration, and membership processes were creating friction and leaking revenue. Fixed the systems, improved the member experience, and cleaned up revenue capture.
These are not values on a wall. They are the things I actually optimize for when I'm running something or fixing something someone else built.
The goal is never to be the person everything runs through. The goal is to build something that holds: clear enough to hand off, strong enough to last, and simple enough that the team can actually use it.
Short-term pressure to cut corners is constant. I don't. The quality of what a customer experiences, the clarity of how a business presents itself, the safety and integrity of what you deliver. None of those are negotiable. The businesses I respect most treat standards as a competitive advantage, not a cost.
Not every important decision comes with a playbook. I'm comfortable making hard calls, taking smart risks, and acting with conviction, especially when the right answer is inconvenient.
AI is a serious tool and I use it seriously. Where it can improve what a customer receives, accelerate what a team delivers, or give a business leverage it couldn't otherwise afford, I'm all in. Where it's being used to cut corners on the customer experience so the operator has an easier day, I'm not interested. The test is always what comes out the other end, not how efficiently it was produced.
To the people on my team, to the clients I work with, and to the communities my businesses operate in. This isn't a values statement. It's just how I think you have to run things if you want them to last.
If the work feels aligned, reach out. I read every message.