CURRENT
Example Publisher Logo

CURRENT

A journal for living in the agentic age

Daily Brief
Market Pulse
Foundations
Practitioner's Corner
Echoes
Vision

When Organizations Commit to Agents They Don't Yet Have

Organizations restructured around agent capabilities before infrastructure exists to support them—revealing how transformation happens through commitment, not readiness.

By Nora Kaplan— December 10, 2025
When Organizations Commit to Agents They Don't Yet Have

Organizations restructured around agent capabilities before infrastructure exists to support them—revealing how transformation happens through commitment, not readiness.

Seventy-nine percent of executives report their companies have adopted AI agents. Only 16% of enterprise deployments qualify as true agents: systems that plan, execute, observe, and adapt autonomously.

The Gap

Organizational commitment is racing ahead of infrastructure capability—and that reveals how transformation actually happens.

The gap between these numbers isn't semantic confusion. Organizations have committed to agent-driven workflows before the infrastructure exists to support them. From where we sit at TinyFish, building enterprise web agent infrastructure, that gap reveals something crucial about how transformation actually happens.

What Infrastructure Builders See

The pattern shows up in the requirements. Teams reach out saying they've "adopted agents" and need infrastructure to run them at scale. Then the questions start: How do we handle authentication across fifty regional site variations? What happens when DOM structures change mid-workflow? How do we monitor agent behavior when we can't see inside the black box?

These aren't questions from teams running true agents. They're questions from teams who've restructured work around agent capabilities they don't yet have, and are now discovering what production-grade infrastructure actually requires.

The organizational changes are real. Forty-six percent of executives fear falling behind competitors, and 88% are increasing AI budgets. That pressure drives teams to reorganize before infrastructure exists. They create "monitor and decide" roles instead of "gather and check" roles. They build workflows expecting systems to handle multi-step processes autonomously. They set decision-making cadences that assume information arrives at internet speed.

Then they need infrastructure that can actually support what they've committed to running.

The performance creates the necessity.

The Production Gap Becomes Visible

RFPs reveal the disconnect. Teams ask for "reliable agent orchestration" but their requirements show they're running enhanced automation, systems that need human oversight at every decision point. They want "autonomous web navigation" but haven't considered how bot detection, rate limits, and personalization make the web adversarial to automation.

Observability requirements expose the gap between claimed capability and actual need. Teams that truly run autonomous agents need to see inside decision-making: why did the agent choose this path, what triggered this retry, how did it handle this authentication challenge? Teams running copilots or orchestration need simpler monitoring because humans are still making the decisions.

But once you've restructured teams around agent-driven workflows, you can't go back to manual processes without losing the organizational gains you've already captured. The competitive analyst team that eliminated daily website checking can't return to that workflow. They've reallocated that time to strategic analysis. The pricing team that built dashboards expecting real-time data can't revert to weekly reports. Their decision cadence has changed.

The organizational commitment creates irreversible pressure to build the infrastructure that makes the commitment real.

Where the Infrastructure Race Leads

The numbers tell the story:

  • Growth projection: $7.63 billion in 2025 to $50.31 billion by 2030
  • Enterprise integration: Gartner predicts 40% of enterprise applications will integrate with task-specific agents by end of 2026, up from less than 5% today

Claimed adoption is driving real infrastructure development. Organizations that structured work around future capabilities are now demanding production-grade systems to support those workflows, systems that handle authentication complexity, site structure changes, and the web's adversarial nature at scale.

The 79% aren't confused about what they're running. They're ahead of the infrastructure, having committed to a future where work gets delegated to autonomous systems. That commitment is reshaping teams, decision-making, and what humans spend their time doing.

By 2026, the real test won't be adoption numbers. It will be whether infrastructure can evolve fast enough to support the workflows already built around agents, and what breaks in organizations that committed to capabilities they can't yet reliably deliver.


Things to follow up on...

  • The organizational cost: Forty-two percent of companies report that AI adoption is "tearing their company apart" through power struggles, conflicts, and even sabotage as teams restructure around capabilities they don't yet have.

  • What actually scales: McKinsey found that fewer than 10% of AI use cases ever make it past pilot stage, revealing the gap between organizational commitment and production readiness.

  • The pricing model debate: Oracle and SAP are embedding AI into base subscriptions rather than charging premium add-ons, betting that "AI included" will drive adoption faster than consumption-based pricing.

  • Where true agents exist: Only 23% of organizations are scaling agentic AI in at least one function, and most deploy in only one or two functions—showing how rare production-grade agent infrastructure actually is.

