Questions buyers actually ask.
If your question isn't here, the fastest way to get an answer is a 30-minute call.
What is a fractional Chief of Staff, and how is it different from a consultant?
A fractional Chief of Staff works part-time inside your organization on the strategic and operational work that sits closest to the leader: surfacing priorities, driving the initiatives that keep getting deferred, and making sure decisions actually get executed.
A consultant typically delivers a recommendation and leaves. I stay in the work, on your meetings, alongside your team, until things are moving. Most of my engagements are six to twelve months at one to two days per week.
Who do you typically work with?
Healthcare and multisite organizations with three or more locations, where strategic direction already exists but execution is stalled. Owner-led groups, private-equity-backed platforms, and mission-driven organizations doing work that matters.
Common signals it's a fit: the same problems keep surfacing, key processes live in one or two people's heads, a vendor decision is overdue, or there's more ambition than bandwidth to act on it.
How are engagements structured and priced?
Most engagements are monthly retainers based on a defined number of hours per week, typically eight to sixteen. Project work (vendor selection, process documentation, an AI workshop series) is scoped as a fixed engagement with clear deliverables.
Pricing is shared on the first call once I understand what you're solving for.
How long does a typical engagement last?
Six to twelve months is the most common shape. Long enough to get embedded, work through the initial set of priorities, and build the structure that lets your team carry the work forward without me.
A handful of clients have continued beyond a year when the work keeps generating its own next step. Project engagements are shorter, usually four to ten weeks.
Can you help us select a new EHR, PMS, or operational software?
Yes. Vendor selection is one of the most common reasons clients come in. The work starts before any demos: defining what you actually need, what's table-stakes versus a real differentiator, and what failure modes you're trying to avoid based on what's broken today.
From there I run a structured evaluation, sit in the demos with you, and pressure-test what the vendors are claiming against what your team will actually use. The output is a decision you're confident in, not one you're second-guessing six months after signing.
Do you do AI training for healthcare teams?
Yes. Hands-on workshops built from live deployments in healthcare organizations, not generic AI curriculum. Teams leave with tools they've already practiced on their own data, workflows they've adapted to their roles, and habits that survive past the training day.
Most engagements run as a series rather than a one-off so the team gets to AI-adopted, not just AI-aware.
How is your process documentation different from a standard SOP project?
Most SOPs are written from memory by someone trying to recall what they do, which means they're partial, idealized, and out of date the day they're finished.
I build documentation from recordings of how your team actually does the work, then turn that into job aids, training materials, and process maps that match reality. Onboarding gets consistent, coaching has something to point to, and the knowledge stops walking out the door when someone leaves.
Where are you based, and do you work with clients outside Colorado?
Based in Denver, Colorado. Most of my work is remote, with travel to client sites for kickoffs, leadership offsites, and key working sessions. Current clients are spread across the country.
How do we get started?
A 30-minute call. You tell me what's not working, I ask questions, and we figure out together whether I'm the right fit. No pitch, no pressure.
If there's a fit, we define what an engagement would look like before any commitment.