The AI Operating Sprint is a live working session, not a seminar.See the Sprint →
Fractional COO · AI operating practice

I'm a fractional COO. I run operations for a handful of companies at once.

My own work runs on an agentic fleet I built. That's how I run more than one operation without the work waiting on me. I've run companies across pharma, devices, and software for twenty years; over the last two years I built the fleet and the practice around it.

The leverage goes to the people who know the operation. When nobody in the room can evaluate what AI built, the work breaks there.

The standing agent fleet The overlapping fields of standing agents, durable context, and running services. Standing agents, durable context, and running services overlap. The center is a fleet Braydon can see, steer, and keep running. STANDING AGENTS DURABLE CONTEXT RUNNING SERVICES They stay there separate workspaces They know the work memory · repos · tasks They keep moving backends · triggers A fleet I can steer visible · context-aware · task-bound The circles overlap because the work does. The fleet is the system. The chat window is one surface.
  1. Standing agents 20–50 workspaces
  2. Durable context memory · repos · task lists
  3. Running services backends · timers · triggers
The standing fleet. An agent is a workspace with memory, repositories, tasks, and services around it. I keep the fleet running and step in where judgment is needed.

The fleet stays running. I step in where the work needs judgment.

Companies I've worked with
  • Sanofi
  • Novartis
  • Biogen
  • Daiichi-Sankyo
  • Vertex
  • Bayer
  • Genentech
  • Kion
  • University of Delaware
  • George Washington University
  • Sanofi
  • Novartis
  • Biogen
  • Daiichi-Sankyo
  • Vertex
  • Bayer
  • Genentech
  • Kion
  • University of Delaware
  • George Washington University
Why now

AI is in a honeymoon phase. One camp thinks anyone can build an enterprise application in an hour. Another thinks it will replace the experts.


Set Earth Inc · Contracts and invoices under this entity · Reply to b@mcco.us