AI Agent for Procurement: What to Automate First in 2026

A purchase request at a 40-person company looks like this. Somebody asks for a tool in Slack. The office manager asks the founder. The founder says yes in a thread that has scrolled away by Thursday. Six weeks later an invoice turns up for a product nobody remembers approving, billed to a card belonging to a person who left in June.

Nothing in that story is broken enough to fix on a Monday. It is just expensive, quietly, every month.

So I went looking for software. On 22 September 2026 I looked for a published price on every procurement platform I could name. Two of them published a number I could read. Tropic starts at $3,083 a month. beam.ai starts at $50 a month for 200 tasks. Everyone else sent me to a demo form.

That $3,083 is Tropic's published floor, priced on employee count, which works out at roughly $37,000 a year before anyone has negotiated anything. It is the higher of the only two numbers I found, and the only one from a platform that sells procurement and nothing else.

If you have a procurement team and a budget line, a price like that is survivable, because there is somebody whose job it is to justify it. If you are 40 people with a purchasing problem and nobody whose job it is, the category's pricing starts where your budget ends. So this post is about the workflow. The suites can wait until you have somebody to justify them.

What I actually checked

One thing, on one day. I went looking for a price on every procurement platform I could name on 22 September 2026, and wrote a number down only when the vendor published one I could read without talking to sales.

• Two published prices. Tropic: starting at $3,083 per month, pricing based on employees. beam.ai: $50 a month for 200 tasks, one base integration and what the page calls lower-complexity work, rising to $3,990 a month at the top tier.
• Two 404s. Levelpath's pricing page and Zip's pricing page both returned HTTP 404 that day.
• One homepage with no number on it. Procure.ai renders no price and offers a demo request.
• Three suites sold through a sales process. Coupa, Ivalua and SAP Ariba sell enterprise source-to-pay with no self-serve price published. I did not read their pricing pages, so nothing in this post claims anything about their plans.
• The general platforms, asked the same question, because they are where a company this size usually already has a login: Ramp, Zapier, Gumloop and Lindy all publish readable plans.

What I did not do: run a procurement pilot, negotiate with any of these vendors, or test the products. There is no performance claim anywhere in this post, because I have not earned one.

One caution about that $3,083, because it is the kind of number that gets repeated badly. It is Tropic's published floor and nothing else. It is not the price of procurement software as a category, and it tells you nothing about what Zip or Coupa would quote. One vendor was unusually straight on a page where most of its competitors say nothing at all.

Quick comparison

Prices are what each vendor's own page showed on 22 September 2026. "No public price" means I looked and found nothing to read: Levelpath's and Zip's pricing pages both returned HTTP 404 that day, and Procure.ai's homepage offers a demo request instead. "Free tier" reflects what each vendor's page showed on 22 September 2026. Where no pricing page was readable, nothing is claimed either way. Ramp advertises 20% off with annual billing, and it covers spend and accounts payable, stopping short of source-to-pay. Zapier's Team plan starts at $69 a month, and its Agents Pro plan works out at $33.33 a month.

Five jobs an agent can take over in purchasing

These are in the order they happen. None of them needs a procurement platform. All of them need somebody to be consistent every week, which is the one thing a small company cannot spare a person for. If the word agent is still fuzzy, what an AI agent actually is sets out how it differs from a workflow you build.

1. Give purchase requests one front door

The request already exists. It is scattered across Slack DMs, a hallway conversation and one email titled "quick question". An agent cannot organise a process with no entrance, so build one: a short form, or a single channel it watches all day.

Then it does the boring part. It reads the message and pulls out what it needs. A row lands in the table, and the person asking gets back a request number they can point at next week.

What the row should capture:

• Who is asking, and which team's budget the cost lands on
• What the thing is, in the supplier's own words, so it matches what you will be invoiced for
• The amount, and whether it is one-off or monthly
• The date they need it by
• Whether anybody here already pays for something that does this

That last field pays for the whole exercise. Software bought on somebody's personal card in another team stays invisible until a human asks the question out loud, and a request form is the cheapest place to ask it.

2. Approvals move when somebody keeps asking

Approvals rarely fail on policy. They fail on silence. The request sits behind everything else in an approver's inbox, the requester feels rude following up, and a fortnight disappears into nothing.

This is exactly the shape of work an agent is good at. It routes by amount, reminds on a schedule, escalates when the clock runs out, and writes down who approved what and when.

A routing shape that works at this size:

• Under a small threshold you set: the requester's manager, one approval, done
• Over it: the manager plus whoever owns that budget line
• Anything recurring: a second pair of eyes, because a monthly charge is a decision you make once and then pay for forever
• A supplier you have never bought from, at any amount: somebody confirms the company exists and the tax details match

Let the approver answer where they already are. A reply in Slack with the word yes in it is a decision. Making an approver log into a new tool to press a green button is how approvals quietly stop happening.

Keep the written record even when it feels like overhead. The first time diligence asks who approved a payment from eighteen months ago, the log is worth more than the minutes it took to write.

3. The purchase order should write itself

A purchase order is a form assembled from a request you have already approved. Every field on it was collected at intake. There is no judgement left to exercise, which makes it the easiest step on this page to hand over.

The agent assembles a PO number from a sequence you own, then the line items, quantities and agreed price, then the currency, tax treatment and payment terms. It fills in the delivery or billing address and the internal cost code, and links back to the approval the order came from so the trail stays intact.

