Skip to content
All insights

Workflow automation

Most of purchasing is chasing. That part can be automated.

Strategic sourcing is a skill. Emailing four suppliers, waiting, emailing them again, and copying their replies into a comparison sheet is not, and it is where most of a buyer's week goes.

Published May 19, 20266 min read

What this covers

  • The repetitive half of purchasing is issuing, chasing and normalizing, and it is almost entirely rule-governed.
  • Comparing offers is hard because suppliers answer in incompatible units, terms and lead times, not because the math is hard.
  • Supplier selection and negotiation stay with buyers, and the agent's job is to make those decisions arrive fully prepared.
  • Supplier master data, especially bank details, must be outside the agent's write surface.

Watch a buyer for a day and the split is obvious. A small part of the time is spent on decisions that need their experience: which supplier to develop, where to push on price, when a lead time is a real constraint and when it is an opening position. The rest is logistics. Sending the same request to four companies, waiting, sending it again, and turning six replies into something comparable.

That second category is not a small residue. In most operations it is the majority of the week, and it scales linearly with volume, which is why purchasing teams grow with the business even when the strategic workload does not.

The repetitive cycle, step by step

  1. 01Read the request

    A purchase request arrives from an internal form, an email, or as a requirement generated in the system. Work out what is actually being asked for, which often means resolving a description to a specific item and specification.

  2. 02Identify suppliers

    Determine who can supply it: approved suppliers for that category, who has supplied it before, and what the framework agreements say.

  3. 03Issue the requests

    Send the same request to each supplier in the form they expect, with the specification, quantity, delivery point and the date a response is needed by.

  4. 04Chase

    Follow up with the ones who have not answered, on a schedule, without being told to.

  5. 05Normalize and compare

    Turn incoming offers into a like-for-like comparison: same units, same currency, same incoterms, same treatment of tooling, freight and minimum order quantities.

  6. 06Route for approval

    Present the comparison to whoever approves this category at this value, with the recommendation and the reasoning visible.

  7. 07Raise the order

    Create the purchase order once approved, send it, and track the supplier's confirmation against it.

Step six is the buyer's decision and stays theirs. Everything else is mechanical, and step four is pure overhead that nobody wants and every organization pays for.

Why comparing offers is genuinely hard

The comparison step deserves more respect than it gets. Four suppliers answer the same request and produce four documents that are not comparable.

  • One quotes per piece, another per hundred, a third per kilogram.
  • One includes freight, one adds it as a separate line, one says "ex works" and leaves it to you.
  • One quotes a lead time from order date, another from receipt of a signed confirmation, a third from receipt of payment.
  • One has a minimum order quantity above what you asked for, so the effective unit price is not the quoted one.
  • One prices tooling separately and amortizes it, another builds it into the piece price.
  • Two quote in different currencies with different validity periods.

The buyer normalizes all of this in their head or in a spreadsheet, which is where errors enter and where the hours go. An agent does it explicitly: landed cost per unit on a stated basis, with the assumptions listed and every original figure still visible.

The value is not that the comparison is faster. It is that the assumptions behind it are written down where a second person can check them.

Chasing, which nobody should still be doing

Follow-up is the clearest case in the entire workflow. It is time-consuming, it is universally disliked, it requires no judgment, and doing it badly costs real money because a supplier who never replied is a supplier who never competed on that line.

An agent follows up on a schedule, escalates to a named contact when the first address does not respond, and reports which suppliers responded, which did not, and what that means for the comparison. A buyer who has spent years writing "just following up on the below" gets that time back entirely.

Where the agent stops

DecisionWhoWhy
Which approved suppliers to approachAgent, by ruleCategory, framework agreement and history are lookups
Which offer to acceptBuyerPrice, relationship, risk and capacity are judgment
Whether to negotiate, and on whatBuyerThe agent supplies the comparison, not the position
Approving a new supplierYour processOnboarding, checks and master data stay where they are
Raising the purchase order once approvedAgentMechanical, against an approved decision
Changing supplier bank detailsNever the agentThe highest-value fraud target in the business

The last row is not a nuance. Supplier master data, and payment details in particular, must sit outside the agent's write surface entirely. That is a structural limit rather than a threshold, and it should be verified rather than assumed. The security review checklist sets out how.

What this connects to

Purchasing rarely stands alone. The supplier confirmation the agent tracks is the document that later has to agree with the invoice, which is the three-way match in accounts payable. In a manufacturer, the requirement being sourced frequently originates in a customer RFQ that is still open, which means the purchasing answer determines whether the quote can be committed at all.

This is the argument for treating these workflows as one system rather than as separate tools. When the same agent foundation handles the sourcing and the invoice, the confirmation does not have to be re-read at the other end. What an AI operating system means covers that in full.

The Procurement Agent sets out what is ready-made and what is configured against your approved supplier list, approval matrix and purchase order fields.

Questions

Questions we get about this.

Does it choose the supplier?

No. It decides which approved suppliers to approach, because that follows from category, framework agreements and history. Which offer to accept is the buyer's decision, made against a normalized comparison with the assumptions listed.

How does it compare offers that arrive in different formats?

By normalizing them to a stated basis: the same unit, currency, incoterm and lead-time convention, with minimum order quantities and tooling costs accounted for. The assumptions behind the comparison are shown, and every original figure stays visible.

Can it approve purchase orders?

It routes them to whoever approves that category at that value, and raises the order once approved. Approval thresholds are yours to set, and nothing above them is committed however clear the comparison looks.

Can it add a new supplier?

No. Supplier onboarding, approval checks and master data stay in your existing process, and supplier bank details are outside the agent's write surface entirely rather than protected by a threshold.

What happens when a supplier does not respond?

It follows up on a schedule and escalates to a named contact where the first address stays silent, then reports who responded and who did not so the comparison states what it is actually based on.

See what this would look like in your operation.

A Workflow Review traces one of your real workflows end to end and names the first step an agent could take over. No platform to evaluate first.

Start with one workflow

Fixed scope for the first workflow, agreed before we start. Expansion is your decision once it proves value.

How it works

Security, stated plainly

Where the agents run, what they can and cannot do, and exactly what we do and do not claim.

Security