Fit: fractional AI executive
What the role usually needs
A fractional AI executive sits inside a company's leadership, owns the AI-adoption roadmap, and is accountable for it actually running, not just for recommending it. That means process discipline as much as technical skill: writing down how things work so they don't live in one person's head, then automating the parts that can be.
What I have done that matches
- I've done this at Adroit already, as an operator inside the company, not as an outside advisor: joined as COO in 2021, became Chief Innovation Officer since 2024 as the role turned toward technical architecture and AI orchestration. See About.
- I built LEGION, the multi-agent operating system Adroit now runs on. It's live, and it operates Adroit's hosted products, deploys them, and checks their health.
- Content Ops is live in production and drafted Adroit's own website rewrite: 92 of 95 planned pages in two days of batch runs, with 74 pages updated and 17 created, now live.
- A revenue-operations rebuild for an anonymized client, a national amateur sports league: 7 systems consolidated into 1, about 2,400 teams, in six weeks, with zero rollbacks.
What I have not done
- All of the above happened at Adroit, where I already had authority and years of context built up. I haven't run this as a fractional engagement, dropped into a company I don't already know — but I'd take it on and figure out the implications for Adroit as they came up. More likely, Adroit would end up an invaluable part of whatever work I did there. I'm willing to be flexible depending on what the client needs.
- I work with owners and CEOs regularly, so depending on how narrowly you define "board-level governance," the old framing here was directionally false. Formal reporting to an outside board or investors specifically, I haven't done.
Evidence
| Claim | Receipt |
|---|---|
| COO (2021) to Chief Innovation Officer (since 2024) | /about/ |
| LEGION: live, runs Adroit's hosted systems, 64 capability packages | /builds/legion/, /receipts/ |
| Content Ops: live; website rewrite, 92 of 95 pages in two days | /builds/content-ops/, /receipts/ |
| League rebuild: 7 systems into 1, ~2,400 teams, 6 weeks, 0 rollbacks | /receipts/ |
How I work
Same discipline whether it's Adroit's systems or someone else's: write the process down, direct an agent to build it in plain English, gate the release behind tests, and label every number measured or estimated. The accurate frame: the agent writes the code, tests and documentation; I direct, decide, buy things and validate. See receipts for the numbers behind all of it.
Where this would not fit
I do change management extensively — my career is full of system migrations, rebrands and acquisitions I've led. Where I'm the wrong pick is a role that's stakeholder politics with no actual system to build; give me something to build alongside the people-work and that's exactly the shape I fit.
More on the work: /builds/. Every number: /receipts/.