Most companies are sold an architecture two levels above where they are. Here are the five levels, what each one actually requires, and how to tell which one fits you today.
| Level | What it is | What it requires |
|---|---|---|
| Level 0: No AI | The right answer is process redesign, an integration, or straightforward automation. | Nothing beyond the process or integration work itself. This is where a large share of stated AI requirements land. |
| Level 1: Hosted Chat | Individual productivity through a chat interface. Lowest friction, real value, no engineering. | A usage policy and some training. That is it. |
| Level 2: Hosted Harness | Persistent context, file access, multi-step and scheduled workflows. Cowork, skills, and equivalents. | Governance decisions and someone to write reusable instructions. No developers. |
| Level 3: Custom Agents | Agents connected to live systems through integrations, with persistent memory and defined roles. | A technical owner inside your company. This is the level where most real ERP and finance value sits, and the level most often attempted without the owner in place. |
| Level 4: Multi-Agent Orchestration | Specialized agents in named roles with handoffs and automated evaluation. | Real engineering investment and senior technical leadership. Very few mid-market companies should be here, and almost none should start here. |
The honest test is not what you want to build. It is what you can support. If nobody in your company owns the integration when it breaks at month-end, you are not ready for Level 3 regardless of budget. If your process is undocumented, you are at Level 0 no matter what the demo showed.
Most mid-market finance and operations teams get the majority of their available value at Levels 2 and 3. Level 4 is where the case studies come from and where the failures come from, in roughly equal measure.
One agent doing one scoped job, with a named human owner and a defined success criterion, beats a single system asked to do everything. When you do move to multiple agents, give each one a narrow role with explicit handoffs rather than building one that does it all. The failure mode of the do-everything agent is that when it is wrong, nobody can tell you which part was wrong.
Almost everyone should start at Level 1 or 2 regardless of ambition, because those levels teach your team what the technology is actually good at, and the workflows you prove there become the specification for anything you build at Level 3.
Not at Levels 1 and 2. Yes at Level 3 and above, and specifically you need someone who owns it internally, not just a vendor who built it.
Rarely, for a mid-market company, and never as a starting point. Multi-agent orchestration solves coordination problems you do not have until you have a lot of working single agents.
It is the architecture selection step inside Walk Before Fly. Workflows get classified first, then sequenced, then matched to the lowest architecture level that will actually do the job.
30 minutes. No commitment. We will tell you honestly whether we can help.
Book an ERP Strategy CallLast reviewed: August 2026
Book a 30-minute strategy call. No pitch deck. Just a conversation about what is not working and what we can do about it.
Book an ERP Strategy CallTFR Solutions, Los Angeles, CA · teddie@tfr.solutions · (310) 894-6031