Nora Kaplan
ABOUT THE AUTHOR

Nora Kaplan, former collaboration platform product leader turned technology writer. Studied human-computer interaction and spent years designing tools for knowledge work. Now writes about AI agents, work transformation, and how enterprise software reshapes human capability at TinyFish.

Seventy-nine percent of executives report their companies have adopted AI agents. Only 16% of enterprise deployments qualify as true agents: systems that plan, execute, observe, and adapt autonomously.

The Gap

Organizational commitment is racing ahead of infrastructure capability—and that reveals how transformation actually happens.

The gap between these numbers isn't semantic confusion. Organizations have committed to agent-driven workflows before the infrastructure exists to support them. From where we sit at TinyFish, building enterprise web agent infrastructure, that gap reveals something crucial about how transformation actually happens.

What Infrastructure Builders See

The pattern shows up in the requirements. Teams reach out saying they've "adopted agents" and need infrastructure to run them at scale. Then the questions start: How do we handle authentication across fifty regional site variations? What happens when DOM structures change mid-workflow? How do we monitor agent behavior when we can't see inside the black box?

These aren't questions from teams running true agents. They're questions from teams who've restructured work around agent capabilities they don't yet have, and are now discovering what production-grade infrastructure actually requires.

The organizational changes are real. Forty-six percent of executives fear falling behind competitors, and 88% are increasing AI budgets. That pressure drives teams to reorganize before infrastructure exists. They create "monitor and decide" roles instead of "gather and check" roles. They build workflows expecting systems to handle multi-step processes autonomously. They set decision-making cadences that assume information arrives at internet speed.

Then they need infrastructure that can actually support what they've committed to running.

The performance creates the necessity.

The Production Gap Becomes Visible

RFPs reveal the disconnect. Teams ask for "reliable agent orchestration" but their requirements show they're running enhanced automation, systems that need human oversight at every decision point. They want "autonomous web navigation" but haven't considered how bot detection, rate limits, and personalization make the web adversarial to automation.

Observability requirements expose the gap between claimed capability and actual need. Teams that truly run autonomous agents need to see inside decision-making: why did the agent choose this path, what triggered this retry, how did it handle this authentication challenge? Teams running copilots or orchestration need simpler monitoring because humans are still making the decisions.

But once you've restructured teams around agent-driven workflows, you can't go back to manual processes without losing the organizational gains you've already captured. The competitive analyst team that eliminated daily website checking can't return to that workflow. They've reallocated that time to strategic analysis. The pricing team that built dashboards expecting real-time data can't revert to weekly reports. Their decision cadence has changed.

The organizational commitment creates irreversible pressure to build the infrastructure that makes the commitment real.

Where the Infrastructure Race Leads

The numbers tell the story:

  • Growth projection: $7.63 billion in 2025 to $50.31 billion by 2030
  • Enterprise integration: Gartner predicts 40% of enterprise applications will integrate with task-specific agents by end of 2026, up from less than 5% today

Claimed adoption is driving real infrastructure development. Organizations that structured work around future capabilities are now demanding production-grade systems to support those workflows, systems that handle authentication complexity, site structure changes, and the web's adversarial nature at scale.

The 79% aren't confused about what they're running. They're ahead of the infrastructure, having committed to a future where work gets delegated to autonomous systems. That commitment is reshaping teams, decision-making, and what humans spend their time doing.

By 2026, the real test won't be adoption numbers. It will be whether infrastructure can evolve fast enough to support the workflows already built around agents, and what breaks in organizations that committed to capabilities they can't yet reliably deliver.


Things to follow up on...

  • The organizational cost: Forty-two percent of companies report that AI adoption is "tearing their company apart" through power struggles, conflicts, and even sabotage as teams restructure around capabilities they don't yet have.

  • What actually scales: McKinsey found that fewer than 10% of AI use cases ever make it past pilot stage, revealing the gap between organizational commitment and production readiness.

  • The pricing model debate: Oracle and SAP are embedding AI into base subscriptions rather than charging premium add-ons, betting that "AI included" will drive adoption faster than consumption-based pricing.

  • Where true agents exist: Only 23% of organizations are scaling agentic AI in at least one function, and most deploy in only one or two functions—showing how rare production-grade agent infrastructure actually is.

Nora Kaplan
ABOUT THE AUTHOR

Nora Kaplan, former collaboration platform product leader turned technology writer. Studied human-computer interaction and spent years designing tools for knowledge work. Now writes about AI agents, work transformation, and how enterprise software reshapes human capability at TinyFish.