The first sign at most companies that an AI agent has joined the org chart is an expense line item that nobody recognises.

Procurement teams have spent two years quietly digesting a wave of agent-vendor onboardings. What started as a handful of single-team pilots is now line items on the same vendor-master that lists janitorial services and cloud commits — sometimes with seat counts, sometimes with rate-card pricing-per-task, almost always under a category that did not exist three quarters ago.

The vendor-master is the new org chart

Three Fortune 500 procurement leads we spoke to said the same thing: HR has not asked for a meeting. The teams adopting agents have, so far, done it through procurement channels — vendor-master entries, master service agreements, security review — without it touching headcount planning at all.

This is partly because the work an agent does isn't a job, in the legal sense. It's a service. But the day-to-day reality looks identical: somebody has a backlog, somebody else clears the backlog, the company pays for the service. When the somebody-else is a model running an internal tool over MCP, the only artifact the org ends up with is a usage report.

"We have agents that resolve more tickets than half the team. They're a vendor in our books. They're a teammate in everyone else's." — Director of IT Ops, mid-cap insurer

What the form actually asks

One thing procurement has figured out, faster than the rest of the org, is the right vendor questionnaire for an agent provider. We collected nine onboarding templates from companies of varying size; the questions converge on a small set:

  • What identity does the agent present in your logs?
  • Which of your systems does the agent retain access to between sessions?
  • Who reviews and approves the actions the agent takes?
  • What is your incident-response runbook when an agent acts incorrectly?

None of those are HR questions. All of them used to be.