You run the business.Not an AI department.
Bring in a fractional Chief AI Officer.
Book a callI find where AI actually pays.
Most AI projects fail because nobody asked what the business needs. I start with how your operation really runs — the handoffs, the workarounds, the things everyone knows are broken — and work out where automation earns its keep and where it would just be expensive.
I build the thing.
Not a slide deck. Working agents and workflows, wired into the systems you already run. I have done this for a medical practice, a hotel, a real estate firm, and a law practice — and in each case the deliverable was software that runs on Monday, not a recommendation.
I hand you the keys.
Your team learns to run it. Documentation, training, and enough understanding that they can change things without calling me. The measure of a good engagement is that you stop needing one.
95%
of guest interactions handled without a human
Hotel, Washington coast
Thirty years building the software other people use.
Before advising on AI, I shipped product at companies you have heard of and built two of my own. The judgment you are hiring came from doing the work, not from watching the space.
- ScribblCo-founder & CTOCurrent
- OnderCo-founder & CTOAcquired by EasyKnock
- DevHubChief Revenue Officer
- AngiVP of Product
- OutreachVP of Product
- ExpediaHead of Global Flights Shopping Product
- CompassFounding member, AI team
17 podcast appearances and features in Business Insider, NewsNation, and Commit 250.
AI at work.
Four businesses, none of them technology companies. Names withheld, numbers real.
References available upon request.
How it works
- 01
Assess
I learn how the business actually runs and find where AI is worth applying.
- 02
Build
Working agents and workflows, shipped into the systems you already use.
- 03
Enable
Your team is trained to run and extend what has been built.
- 04
Stand watch
I stay on as your part-time Chief AI Officer for as long as that is useful.
Questions
The same thing a full-time one would, for a fraction of the week. I figure out where AI is worth applying in your business, build the things worth building, and make sure your team can run them after I step back. You get the function without carrying the headcount.
Most start with a short assessment of how the business actually runs — not a survey, a look at the real workflows. That produces a short list of things worth doing, in order. From there we either build, or I stay on at a set number of days a month as your Chief AI Officer.
It depends on scope and how much of the week you need. Assessments are a fixed fee. Build work is scoped per project. The ongoing role is a monthly retainer. We will land on a number on the first call, once I understand what you are trying to change.
Almost never. The work is usually about connecting what you already have and automating the parts your team does by hand. Ripping out working software is expensive and rarely the thing standing between you and the outcome.
Weeks, not quarters. The first engagement is scoped so that something real is running early — a workflow your team stops doing manually — rather than a strategy document that sits unread.
That is decided deliberately, not by default. In regulated settings it has meant running models locally so sensitive records never leave the building. Elsewhere it means being explicit about which vendors see what, and writing that down.
Everything, eventually. The measure of this working is that you stop needing me. Systems get handed over with the documentation and the training to run and extend them, not as a black box only I understand.
Start with a conversation.
Thirty minutes, no deck. Tell me how the business runs and I will tell you honestly whether I can help.
Book a call