Then a person sends it. Or the agent sends it, once the supplier is on your approved list and the amount sits under your threshold. Draft-then-send is the sensible default for the first few months.

The purchase order earns its keep later. When the invoice arrives, matching it against what was ordered is what stops you paying twice, and that matching is itself an agent-sized job: see reconciling invoices in Xero against what you ordered.

4. Chasing the supplier is the job nobody volunteers for

Here is where the hours actually disappear. Deciding is quick. The paperwork is slower. The small follow-ups between placing an order and holding the thing are what eat the calendar.

What gets chased, in practice:

• An order confirmation that never came back
• A delivery date that moved and nobody thought to mention
• Tax details, bank details, a signed W-9 or a GST certificate
• The invoice for something that arrived three weeks ago and still has not been billed
• A credit note for the part that turned up broken

An agent will send the third follow-up. You were not going to. It keeps one thread per order and watches that thread for a human reply. The moment somebody answers, the row updates and the nagging stops, which is the part people get wrong when they build this with a scheduler and a template.

The same muscle runs in the opposite direction when the money is owed to you. An agent for chasing overdue invoices is the accounts-receivable version of this step, and most of the design decisions carry over.

5. Renewal dates need an owner, and it can be software

Cheapest thing on this list to automate, and the most expensive to miss. An auto-renewal is a decision you made a year ago, enforced by a calendar nobody has read since. The fix is a table and a reminder, and an agent can maintain both.

Next to the vendor name and one line on what it does for you, the columns that matter:

• Who inside the company owns it
• Renewal date
• Notice period, the field everybody forgets
• Annual cost, seats paid for, seats actually used

The notice period is the whole reason this is worth doing. A contract that renews on 1 March with 60 days' notice has a real deadline of 31 December. A reminder on 1 February is not a reminder, it is an invoice for another year.

An agent can also hunt the subscriptions that never made it onto the table, by reading receipt emails and card statements for charges that match nothing you have recorded. That first pass is the one most likely to turn up a subscription nobody remembered.

What not to hand to an agent in purchasing

The test I use is simple. If a mistake costs money you cannot claw back, or creates an obligation a lawyer would recognise, a person presses the button. Everything else is fair game.

• Money movement. Payment runs, card issuance, anything that leaves the bank account. An agent drafting the payment file is useful. An agent releasing it is a risk you have no reason to accept.
• Any change to a supplier's bank details. Treat that email as hostile until a human has confirmed it by phone, on a number you already had, with a person you have spoken to before. This is the one step where automation makes you worse off.
• Contract signature. Somebody with authority reads the term, the auto-renew clause and the liability cap, then signs. An agent can summarise the contract and flag the clauses that will annoy you in eleven months. It does not get to agree to them.
• Vendor security review. Someone has to decide how much risk is acceptable with your customer data inside another company. That is a judgement about your business, not a checklist an agent ticks off.
• The final call between two shortlisted suppliers. When the prices are within a few percent of each other you are choosing a relationship, and what decides it is rarely written in either proposal.

This is how Gravity is built too, for what it is worth. Anything that messages a customer or moves money waits for your approval before it goes. A run that fails on a platform error, with no usable output, is refunded under the refund policy.

Which should you start with?

Answer one question first: do you have a procurement problem, or a spend visibility problem? Most companies under 100 people have the second, and the two have different shopping lists.

If cards and bills are the mess, look at Ramp first. Free is $0 a month per user; Plus is $15 a month per user plus a platform fee based on team size, with 20% off annual billing advertised on the page. It is spend and accounts payable, so it shows you what you pay for without running the buying process.

If you do have a procurement team and somebody senior to sign, the suites are built for you. Tropic at least tells you its floor, $3,083 a month on employee count, before the call. Coupa, Ivalua, SAP Ariba, Zip and Levelpath will not. Work through the AI agent procurement checklist before the first demo.

Task-metered procurement agents are beam.ai's pitch: $50 a month for 200 tasks with one base integration, running to $3,990 at the top. Work out which end your volume lands on.

If you enjoy building, Zapier will wire an intake form to an approval. Free is $0, Professional starts at $19.99 a month, Team at $69, and Agents are sold separately at $400 billed annually. You own it afterwards, including the morning it breaks.

Lindy is credit-metered per seat, $29.99 a month per user on Plus with 3,000 credits. Watch the burn before adding seats. Gumloop Pro starts at $37 a month with a 14-day trial, for somebody who wants AI steps inside a flow they design.

Budget first? The cheapest AI agent platforms and the best AI agent platforms under $50 a month both compare what you get at that end of the market.

Last, and this is my own product, so discount it accordingly. Gravity runs your first agent free, with no card. Pro is then $5 a month during the alpha, and Max is $20 a month for more agents and usage; buy more usage if you run out. It is in private alpha, so the catalogue is still short. It fits when you want the job done rather than a place to build it.

My bias, stated plainly: at 40 people the purchasing problem is five small jobs done inconsistently, and none of them justifies a procurement suite. Put an agent on intake and renewals first. Those two will tell you within a month whether the other three are worth touching.

FAQ

Sources

Every figure below came off the vendor's own page on 22 September 2026. Prices move. Check them yourself before you sign anything.