What does a fractional Chief AI Officer do in the first 90 days?
In the first 90 days, a fractional Chief AI Officer should take you from a list of ideas to systems running in your business: find the few opportunities worth building, build them in accounts you own, train your team to run them, and hand over the keys with the results priced in dollars. If the first quarter ends with only a strategy document, you hired a consultant.
What should happen before the clock starts?
The diagnosis should happen before the engagement, so the 90 days go to building. A serious fractional Chief AI Officer learns what is costing you the most, maps your operation process by process, and puts it in writing: exactly what gets built, and the number.
At Meet Caddy, that is a free discovery call, then architecture calls that map your operation live, then a written proposal. You accept, and the engagement starts. Nothing about the scope should be a surprise on day one.
What happens in the 90 days?
Four phases. The build starts early on purpose, so systems are working long before the handover.
| Phase | When | What happens | What you should see |
|---|---|---|---|
| Discover | First days | Surface every opportunity, rank it by value, and pick the handful worth building first. At Caddy, we call them the magic five. | A ranked list, priced in dollars |
| Build | Weeks 1 to 7 | Digital labor built and deployed in accounts you own. | Systems doing real work, not demos |
| Adopt | Weeks 8 to 10 | Your team trained, with written procedures for every system. | Your people running it, not watching it |
| Optimize | Final weeks | Stress-test, tune, and hand over the keys. | An operating manual and full access |
The order matters. Discovery that drags past the first days eats the build. A build that starts before the opportunities are priced ends up automating the wrong things.
How should you stay in the loop?
You should never have to ask what is happening. Inside ACE, the rhythm is a written report every week, a standing call every other week, and a direct line whenever you want it. The weekly report is the one to insist on from anyone: it shows what shipped, in writing, and it is hard to fake.
What should you hold at the end?
Systems running in accounts you own, a team that knows how to run them, and three documents:
- The number. A value scorecard that prices the work in dollars a CFO would defend, built on our 21-metric framework.
- The log. The weekly reports: what shipped, week by week, in writing.
- The keys. An operating manual for how your team runs the system without us.
If any of the three is missing, ask why before you sign off.
What are the warning signs in the first 90 days?
- Nothing live by the midpoint. A build that has not shipped by week 6 or 7 will not ship by week 12.
- Systems in their accounts. If it runs on the vendor's infrastructure, you are renting it.
- No dollar figure. "Productivity" is not a measurement. Every system should carry a number.
- Your team is not involved. Systems your people never touched will not survive the handover.
- A new roadmap instead of shipped work. A plan for the next quarter is not a result from this one.
What happens after day 90?
Your team runs the systems. Optional ongoing support and senior advisory are there if you want a long-term partner, but they should be a choice, never a dependency. If AI turns out to be a permanent function at your scale, this is the moment to hire a full-time leader, with a far better brief than you had 90 days earlier. For the role itself, see what a fractional Chief AI Officer is.
This is how ACE runs, so weigh it accordingly. The scope goes in writing before anything gets built, and it carries a guarantee: if we cannot deliver what we scope together, you pay nothing.
The first 90 days, asked and answered.
How soon should the first system be live?
Well before the last week. Inside ACE, the build starts in week 1, and the first systems are typically live within weeks, not at the end of the engagement.
How much of our team's time does it take?
Some, by design. Your team is in the room from day one, so the systems land with the people who will run them. Expect the most involvement during training and adoption, which runs weeks 8 to 10 in ACE.
What does a fractional Chief AI Officer cost for 90 days?
It depends on scope. Meet Caddy prices each engagement to what discovery finds and puts the number in a written proposal before you commit. Compare any quote against the loaded cost of the work it will retire.
Do we need a full-time Chief AI Officer after the 90 days?
Only if AI becomes a permanent function big enough to fill the seat. Many companies keep optional support instead. Either way, you would be hiring against systems that already run and a team that already knows them.