A chart that means something
Fewer than about 250 accounts with real dimensions. An agent learning from a chart where the same cost sits in four places learns the inconsistency.
Framework
Most maturity models are a ladder with the vendor at the top. This one has five levels defined by who initiates the work, and level four — autonomous finance — is marked as something we do not build and think nobody should. The useful question is which level fits you, not how high you can climb.
Three questions about size, stack, and process. We will tell you which level you are at and what the next step costs.
A bill arrives; an agent codes it and routes it.
The work starts without a person. Requires an authority model, an audit trail, and a policy engine — which is why it cannot be retrofitted onto a screen-driven system.
Readiness
None of these are about buying software. They are the conditions under which handing work to an agent produces a good outcome rather than an expensive disappointment.
Fewer than about 250 accounts with real dimensions. An agent learning from a chart where the same cost sits in four places learns the inconsistency.
If the close does not currently finish, automating parts of it accelerates a process that does not work. Fix the sequence first; it is cheaper.
Twelve months of consistently coded transactions is the input. Without it the first quarter is spent building what should already exist.
Written down, current, and actually followed. An agent routing to your documented matrix is useless if everyone routes around it.
One person who can decide that a policy is acceptable. Automation stalls at exactly the same place implementations do — an unmade decision.
An API or a usable export. A ledger nobody can read is a constraint no amount of capability overcomes.
Every company we work with can technically operate at level three on day one — the software supports it immediately. What determines whether it goes well is the six conditions above, and five of them are about your own processes rather than about us.
The one that stalls most projects is the last kind: an owner with authority. Agentic automation requires somebody to decide that a policy is acceptable, and that decision has consequences. Where it gets escalated to a committee, the agents sit at level one indefinitely and the investment produces speed of preparation rather than autonomy.
Notice that most of the first year is at level three with low authority. That is not caution for its own sake — it is where the corpus is built, and skipping it means automating on a model that has not learned your conventions.
Autonomous finance — software that closes the period, releases the payment, and signs the assertion — is technically approachable and we think it is the wrong destination.
Closing a period asserts that the numbers are right, to an auditor, a board, or a lender. That assertion has value because a person is accountable for it. Automating it does not remove the work so much as remove the meaning, and the first time it matters is the first time somebody asks who is answerable.
So this model tops out at level three by design. A vendor promising level four is either not thinking about accountability or is describing a product for a market that does not exist.
We sell software that operates at level three, so a model placing level three as the sensible destination is convenient for us. The check worth applying is whether the argument against level four holds independently — we think it does, and it costs us the more ambitious claim.
Questions
Three questions about size, stack, and process, and a straight answer about what the next level would take.