Where does a non-technical procurement manager start with AI agents?

November 13, 2026 4 answers
Asked by v62~parcel_4

I manage a procurement team and keep hearing about AI agents, workflows and integrations. We spend a lot of time pulling data, following up with suppliers and formatting reports.

Can someone explain what these tools actually do, and whether a non-technical person can set one up without an IT team?

Answers

puddle__ledger-8

Think of a workflow as a sequence of steps, like pulling a report, checking it and preparing a supplier follow-up. An integration is the connection that lets one tool exchange information with another, such as your ERP system.

An AI agent adds something more flexible to that sequence. It might read an email, decide what information is relevant and draft a response. Some tools can also take actions, but that depends on what they are connected to and what permissions they have.

There are tools designed for non-technical users, so you don't necessarily need to write code to try one. Connecting company systems, setting permissions and checking data security may still need help from IT. And a polished answer isn't necessarily a correct one, so keep a person in the loop for decisions and outgoing messages.

v62~parcel_4:

So an agent could draft a supplier follow-up without being allowed to send it?

u1+datapath_59:

Yes, if the tool and workflow support that setup. Check the permissions and approval steps before connecting it to your email.

Reply to this answer
mosaic.afterglow

Don't start with an agent just because the demo called it one. If your report always pulls the same fields and puts them in the same format, ordinary workflow automation may be enough. It follows fixed steps rather than asking AI to interpret the task.

AI is more appealing when the input varies, like supplier emails written in different ways. Even then, a draft for review is a safer starting point than automatically changing records or sending messages.

spare-room-for-asterisks:

Some fixed-step automation still needs technical setup. A visual tool may make the workflow easier to build, but it won't necessarily solve every connection to your ERP.

Reply to this answer
r8.tinwhistle

Before picking a product, write down one task from start to finish. Where does the data come from? What does someone check or change? What should the finished result look like, and what happens when information is missing?

Take that to a vendor and ask them to show that exact task, not a generic demo. Ask what you can configure yourself, what needs an engineer, whether someone can approve the result, and how the tool handles company and supplier data. A small report formatting task would make a reasonable trial.

Reply to this answer
pebbleless-picnic

A low-code tool might be worth looking at if you want to build something yourself. Low-code generally means configuring steps through an interface instead of writing everything as a program. Copilot Studio is one example, though whether it fits depends on your systems and the task.

Keep the first test small. Compare its output with the report you already produce and check any mistakes before relying on it. Getting a tool running is one thing, keeping a workflow reliable is another.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions