Agents that own a workflow, not a text box

What makes these agents rather than features

The word has been stretched to cover almost anything with a model behind it, so it is worth being specific about what we mean. Three properties, and a thing has to have all three.

• It initiates. The work starts without a person opening a screen. A bill arrives, a bank feed updates, a contract is signed, a period opens — the agent picks it up.
• It owns an outcome, not a step. The AP agent is not a document parser. It is responsible for a bill reaching a correct posted entry, which includes deciding when it cannot do that alone.
• It operates under explicit authority. It has a permission level, it is constrained by a policy engine it cannot address, and everything it does is recorded. Without this a thing that initiates work is not an agent, it is a liability.

They share one context

This is the part that is hard to see in a demo and matters most in production. Because every agent reads the same business graph, the AR agent knows a customer is mid-renewal before it sends a dunning notice, the Close agent knows the AP agent has forty bills still in the exception queue, and the CFO agent explains a margin movement using the project data the delivery team entered rather than a separate export.

In a stack of point solutions each of those is an integration project. Here it is the default, because there is nothing to integrate — and it is the single biggest reason a fleet of agents behaves sensibly rather than each one doing something locally reasonable and collectively wrong.

How customers actually roll these out

Almost nobody should turn on eight agents in a month. The pattern that works, and the one we recommend in the first call, runs roughly like this.

• Weeks 1–6: accounts payable at Level 1. Everything drafted, everything reviewed. This is where the labelled corpus comes from and where your team calibrates its trust.
• Weeks 6–10: AP to Level 2 for recurring vendors under a threshold. Typically once a vendor has thirty clean drafts. Dunning moves to Level 2 around the same time.
• Quarter 2: reconciliation and close. Reconciliation at Level 2 daily, close at Level 1 driving the checklist. This is where close duration starts moving.
• Quarter 3 onward: the analytical agents. CFO and Controller at Level 0 and 1, which need three or four closed periods of clean data behind them to be worth anything.

Procurement and revenue recognition tend to come later and are more industry-dependent — rev rec early for software companies, procurement early for distributors.