- Analyst guidance assumes enterprise structure: platform teams, multiple ERPs, a transformation office.
- Mid-market deployment differs structurally, not just in scale.
- One ERP and a small team are advantages if you sequence for them.
Almost every piece of agentic-AI research a mid-market manufacturer reads was written for a company ten times its size. The advice is not wrong, it is addressed to someone else: a firm with a platform team, several ERP instances and a dedicated transformation office. Applied at $100M to $2B, that advice produces a programme you cannot staff.
What is structurally different, not just smaller
Three differences change the shape of the work. You probably run one ERP rather than a federated estate, so integration is simpler and there is no reconciliation layer to build. You have no platform team, so anything requiring one is out of scope regardless of merit. And your executives are close to operations, so a decision that takes an enterprise two quarters can take you two weeks.
Enterprise guidance is written to manage the first two problems, which you do not have, and it ignores the third advantage, which you do.
Copying it means importing coordination overhead you have no need for.
Why one ERP and a small team is a strong hand
A single system of record means an agent has one place to read from and write to. No entity resolution across instances, no arguments about which system is authoritative. That removes the most expensive part of most enterprise agent programmes.
A small team means the person who owns the process, the person who approves the exception and the person who signs the budget are often in the same meeting. Constraint engineering — scope, authority, owner, revocation — is a conversation rather than a governance workstream.
Speed of decision is the mid-market's actual edge. Sequence to use it.
The $100M–$2B operator's deployment pattern is structurally different and under-served.
The sequence that fits
Start with one workflow that sits entirely inside your ERP and has a named owner who wants it fixed. Ship it with a real approval gate. Measure it. Then take the next workflow adjacent to the first, so the second reuses the identity, audit and approval pattern of the first.
Three or four cycles of that produces a governance layer as a by-product, without a platform team and without a transformation office. It is slower per workflow and much faster to the tenth.
What to do next
- 01Discount any guidance that assumes a platform team or a federated ERP estate. It is not addressed to you.
- 02Choose a first workflow that lives entirely inside your system of record.
- 03Reuse the identity, audit and approval pattern from workflow one on workflow two. That reuse is the whole strategy.