Agent Scale Has a Company-Size Gap

Two people at a small company are more than a year into building a gateway, a registry, and a governance council, and no agent has yet touched a customer. I’ve watched a handful of versions of that scene over the past year, and this year’s adoption data suggests it isn’t rare. McKinsey’s August survey has 40% of organizations above a billion dollars in revenue reporting that they’re scaling AI agents, up from 27% a year ago. Below that line: 22%, flat year over year.

Before building on that, note what a survey rate can’t say. A conglomerate has hundreds of workflows; one scaled agent anywhere lets its respondent answer “scaling,” so some of the gap is arithmetic: more workflows, more chances to report. And a smaller firm may be rationally slower. With fewer workflows whose volume justifies the evaluation, supervision, and failure costs agents carry, the correct agent count for some businesses is currently zero. Both explanations are live. The hypothesis I’d add, from that handful (a sample, not a study), is that a real constraint sits in the gap too: scaling agents needs scaffolding, meaning evals, identity, cost control, rollback , and the reference architectures for that scaffolding ship in enterprise size only. Big companies staffed a platform team. Small companies read the same posts, correctly concluded they couldn’t afford one, and stayed in permanent pilot. If that’s right, the failure mode below the line isn’t absent ambition, it’s the miniature enterprise program: a year or more of foundation for workflows that needed a few weeks, recreating the bottleneck platform teams become with none of the amortization that justifies them.

The correction isn’t a smaller platform. A small company needs one workflow with an owner, a quality gate, a security boundary, a cost ceiling, and an off switch. Five entry conditions, each written as a test an executive can check, not a system to build.

An owner: one named person for one commercially real workflow, whose review includes the adoption and outcome numbers, not a side quest . Test: you can say who, and they can say what number they’re moving. A quality gate: a few dozen real cases with pass criteria a domain expert wrote, versioned, run on every change, blocking on failure. That’s the benchmark only you can build , at minimum viable size. Test: a change that degrades the eval set cannot ship. A security boundary: the agent holds its own deny-by-default credentials scoped to that workflow’s systems, and you have revoked them once to prove you can. Test: the revocation drill happened. A cost ceiling: the workflow’s spend on its own billing tag, with a threshold that alerts the owner. Test: the owner saw last week’s number. An off switch: a rehearsed way to route the workflow back to the manual path, with the detection that triggers it. Test: you’ve run it, and the workflow survived the hour.

Then the discipline that makes five conditions sufficient where a platform wasn’t necessary: the amortization rule. Scaffolding amortized across one workflow must be nearly free, so nothing generalizes until workflow two demands it. The registry arrives when two workflows share prompts, the gateway when two owners need the same boundary, the standing review when there are enough numbers to fill one. Abstractions earn existence on the second use. The go/no-go for workflow one is the same arithmetic: expected value of the workflow, against evaluation, supervision, failure, and operating cost. If nothing clears that bar, the right answer is zero agents this quarter, and none of the five conditions built on spec. That outcome is also the falsifier for my hypothesis: a company that meets the five conditions on a worthwhile workflow and still can’t scale it is evidence the constraint lives somewhere else.

If you run a larger org, invert the reading. Your platform investment finally pays in exactly the coin the survey suggests, and the risk is spending the advantage on ceremony instead of workflows that route work differently . Either side of the billion-dollar line, the unit of progress is the same, and it isn’t a platform. It’s one workflow, owned, gated, bounded, metered, and stoppable. Then the next one.