The questions I get before we start

It means I don’t just hand you a strategy and leave. I deploy into the work alongside your team and stay until the change is real. The same person who frames the plan can own its delivery and put hands on the build. You’re not coordinating between a strategist, a project manager, and a builder, that’s one seat.

Strategist is the thinking and the map: roadmaps, org design, the business case. Orchestrator is ownership of the outcome: running the plan, pulling in the right people, holding the timeline. Builder is hands on the tools: configuring working artifacts in modern AI and no-code stacks.

It matters because most engagements break at the seams between those three roles. When one operator carries all three, the strategy doesn’t get lost in translation on the way to delivery.

No. You decide how far down the stack I go and pay only for the lens you need. Some clients want the defensible plan and will run it themselves. Some want me to own delivery. Some want a working tool built fast. The full arc, all three, is the Forward Deployed Executive engagement.

A focused 15-minute call to pressure-test the problem. If there’s a fit, I scope a short, defined first piece of work, usually a current-state map or a tightly bounded build, so you see real output before committing to anything large. From there we expand into whatever the situation actually needs.

Same operator, different seat. CSO sets the multi-year target and roadmap. COO turns the plan into stages, SLAs, and a cadence the team can run. CTrO leads the move from a flat org to a system, with governance and adoption. CAIO takes AI from idea to measurable pilot. The right title depends on which gap is costing you the most right now.

Both. The career was built inside demanding institutions in finance, private equity, and hospitality, which is where the rigor comes from. But I’m just as motivated to help an SMB owner or a founder hit and exceed their objectives. The methods scale down cleanly; the difference is pace and how much I personally build versus orchestrate.

Transformation and change programs, operating model and org redesign, workflow and process improvement, governance and risk structure, vendor and program delivery, and getting people to actually adopt a new way of working. If the work involves turning complexity into a system that sticks, that’s home.

I’m not a production software engineer, and I won’t pretend to be. I build working prototypes and configured solutions in AI and no-code stacks, fast. When something needs to harden into production-grade engineering, I’ll tell you plainly and help you bring in the right specialist. Honesty about where the line is protects your outcome.

Make It Make Sense (MIMS) is my method for transformation and execution: Map the current state, Interpret what matters, Mobilize into action and ownership, Sustain with habits and governance.

Make AI Make Sense (MAIMS) applies the same discipline to AI: Map where AI creates real value, Assess and prioritize, Implement with change management, Measure adoption and impact, Scale what works. The guiding rule is adoption over deployment, a tool that’s live but unused has delivered nothing.

No. The first question is always whether AI is even needed, or whether a simpler workflow, template, rule, or automation solves it better and cheaper. When AI does fit, I’m specific about what data it needs, what it can touch, what stays human-reviewed, and how we’ll measure whether it actually worked. Advanced isn’t the goal; the right-sized solution is.

Modern AI and no-code stacks where the path is well-trodden, the kinds of tools that get a working artifact in front of you quickly rather than a slide describing one. The point is speed to something usable, then hardening what proves valuable.

Scoped to the engagement and the lens you need, not a one-size-fits-all retainer. A defined first piece of work has a fixed scope and price so there are no surprises; ongoing fractional roles are structured around the time and ownership the seat requires. Tell me what you’re solving and the stakes, and I’ll give you a clear, specific proposal.

Both, depending on what the work needs. A lot of transformation and build work runs cleanly remote. Some change work benefits from time on the floor with the team. We’ll set the right mix when we scope.

It depends on current commitments, but a scoped first piece of work can usually begin within a short window of a clear go. The fastest path is a call: we’ll know in 15 minutes whether there’s a fit and what the first step looks like.

You keep a system you can run, not a dependency on me. Part of the work is documentation, playbooks, and the handoff, so the change is owned by your team after I step out. That’s the whole point of sustain: it has to hold without me in the room.

Ask me directly →