← All insights

Collection

AI agents for ERP and manufacturing operations

We build conversational AI and AI agents that sit on top of live ERP, Dynamics 365 Business Central — not chatbots that paraphrase documents. The case studies below show real systems where natural language replaces navigation: customer service teams answering order queries through chat, operations leaders pulling commission data on the road, dispatchers triggering workflows without opening an app.

Decision intelligence is the larger pattern. When the cost of asking a question drops to one message, more questions get asked, more decisions get made on data, and execution speeds up.

This collection covers conversational AI deployments and the workflow automation that surrounds them — the systems that move information and the systems that act on it.

Product · Active beta
OpsGrid — decision infrastructure for Dynamics 365 Business Central
The articles below are the editorial behind a real product. OpsGrid takes the conversational-AI + Skills paradigm and ships it as a Microsoft Teams experience for BC operators — ranked decisions, human-approved execution, in 2 weeks.
See OpsGrid →

What we mean by AI agents

The phrase "AI agent" has been stretched to cover everything from chatbots to autonomous systems. In our work, an AI agent is a system that can receive a goal, access live operational data, decide how to fulfil it, and execute — with human checkpoints where the decision has real consequences.

For manufacturing and managed services, that looks like: a customer service agent that queries open orders in Dynamics 365 Business Central and responds via WhatsApp. An invoice reconciliation agent that matches supplier invoices against POs and flags mismatches for human review. A lifecycle automation agent that provisions accounts the moment an employee record is created and revokes access within minutes of offboarding.

What distinguishes these from standard workflow automation is the conditional reasoning layer. The agent decides what to do based on live state, not just a fixed trigger. When an order is delayed, it drafts an apology and surfaces the ETA. When an invoice matches, it closes the ticket. When a new hire is in manufacturing, it provisions different systems than if they're in sales. The cases below show what that looks like in production.