An agentic ERP is an ERP with AI agents that read its data, flag what is missing and run routine work, with approval or validation before anything moves money.
What it does, in order, and what it never does.
Connections
What the system never does
KINTO builds this layer on the ERP a company already has, or builds a new one when the old system cannot be saved.
In the cases KINTO has worked on, the ERP held the whole operation but nobody could see inside it. A real estate firm ran leases, invoicing, treasury and maintenance in a property-management ERP with thousands of undocumented API services, and its old website was maintained apart from the ERP. A freight operator ran on a web application more than twenty years old, with hundreds of thousands of waybills in one database and a twice-monthly close done in a macro-driven spreadsheet.
The cost was hidden. High-value customers stopped shipping without anyone noticing, and every day someone retyped data that already existed on a third party’s platform.
Companies whose ERP is old, closed or poorly documented, with a manual close or staff retyping data between systems. Not every figure is in yet: accounting hours saved in the real estate case and data-entry hours saved in the logistics case have not been timed.
Headless e-commerce
By making the ERP, not the web catalog, the source of truth, KINTO got an auto parts distributor’s WhatsApp agent to offer ≈26% more real products and stop offering hundreds it did not have.
WhatsApp & voice agents
By analyzing a year of invoices, KINTO found that fewer than half of a food manufacturer’s customers drove almost all of its volume; we built a production WhatsApp agent, an AI calling pilot and a headless store that kept every URL.
Agentic ERP
KINTO replaced a two-decade-old system and a macro-driven spreadsheet with an agentic ERP that matched the old system to the cent on 100% of shared waybills over six months and surfaced customer-reactivation opportunities.
Agentic ERP
KINTO gave a real estate firm locked inside a sector ERP an agent layer that reads the ERP, shows lease by lease the status of each document, and writes only when a person approves.
Agentic ERP
KINTO co-developed with a US last-mile delivery operator a dispatch cockpit that reconciles platforms that don’t talk to each other and proposes assignments with a human in the loop, delivered as a working browser extension.
An agentic ERP is an AI layer on top of a company's ERP that reads its data, explains what is missing and proposes actions. It starts read-only because a wrong write to the books costs far more than a slow answer; writes to an existing ERP need a person's approval.
A WhatsApp AI agent should not memorize the catalog because memory goes stale and models fill gaps with plausible inventions. It should look up products, stock and prices in the system of record, and let code compute dates and totals.
Only under controls. KINTO starts ERP projects read-only. What moves money or changes the books or the ad accounts is approved by a person or validated against the previous system before it goes live; routine work that code can verify runs on its own. In the real estate case ERP writes go through an approval queue with a dry run and a duplicate check.
No. In a real estate case, KINTO built a read-only agent layer on the firm's existing property-management ERP, curating thousands of endpoints for agents. In a logistics case the old system was rescued without a rewrite while a new ERP was built beside it.
By comparing record by record, not by totals. In the logistics case KINTO validated waybill by waybill across six months of billing periods: the new system matched the old one to the cent on 100% of shared waybills, and the remaining differences were explained one by one before the switch.
The system handles routine work on its own and calls a person only when something falls outside what is expected. That was the guiding principle in the logistics case, where the ERP also surfaced high-value customers who had stopped shipping unnoticed.
It makes existing data visible. In the logistics case the ERP showed customer-reactivation opportunities: high-value customers who had stopped shipping. In the real estate case the ERP and the ledger were matched document by document. Both are measured, not projected.
Often, yes, but it depends on the ERP and its access. KINTO has put agent layers over ERPs in real estate and auto parts. It starts read-only, and on an existing ERP writes to the books go through a queue a person approves. In one case access restrictions stopped the project, so access is verified first.
An agentic ERP is an AI layer on top of a company's ERP that reads its data, shows what is missing and proposes actions. It starts read-only because a wrong write to the books is costly. What moves money or changes the books is approved by a person or validated against the previous system before it goes live.
Tell KINTO what is going on. The first conversation is to understand it, not to sell.
