Upwork says AI agents have made nearly 50 million requests on its marketplace since August, and that its new Upwork Now product lets those agents bring in freelancers the moment a need arises. HR and procurement teams should amend their contingent-labor policy now so that it names AI agents as requesters, with approval limits, before an agent books anyone.
What Upwork reported
In its third-quarter results release of 2 November, Upwork described a marketplace that now has a second kind of buyer. “At the same time, the launch of Upwork’s MCP server is opening our marketplace to AI agents as a new class of client,” chief executive Hayden Brown, president and CEO of Upwork Inc., said in the release.
The release puts numbers on it. Weekly active users of the Model Context Protocol server have risen 20x since the August launch. AI agents have made nearly 50 million requests, which the company says drove more than $3 million in estimated annualized Connects revenue. Upwork also launched the public beta of Upwork Now, which connects clients with freelancers who are online and ready to start immediately. The release says it is also available through the MCP server, “so people and their AI agents can bring in those freelancers the moment a need arises and without leaving their AI workflow.”
Where the policy gap is
Most contingent-labor policies were written for a person who raises a requisition, a manager who approves it and a procurement team that checks the vendor. The requester in that model is a named employee. An agent working from a prompt inside someone’s AI assistant does not fit any of those roles, and the policy is silent on it.
That silence matters because the release describes speed as the product. A freelancer who is “online and ready to start working immediately” can be engaged before the approval chain has met. Spend limits, scope descriptions, worker-classification checks and data-access rules all sit in that chain. If an agent can start the engagement from inside a chat window, each of those checks needs a written answer for the case where no manager clicked anything.
I would add four lines to the policy:
- Name the requester. Every engagement started by an agent is logged to a named employee who answers for it.
- Set a ceiling. An agent may commit up to a stated amount without approval, and above it a person signs.
- Require a scope statement. The agent writes what the freelancer will deliver and what data they may see, and a person can read it before work starts.
- Keep classification with people. Whether a worker is a contractor or should be an employee stays a human decision, because the engagement moves faster than the legal analysis.
HR already has some of this thinking on paper for its own tools. This site argued that HR should tell employees how far its AI agents can act, and covered four vendors’ cases for trusting AI agents with pay data. Agents that purchase labor are the outward-facing version of the same question, and they involve money leaving the company.
The strongest objection
The fair objection is scale. Upwork reported third-quarter revenue of $185.6 million. Agent-driven Connects revenue of more than $3 million a year is small next to that, and the release does not say how many of the 50 million requests ended in a contract. A policy for a behavior that few employees use yet looks premature.
I accept the numbers and disagree with the conclusion. The release describes a product launched in August and a beta launched on 2 November, so the figures show the first weeks of a channel the vendor is pushing, with a 20x rise in weekly users already. A policy written after the first surprise invoice or the first contractor with access to a shared drive is a policy written under pressure. Writing four lines now costs an afternoon.
There is also a plain check HR can run this week. Ask procurement and IT whether any employee has connected an AI assistant to a freelance marketplace, and who would see the spend if one had. If nobody knows, the policy gap is already live, and the first step is to find out.
Source: Upwork Inc., Third Quarter 2026 Financial Results (SEC Form 8-K, Exhibit 99.1)
