AI assistants can now build workflows, but something still has to run them. That is an architectural choice: a model that keeps checking for work (model-led orchestration), or software that acts only when there is work to be done (deterministic AI orchestration).
Imagine you’re at home waiting for a courier to deliver an envelope containing instructions for your next job. You could get up periodically, turn on the lights, and check if the courier is there. Or, you could install a doorbell and stay on the couch until it rings. Either way, you read the instructions and get to work when the courier arrives.
In deterministic AI orchestration, you’re using “doorbells”. The workflow starts when something happens: a customer submits a form, a record changes, or a scheduled time arrives. Software handles the sequence of steps, calling AI when reasoning is needed.
In virtually all the configurations we tested under model-led orchestration, you’re “getting off the couch periodically to check”. A model activates on a schedule, reads its instructions and context, and decides what to do and which tools to call. If there’s nothing there, it has still spent tokens finding that out.
On our central estimate, model-led orchestration cost 2.1× as much overall. For workflows that complete fewer than 30 runs a month, it cost 8.3× as much.
Here is why. Most business workflows spend their days waiting and step in only when something needs attention. In this study, 61% of workflows completed fewer than 30 runs a month and accounted for about half the projected model-led bill. Most of that group’s cost came from what we call sentinels: workflows whose checks usually find nothing to do, such as watching for a policy renewal.
The first AI Workflow Index examined where AI belongs inside a workflow. This edition measured the running costs of the two orchestration architectures. We rebuilt a smaller set of workflows as working automations on OpenAI and Anthropic’s business products and measured what they cost to run. We combined those measurements with observed workflow activity and estimated checking schedules to price all 2,944 workflows at published usage-based rates.
AI can increasingly build either kind of workflow.
It can also handle the reasoning when something needs attention. For most workflows in this study, letting conventional software run the workflow cost less.
That points to a practical division of labor for enterprise leaders: use AI to build the workflow and handle reasoning. Let conventional software run it.
These findings reflect today’s pricing and product capabilities. We expect the two architectures to converge. Model-led systems will increasingly gain ways to respond to events by building “doorbells”, while deterministic AI orchestration platforms already let users build and deploy workflows using AI.
As these capabilities mature and token prices change, the economics will shift. Reliability, governance, and the cost of building and maintaining workflows already matter; this edition does not measure them. Section 3 sets out how to evaluate your approach; the appendix shows how to price your own workflows.