Chief Operating Officer | Chief of Staff
The operator behind the founder. I turn a founder's vision into an operating system — the audit that tells you what's actually true, the SOPs and systems that hold under pressure, the org design and hiring that fit the stage you're in, and the reporting that makes performance visible before it becomes a problem. Ten-plus years inside founder-led, fast-moving businesses, most of it as the right hand who owns the outcome, not just the plan.
How I Operate
In a founder-led company the two titles blur, and I've worked both sides of the line. As Chief of Staff, the job is to make the founder more effective. As COO, I carry the ownership and the execution authority. In practice I bring both — the instinct to read what a founder needs before they ask, and the mandate to go build it.
You can't fix an operation you haven't looked at honestly. Every engagement starts with a full audit, not a reorganization.
Whatever process is missing, I create. Whatever process isn't working, I rebuild. Same for the systems underneath them.
A COO doesn't advise on the plan. A COO is accountable for whether it happens.
The half of the job that never makes it into a job description — and the part that makes the rest of it work.
The functional territory I take responsibility for. Some of it is standard for the role. Some of it isn't — like building the dashboards, internal apps, and AI-driven automations myself instead of waiting on a development queue.
Eight bestselling titles across business and fiction. It's worth mentioning because it explains something about how I operate: clear writing is what makes executive communications land, SOPs actually get followed, and a founder's vision survive contact with everyone who has to execute it. The operating documents I build get used, not filed.
Two questions every founder asks before bringing on an operator: what happens when she starts, and what has she actually delivered.