I help founders and high-growth leaders build the operating system underneath the growth. Fifteen years of hands-on work, done with care. AI and automation make it faster. The operating clarity is what makes it stick.
Which tools, which order, who owns it after launch, and how it plugs into the operating system you already have.
We have AI tools (and a lot of them), but no one owns the strategy and program.
We know the work is messy, but we are not sure what to automate (and when).
The strategy makes sense in a deck, but not in the daily grind.
The team is growing faster than the operating system around it.
The work clusters into five areas. Most engagements touch three or more.
I find where AI fits in the work you already do, then build and ship the one or two agents that earn their keep. No new chaos, just clarity.
Actionable plans that align operations with the business goals, written so your team can run them without me moving forward.
Rebuilding the structure, mentoring the managers, and putting rituals in place so motivation shows up weekly.
Sharper budgeting and forecasting, real cuts to vendor and tool cost, and growth models the team uses to make decisions.
Plans for the failure modes that matter, so the team can keep moving fast without getting trapped.
Pick the model that matches where you are.
We'll confirm on our first call.
Roadmap + leadership readout
Accountable program ownership
Senior counsel on demand
Every engagement starts with deep listening to the leadership team, to the operators, and to what isn't being said in the all-hands. I'm an operator and executive coach at heart; the diagnosis is the deliverable that makes everything downstream flow.
Before we touch any tool, we map what the company actually does today: processesworkflows, handoffs, points where work stalls, and the points where it sparks. Most "AI strategy" engagements skip this step. They really shouldn't.
The right tool is the one your team will actually use when they need it. We pick the stack that fits your OS: your data, your security framework, and your team's daily flow. Then we build alongside the team, not over their heads. Tool-agnostic by default: Claude, OpenAI, n8n, custom. Whatever makes an impact for success.
AI programs easily looses tracking. Most peak right after deployment and then is slowly forgotten. We measure what each automation saves and improves, retire what doesn't, and re-prioritize ongoing. The operating cadence is the key to ongoing success.
I'm an operator. Fifteen years inside high-growth companies across creative agencies, consumer hardware, immersive media, and AI-native work, plus a handful of stealth-stage builds along the way. Different industries, same problem underneath: ambition outpacing the systems built to carry it.
What I do is the load-bearing work of scaling. The trust, transparency, and operating rhythm that turn ambition into something a team can actually deliver. AI, automation, and operations are the lenses I'm best known for, but the role takes the shape of the moment: Chief of Staff, fractional Head of Operations, embedded operator. Mapping the process. Understanding the landscape, then selecting and implementing the tools that fit the problem, not the other way around. Restructuring teams so people can do their best work. Cleaning up the budget. Building the cadence the team trusts on Tuesday. I work embedded and tool-agnostic by design, and most engagements end up touching product, finance, legal, and beyond.
I keep a small roster, by design. Each client gets my full attention and care, not a slice of a distracted calendar. I lead from listening. The difference between a consultant and an operator, in my view, is whether they stick around long enough to see if the thing they shipped actually got used.
Outside the work, I write about fatherhood, take pictures, and make ceramics. The coaching shows up everywhere.
If any of this resonates, book 20 minutes.
P.S. And yes, I do actually use em-dashes :)
I do not replace your team. I make them stronger.
Tool-agnostic by principle. I start with the problem, the path to solving it, and the stack you already have.
I do not disappear after launch. Guidance and hands-on work are part of the work.
I do not take work I cannot do well. If you need something outside my range, I will tell you and point you to someone can do it.
A 20-minute call to start. No deck, no pitch. A conversation about where you are, where you want to go, and what's keeping you stuck.