AI Agent Market Forecasts: What the Numbers Do and Don't Tell You
What published forecasts say about the AI agent market, how far apart they are, what is driving growth and what it means for builders.

The forecast: The most bullish projections talk about an AI agent market worth $100 billion within a few years. The more conservative, published figures are still striking: Grand View Research pegs 2024 market size at around $5.4 billion, growing at roughly 45% a year, with acceleration expected as enterprise adoption matures.
Why this matters: These projections shape where venture capital flows, which problems get solved, and which companies get built. Understanding the forecast helps builders position for where the market is heading.
The builder's question: Is this hype or reality? Where specifically are the opportunities, and what segments are most attractive for new entrants?
Deconstructing the forecast
Let's examine what's actually being measured and predicted.
Market definition
Analysts typically include:
- Autonomous AI agents: Systems that execute multi-step tasks with minimal human intervention
- AI assistant platforms: Conversational interfaces with tool-use capabilities
- Orchestration infrastructure: Frameworks and platforms for building and deploying agents
- Agent-specific tooling: Monitoring, evaluation, and management tools
Notably excluded: General LLM API revenue (counted separately), traditional RPA (robotic process automation), and narrow-scope chatbots.
Growth assumptions
Forecasts like these assume:
| Factor | Assumption |
|---|---|
| Enterprise adoption | Broad deployment of agents across large enterprises |
| Model capabilities | Continued improvement in reasoning and reliability |
| Integration maturity | Standard protocols (MCP, OpenAPI) enabling interoperability |
| Regulatory clarity | Workable frameworks emerging globally |
| Cost trajectory | Steep, continuing declines in inference costs |
If any assumption fails significantly, the forecast adjusts accordingly. Model capability improvements and cost reductions seem safe. Regulatory clarity is the wildcard.
Market segmentation
By deployment model
| Segment | Share today | Direction |
|---|---|---|
| Cloud/API | Largest | Growing, but losing share |
| On-premises | Smaller | Growing |
| Hybrid | Smallest | Growing fastest |
The shift toward hybrid deployments reflects enterprise security requirements and the emergence of capable smaller models that can run locally.
By use case
| Use case | Maturity today | Growth outlook |
|---|---|---|
| Customer service | Most mature | Strong |
| Sales and marketing | Established | Strong |
| Software development | Established | Very strong |
| Operations and finance | Emerging | Strong |
| Research and analysis | Emerging | Strong |
Customer service leads because the ROI case is clearest and implementation is most mature. But software development looks like the breakout category, with developer tooling moving fastest.
By company size
| Segment | Share today | Direction |
|---|---|---|
| Enterprise (>1000 employees) | Majority | Losing share as others catch up |
| Mid-market (100-1000) | Significant | Gaining share |
| SMB (<100) | Small | Gaining share |
Enterprise dominates today because agents require integration with existing systems - something large companies have capacity to implement. As tooling matures, mid-market and SMB adoption accelerates.
What's driving growth
Pull factors (demand side)
Labour economics: In markets facing skilled labour shortages, agents provide scalable capability. A single customer service agent platform can handle a volume of inquiries that previously needed a large team.
Competitive pressure: As early adopters demonstrate productivity gains, laggards face competitive disadvantage. This creates adoption cascades within industries.
Capability improvements: Each model generation expands what agents can reliably do. GPT-4 enabled function calling; subsequent models improved reliability to production-grade levels.
Push factors (supply side)
Venture investment: Billions of dollars flowed into AI agent startups in 2024. This capital is creating products that find markets.
Platform effects: Microsoft, Google, and Amazon are embedding agent capabilities into enterprise platforms. When agents come bundled with existing tooling, adoption friction drops.
Open source momentum: Frameworks like LangChain, AutoGen, and CrewAI lower the barrier to building custom agents. More builders means more solutions means more adoption.
Competitive landscape
Infrastructure layer
The foundation providers capturing platform economics:
| Company | Position | Moat |
|---|---|---|
| OpenAI | Model + platform | Capability leadership, distribution |
| Anthropic | Model + safety | Enterprise trust, reliability focus |
| Model + cloud | Integration with GCP, Workspace | |
| Microsoft | Distribution + model (OpenAI) | Office, Azure, GitHub ecosystem |
| AWS | Infrastructure + Bedrock | Enterprise relationships, multi-model |
These players capture baseline compute and API revenue regardless of which agent platforms win.
Platform layer
Companies building agent orchestration and deployment:
| Category | Leaders | Challengers |
|---|---|---|
| Horizontal platforms | LangChain, Anthropic Claude | Fixie, Dust, OpenHelm |
| Vertical solutions | Harvey (legal), Abridge (healthcare) | Multiple per vertical |
| Enterprise orchestration | Microsoft Copilot, Salesforce Einstein | ServiceNow, SAP |
The platform layer is where most value will be captured. Horizontal platforms compete on developer experience and ecosystem. Vertical solutions compete on domain expertise and integration depth.
Application layer
End-user products built on agent capabilities:
- Customer service: Intercom, Zendesk, Freshdesk adding agent features
- Sales: Outreach, Apollo, Gong integrating AI agents
- Development: GitHub Copilot, Cursor, Replit evolving toward agents
- Operations: Notion, Asana, Monday adding AI automation
Application layer is crowded but large. Winners will be those who solve real workflows, not those with the flashiest AI demos.
Where the opportunities lie
Underserved verticals
Some industries lag in agent adoption despite clear use cases:
| Vertical | Opportunity | Blockers |
|---|---|---|
| Construction | Project coordination, safety compliance | Fragmented tech stack |
| Agriculture | Yield optimisation, supply chain | Connectivity, data quality |
| Manufacturing | Quality control, maintenance prediction | Legacy systems |
| Local government | Citizen services, permit processing | Procurement, security |
Startups that can navigate industry-specific blockers have less competition and stickier customers.
Horizontal capabilities
Several capabilities remain unsolved and valuable:
Multi-agent coordination: Enabling agents to collaborate on complex tasks. Current solutions are brittle.
Long-term memory: Agents that remember and learn from past interactions across sessions.
Reliable tool use: Despite improvements, tool calling still fails too often for mission-critical applications.
Human-agent collaboration: Better interfaces for humans to supervise, correct, and train agents.
Infrastructure gaps
Supporting infrastructure that agents need:
Evaluation and testing: How do you know if your agent actually works? Testing frameworks are immature.
Monitoring and observability: What is your agent doing in production? Current tools provide limited visibility.
Cost management: Agent workloads can be expensive. Tooling to optimise costs is nascent.
Security: Agent-specific attack vectors (prompt injection, tool abuse) need specialised defences.
Reasons for scepticism
Not everyone agrees with the $100B forecast. Counterarguments:
Capability plateau: What if model improvements slow? Agents become much less compelling without continued capability gains.
Integration friction: Enterprise software integration remains painful. Agents that can't connect to existing systems have limited value.
Trust barriers: Will enterprises trust autonomous systems with consequential decisions? Adoption may be slower than projections assume.
Economic headwinds: If recession hits, AI budgets get cut. The forecast assumes continued investment.
Regulatory risk: Aggressive regulation could constrain agent deployment in key verticals.
These are real risks. The base case forecast likely represents the optimistic end of the probability distribution.
Our take
The directional trend is clear: AI agents will be a massive market. Whether it's $50B or $150B by 2028 matters less than the certainty that it's growing rapidly.
For builders, the implications:
- The market is real. This isn't speculative technology - enterprises are deploying agents today with measurable ROI.
- Platform economics apply. Companies that become platforms where others build will capture disproportionate value.
- Vertical depth wins. Generic "AI agent for everything" plays will struggle. Deep expertise in specific workflows creates defensibility.
- Infrastructure is undervalued. The picks-and-shovels opportunity (evaluation, monitoring, security) has less competition than application layer.
- Timing matters. Too early and you're educating the market. Too late and you're competing with well-funded incumbents. The next 18 months represent a window.
The $100B forecast might be wrong in specifics. But the opportunity it describes is real.
---
Further reading:
- /blog/ai-agents-market-growth
- /blog/how-to-implement-autonomous-ai-agents-2025
- Grand View Research AI Agent Report
---
Frequently Asked Questions
Q: What's the typical ROI timeline for AI agent implementations?
Many organisations see positive ROI within a few months of deployment, with improvements compounding as teams optimise prompts and workflows based on production experience.
Q: How long does it take to implement an AI agent workflow?
Implementation timelines vary based on complexity, but most teams see initial results within 2-4 weeks for simple workflows. More sophisticated multi-agent systems typically require 6-12 weeks for full deployment with proper testing and governance.
Q: How do AI agents handle errors and edge cases?
Well-designed agent systems include fallback mechanisms, human-in-the-loop escalation, and retry logic. The key is defining clear boundaries for autonomous action versus requiring human approval for sensitive or unusual situations.
More from the blog
How to Set Up Claude Code on a VPS: A Complete Guide
Claude Code VPS setup, step by step: provisioning, authentication, tmux vs systemd, security, and an honest look at when a VPS beats running locally.
Claude Code Agent Teams: How to Run Them on a Schedule
Claude Code Agent Teams runs up to 10 parallel Claude instances against one task list. What it is, how it works, and how to schedule runs.
Stop doing the work around the work
OpenHelm connects to your tools, reads the context, and does the steps, so you sign off on the result instead of producing it. See how it covers an entire role’s weekly workload, check the pricing, or run it yourself with the free local app.