AI Statistics

The Pilot Worked. The Business Didn't Change.

On this page
  1. The number that actually moves
  2. Where the pilot actually dies
  3. What this means if you are not a billion-dollar firm
  4. Scale is a kill list, not a bigger budget
  5. Stop funding another pilot week

On September 9, UiPath published a survey of 590 technology leaders at companies with at least $1 billion in revenue. Less than one in three, 31 percent, said AI is fully embedded in the business. Eleven percent are still in a pilot. Thirty-five percent have rolled it out only to select teams.

That is not a small-business poll. The pattern still fits any firm that buys seats and calls it a strategy. A demo runs. A person pastes the output into the real system. ROI stays a slide.

The number that actually moves

The useful split is not "using AI" versus "not using AI." It is whether the work around the model changed.

Among respondents who said orchestration is fully embedded across the enterprise, 89 percent said their agentic implementations met or beat ROI expectations. Only 29 percent said orchestration is fully embedded in their workflows. Source: UiPath AI Adoption and Orchestration Survey, September 9, 2026. Fieldwork ran May 25 to June 8, 2026.

Read that again. Most of the sample has not built the layer that connects the model to the systems, the data, and the person who owns exceptions. The minority that did is the group reporting the return. Same story as the AI productivity gap: saved hours that never reach the P&L.

Where the pilot actually dies

Asked what gets in the way of scaling, leaders named three things more than model quality:

  • Data quality and readiness, 38 percent
  • Integration with existing workflows and systems, 37 percent
  • Governance and compliance, 33 percent

Integration at 37 percent is the line operators should underline. A pilot can ignore the CRM, the inbox, and the approval queue. Production cannot. If the output still waits on a human to copy it, you did not deploy AI. You added a drafting step in front of the old job.

UiPath also found 52 percent of these companies plan to apply AI to hybrid workflows in the next 12 months: part fixed rules, part judgment. Those paths are exactly where a loose pilot fails. Someone has to define the trigger, the system of record, and what happens at 11pm when a step dies.

What this means if you are not a billion-dollar firm

You do not need an orchestration platform with that name on the invoice. You need the same idea at the size of one painful path. The AI agent built into your CRM will not do it for you either. Built-in AI handles tasks, not workflows.

A ChatGPT seat is the pilot. The workflow is the rest:

  • What event starts the work, so it does not depend on someone remembering
  • Which system the result is written into, so Slack is not the database
  • Where a person is required, and where they are not
  • Who gets pinged when it fails, with enough context to fix it once

That is orchestration for a 12-person company. It is also the gap in the survey. Thirty-one percent embedded the tool. Twenty-nine percent embedded the path. The ROI number sits with the second group.

Scale is a kill list, not a bigger budget

When a pilot doesn't pay, the default answer is to raise the budget. Gartner's latest functional leader survey shows how popular that plan is, and how little it has to do with scale.

The survey ran from January to April 2026 and covered 1,303 respondents at organizations with at least $50 million in 2025 revenue. Only 22% had successfully scaled AI across multiple business units or adopted an AI first approach. Meanwhile, 85% of functional leaders plan to increase AI spending in 2026, after putting an average of 12% of their functional budgets into AI in 2025. Roughly 11% didn't know what their function had spent on AI in 2025 at all. Source: Gartner Survey Finds Only 22% of Organizations Have Successfully Scaled AI Across Multiple Business Units.

The useful part is how Gartner describes high performers. They constantly track the ROI of AI initiatives, treat AI as a portfolio, and regularly reallocate or shut down what underperforms. Those organizations reported positive returns on 81% of their AI initiatives. Low performers didn't know the rate of return for 29% of theirs.

That is an operating rule, not a model tip:

  • Every AI initiative has an owner, a cost, and a kill date if the metric doesn't move
  • Underperforming work loses budget on purpose, not by accident
  • New spend waits until you can say what last quarter's spend bought

Before you ask for more money, write the kill list. One page is enough: each AI or automation spend, the path it was supposed to change, the metric, and the last date anyone checked it. That is the same idea as an automation list instead of an AI strategy, with a column for what gets switched off.

Stop funding another pilot week

If last quarter's AI experiment produced a thread of nice drafts and no change in how the week runs, do not buy a second tool to fix the first. Write the path the pilot skipped. If the spend is going to tools instead of one owned path, why enterprise AI tools burn budgets covers the same trap.

Pick one repeating job. Name the trigger. Name the system that must update. Name the stop. Then let the model touch only the step that needed judgment or drafting. The survey's 89 percent did not get there by prompting harder. They got there by putting the model inside a process someone owns.

A pilot is a demo. The path is the product. Build that, and the usage stat finally has somewhere to land.

Each new post by email. Confirm your address first, unsubscribe anytime.

Keep reading

Ready to automate?

If the AI seat is live and the old process is still the system of record, a 30-minute discovery call is enough to pick one path and see what a right-sized build looks like.

Book a discovery call →