How employees without technical knowledge can use AI in your ERP

The biggest fear with AI projects in SMEs is not “does the technology work?” That is a concern for the IT supplier. The fear in the boardroom is different: “we do not have the people internally who can build this.” Justifiably so, if you think in terms of developers, API specifications, and Python scripts. But that is not how it works anymore. The people who get the most value out of AI in your ERP are not the programmers. It is the people who run your processes on a daily basis.

What it looks like in practice

Take a project manager at an installation company. She has five contracts in front of her: all service subscriptions, all with slightly different terms and conditions.

The old way: read each contract, note the differences, email the legal department, wait. The new way: she selects the contracts in your ERP and types in the chat: “What deviations do you see compared to our standard contract and what risks do they contain?” Thirty seconds later, there is an overview of deviations, risk points, and a draft email for legal affairs. No training. No script. Just typing.

How this works

Three steps, nothing more: 1. Select documents, requests, or relations in your ERP 2. Choose an assistant agent 3. Give a command in the chat — in plain language. The agent knows which data you have selected, knows your ERP system, and can combine the relevant information and prepare actions. What used to be an IT project — “we need to build a report that compares contracts” — is now a question the project manager asks themselves.

More applications across the organization

This pattern repeats in every department.

• Finance: a controller uses it to check invoices from a batch against purchasing conditions — deviations are automatically flagged.

• Service: a planner summarizes a stack of complaints and categorizes them for correct routing.

• Sales: an account manager searches the quotation history of a specific customer to draft a targeted email.

• HR: an employee matches incoming CVs with a job profile and gets an initial screening.

In all these cases, it is not the IT department that directs the agent. The employee who knows the process does it themselves.

Why this is the fundamental change

For a long time, automation was a sequence of investments: first an ERP, then a CRM, then a BI tool, then an integration platform. Each step required an IT project, specialists, and lead time. AI agents change that dynamic. The people who know the process — not the people who know code — direct the agent. Domain knowledge wins, not code. Anyone who can type an email can operate an agent. That does not mean IT disappears. On the contrary: someone has to configure the agents, manage permissions, and secure integrations. But daily use shifts to the work floor. And that is where the profit lies, because that is where the repetition is.

What you can do tomorrow

No six-month pilot. No steering committee. Give three people from one team access for two weeks and simply ask them: where did it help you?

What works spreads naturally through the organization. What does not work will also surface soon enough.

That is the most pleasant way to introduce AI in a medium-sized environment: not as a large transformation program, but as a tool that people discover for themselves.