Questions I get before anyone says yes.

Systems that take routine work off your desk, each one a role with one job: a reply desk that drafts answers to inquiries, a call-back that texts a missed caller and logs the callback, a collections clerk that sends invoice reminders on a schedule, a weekly report that builds itself, an onboarding coordinator, and a morning list that tells you what is waiting.

Each one runs in the tools your team already uses. The services page lets you hand one a job and watch what it does.

No. Each system drafts and prepares, and a named person on your team reads, decides and sends. The only messages that go out without a person pressing Send are ones you approved in advance, like the text a missed caller gets, which comes from a template you signed off.

Usually not. I build in the tools your team already uses for email, chat, scheduling and the books, and I connect them where they need to talk to each other. If a tool costs more than it gives, I say so and show you the replacement before anything changes.

Yes. My own practice runs on one. At 6:15 each morning an AI system I built in Claude Code reads my calendars, inboxes and project files and hands me one ordered list. It drafts the replies I owe, and I decide what goes out.

I do not publish a price list, because the right number depends on what the operation is losing. The Operations Leak Audit sets it: the audit names each leak and what it costs in hours or dollars, and any proposal that follows is one flat figure tied to closing those leaks.

You see the number in writing, after the audit. I do not quote on the call.

A fractional COO engagement is a flat monthly retainer, priced on the outcome and the scope, not on hours. A fixed-scope system build is priced per build, with the deliverables named before the work starts.

A retainer starts with a 90-day commitment. The first 30 days are the map and the first system; the next 60 build the systems into how the team works. After that it runs month to month.

For a fixed-scope build, the timeline depends on the deliverable and is written into the proposal.

With a 45-minute Operations Leak Audit: a working session on where the business is leaking time, money or attention. You leave with a one-page leak map and the first system I would build, whether or not we work together.

If there is a fit, usually within one to two weeks of a signed proposal. There is no long onboarding on my side. I start learning the business on day one.

Enough to own the outcome. The proposal names the scope, the weekly rhythm and the deliverables, so you know what you are getting. I do not sell blocks of hours.

Through the tools your team already uses for chat, email and project management. You do not adopt anything new to work with me.

Most engagements include a weekly review with you, daily contact with the people running operations, and a reachable window every working day on US business hours.

The map and the first system. I map every workflow, tool and handoff, talk to your team, and find where things break in practice, which is rarely where the founder expects. By day 30 you have a written map of the operation, a ranked build plan and the first system live. The process page lets you scrub through all 90 days.

Any industry where a team is in place and too much still waits on the founder. My deepest experience is in home services, private lending, media production and multi-location hospitality, and the same jobs turn up in agencies, professional firms and online stores under different names. See the notes on private lenders and home services companies.

A consultant diagnoses and recommends. You get a report and a roadmap, and making it work is your job.

I build the systems, own the operational layer beside your team, and stay until they hold on their own. There is a longer answer on what a fractional COO does and when to hire one.

Usually not before there is real revenue and a team. A business before revenue usually needs product-market fit, not operating systems, and building systems before there is something worth systematizing is a distraction.

I work remotely on US business hours, with clients worldwide. You get a reachable window every working day and a weekly review. All fees are quoted in US dollars.

Every system I build is written down. Every process is owned by a person on your team, not by me. Every handover is trained before I step back.

A good engagement ends with your team running the operation without me in every conversation. If that is not true, the work is not finished.