Fifty Agents, No Orchestra: The Sprawl Nobody Budgeted For

I once argued that AI agents should have job descriptions — a written role, boundaries, KPIs, someone responsible for the outcome. That was the hiring conversation. This is the management conversation, and it's uglier: what happens when every team hires five agents and nobody conducts the orchestra? Walk through any mid-size enterprise right now and count. Marketing has a campaign agent and a content agent. Sales has a prospecting agent and a forecasting agent. Support has a triage agent. HR has a screening agent. Engineering has three nobody will admit to. Finance is piloting two. That's fifty agents before lunch, each deployed by a team that did the responsible thing locally — wrote the job description, set the boundaries — and never once asked what happens when all fifty start interacting. The agent that promises a customer a refund by Friday. The agent that approves the budget the first one just spent. Nobody's agent is misbehaving. The ensemble is. This is the failure mode nobody budgeted for — literally. Nobody budgeted for it, because nobody planned the fleet. We deployed agents the way we used to buy software: one team at a time, each solving its own problem, each convinced its five agents were the whole story. But agents aren't software licenses. They're workers. And fifty workers with no manager, no org chart, and no shared rules isn't a workforce — it's a crowd. Run it through SPICE: Strategy. You need an agent portfolio, not an agent collection. Go back to the job-description question and ask its portfolio sibling: which jobs deserve agents at all, and which of those deserve your agents versus a shared service? I'm watching governed agent catalogs emerge — including for federal agencies — and the smart ones aren't bureaucracy; they're portfolio management. A catalog says: here are the approved agents, here's what each is allowed to do, here's who owns it, here's what it costs. That's not red tape. That's the difference between a fleet and a stampede. Politics. Here's where it gets delicate: every team owns its agents, and nobody owns the interactions. When marketing's agent makes a promise that fulfillment's agent can't keep, whose problem is that? Marketing's? Fulfillment's? The AI center of excellence that approved both deployments and neither integration? Turf wars love a vacuum, and agent-to-agent interactions are currently a vacuum with API keys. The politics have to be settled explicitly — interaction ownership, escalation paths, who can override whom — before the first cross-agent failure, not during it. Because "not my agent" will become the new "not my department," and it will be just as corrosive. Innovation. The real innovation here isn't another agent — it's the conducting layer. A registry where every agent declares its capabilities, its limits, and its owner. Standards for agents to identify themselves to each other and to the humans watching. An orchestration tier that sees the whole ensemble: who's calling whom, who's duplicating whom, who's about to step on whom. The organizations building this now aren't slowing agents down; they're making fifty agents safer than five were without it. Conducting isn't control-freakery. It's what turns noise into music. Culture. Start managing agents like the workforce they've become. Onboard them: announced, documented, with a named owner. Evaluate them: against the job description, on a cadence, with consequences. Retire them: decommissioned cleanly when the job changes, not left running in a corner consuming budget and confusing everyone. "You wrote the job description" was step one. Step two is writing the org chart. A culture that treats agents as disposable scripts will get disposable outcomes; a culture that manages them as staff will get leverage. Execution. And now the part nobody wants to say out loud: the bill. Metered API costs multiplying across fifty agents. Three teams paying for three agents that do the same job. The security review nobody scheduled because each deployment was "small." Audit the fleet the way you'd audit headcount: every agent gets an owner, a cost center, a kill switch, and a review date. Kill the duplicates — gently, with migration, not with a midnight revocation. And put agent spend in the budget where everyone can see it, because invisible spend is how fifty became a hundred while nobody was watching. Today, the enterprise has fifty agents and no orchestra — each one well-behaved, each team responsible, and the whole thing one interaction away from an incident nobody owns. Tomorrow, the winners won't have fewer agents. They'll have a catalog, a conductor, and a budget line with a name on it. You wouldn't hire fifty people with no manager, no org chart, and no budget. So why did you do it with agents?