AI Agents
From chatbots that talk to systems that act: what agents really are, where they already work, why most projects fail, and who captures the value.
A chatbot answers questions; an agent gets things done: it plans, uses tools, and acts on your behalf. Agents are where AI's promise meets operational reality, and the gap between the two is exactly where fortunes will be made and burned.
What this argues
- Agents are AI with handsModels that plan, call tools, and complete multi-step work.
- Coding proved the patternSoftware engineering is the first industry visibly reorganised.
- Reliability is the productA 95%-reliable agent is a demo; 99.9% is a business.
- Most projects will failGovernance and ROI gaps, not model quality, kill them.
- Value flows to the workflowWhoever owns the work being automated captures the gain.
What has changed
Updated November 2026
Deployment is still a minority of firms
Gartner's 2026 CIO and Technology Executive Survey, cited in its Hype Cycle for Agentic AI (15 April 2026), found 17% of organisations have deployed AI agents and more than 60% expect to within two years (as reported by Digital Applied, July 2026).
Production-ready systems remain around one in nine
Deloitte's Tech Trends 2026 (10 December 2025) reported 11% of organisations with production-ready agentic systems and 42% without a formal agentic AI strategy.
Experimenting is common, scaling is not
McKinsey's State of AI (November 2025) found 62% of organisations at least experimenting with agents and 23% scaling an agentic system somewhere, with no more than 10% scaling agents in any single business function.
The cancellation forecast stands
Gartner's June 2025 press release predicts over 40% of agentic AI projects cancelled by end-2027 on cost, unclear value or weak risk controls. Gartner also projects 33% of enterprise software apps will include agentic AI by 2028, up from under 1% in 2024.
Market size estimates cluster near $11 billion
Grand View Research puts the AI agents market at $7.63B in 2025 and $10.91B in 2026; other firms (Global Market Insights, MarkNtel) give about $10-11B for 2026, with wide long-range variation.
Not refreshed: Google AI-generated code share, developer daily-use rate, the MIT coding study figures, and the Gartner 2028 and 2035 forecasts could not be re-verified and are left as written.
What an Agent Is
From answers to actions
There is a spectrum from autocomplete to autonomy
Five points on the spectrum
| What it does | Mode | |
|---|---|---|
| Autocomplete | predicts your next word | Suggests |
| Chatbot | answers when asked | |
| Copilot | drafts, you approve | |
| Agent | executes multi-step tasks | |
| Autonomous | runs with no human loop | Acts alone |
What an agent actually does, over and over
- Goal: you give it an outcome, not instructions.
- Plan: it breaks the goal into steps.
- Act: it uses tools (browsers, code, APIs, files).
- Check & adapt: it verifies results, fixes errors, and continues.
Chatbot versus agent, side by side
| Chatbot | Agent | |
|---|---|---|
| Output | words for a human to use | completed work |
| Steps | one exchange at a time | dozens, chained together |
| Tools | none, it just talks | code, browsers, systems |
| Failure | a wrong answer | a wrong action |
Even if only half-right, delegated decision-making is entering the workplace faster than any prior enterprise technology.
From viral toy to enterprise roadmap in three years
- AutoGPT: the viral, broken first draft
- Computer use: models learn to click and type
- Protocols: MCP standardises agent-tool wiring
- Embedded agents: 40% of enterprise apps (Gartner)
- Delegation era: 15% of decisions autonomous
How Agents Work
Under the hood, plainly
Five parts make a working agent
- Guardrails: permissions, approvals and audit trails.
- Orchestration: the harness that runs the loop and enforces limits.
- Memory: context it keeps across steps and sessions.
- Tools: what it can touch, including code, browsers, databases, apps.
- The model: the reasoning engine that plans and decides.
Why agents became possible in 2024-26
- Reasoning models: models that think before acting, cutting error rates.
- Tool protocols: standards like MCP let models drive real software.
- Long context: agents can hold a whole task in working memory.
- Computer use: models that see screens and click like a person.
- Cheap inference: thousands of steps per task became affordable.
- Verification loops: agents that test their own work before shipping it.
An agent's real cost isn't the model, it's the error rate compounding across every step of the task. A 99%-reliable step fails 1 time in 100. Chain 50 steps and the task fails 4 times in 10.
Why long tasks are exponentially harder
Agents at Work
Where it's already real
Software engineering is the first industry visibly reorganised by agents, because code can be tested, checked and rolled back.
Where errors are cheap to catch, autonomy scales fast. That is why coding went first.
Coding agents, by the numbers
Agents multiply output, not outcomes
View the data
| Increase | |
|---|---|
| Code written | 180 |
| Code shipped | 30 |
Source: MIT study of 100,000+ developers (2026)
Where agents are deploying next
- Customer operations: resolving tickets end-to-end, not just drafting replies.
- Research & analysis: multi-source investigation compressed from days to minutes.
- Back office: invoices, claims, reconciliation; high-volume, rule-rich work.
- Sales ops: CRM hygiene, outreach drafts, pipeline management.
- IT & security: triaging alerts, patching, access reviews.
- Personal work: inboxes, scheduling, bookings; slower, higher-trust.
Agents spread through enterprise software
View the data
| Share of enterprise apps | |
|---|---|
| 2025 | 5 |
| 2026e | 40 |
| 2028e | 60 |
| 2035e | 80 |
Source: Gartner (2025-26)
The Economics
Who pays, who profits
Who is building the agent layer
- Anthropic: Claude and Claude Code, the reasoning-and-coding agent leader.
- OpenAI: consumer agents at ChatGPT scale; operator-style computer use.
- Microsoft: Copilot embedded across the enterprise estate.
- Salesforce / SaaS: every incumbent bolting agents onto its workflow.
- Startups: thousands of vertical agents for support, legal, finance, ops.
- Open source: frameworks and local agents keeping pricing honest.
A small market growing very fast
View the data
| Market size | |
|---|---|
| 2025 | 7.6 |
| 2026e | 10.9 |
| 2028e | 24 |
| 2030e | 50 |
Source: Grand View Research (2025-26); other forecasts
From seats to outcomes
| Software as seats | Agents as outcomes | |
|---|---|---|
| Unit | per user, per month | per task completed |
| Value | access to a tool | finished work |
| Buyer | IT budgets | operating budgets |
| Growth | headcount-linked | workload-linked |
Where agent value concentrates
A two-by-two map of value per task (vertical) against ease of deployment (horizontal). Coding and research sit top-right, the frontier, with customer ops just right of centre. Legal work and healthcare admin sit top-left (hard, rich). Back office sits near the centre line, on the easy side. The bottom quadrants (hard/modest and easy/modest) are empty.
If even directionally right, agents are not a product category; they are the next business model of the software industry.
What Breaks
Why 40% of projects will die
Gartner expects over 40% of agentic AI projects to be cancelled by 2027, not because the models fail, but because the organisations do.
Unclear ROI, missing governance, and workflows that were never redesigned for delegation.
How agent projects actually die
- Demo-to-production gap: 95% reliability wows a boardroom and breaks a workflow.
- No owner: agents cross team boundaries; nobody owns the outcome.
- Unbounded cost: loops that burn tokens without a budget or kill-switch.
- Compliance stall: legal can't sign off on what it can't audit.
- Workflow mismatch: automating a broken process just breaks it faster.
- Vendor-washing: 'agents' that are chatbots with a new label.
What the successful deployments share
- Narrow first: one well-bounded workflow, measured end to end, not a general assistant.
- Verification built in: every action checkable, reversible, or approved.
- A human escalation path: agents handle the routine; people own the exceptions.
- Real baselines: measured against the process's true cost, not a vendor's slide.
Build your own agents, or buy them embedded?
| Build | Buy embedded | |
|---|---|---|
| Control / Speed | your data, your guardrails | live in weeks, inside tools you use |
| Fit | shaped to your workflow | generic, vendor-shaped |
| Cost | engineering-heavy upfront | subscription plus usage |
| Risk | you own every failure | lock-in and data exposure |
Trust is earned one rung at a time
- Read-only: agents observe and draft; humans act.
- Approve-to-act: agents act only on explicit sign-off.
- Act-and-log: routine actions execute, fully audited.
- Autonomous: trusted workflows run unsupervised, with limits.
Trust & Control
The new questions
Delegation's promise and peril
| The promise | The peril | |
|---|---|---|
| 1 | Leverage: one person directing ten agents | Wrong actions: errors that execute, not just mislead |
| 2 | Speed: hours of work in minutes | Security: agents are a new attack surface |
| 3 | Coverage: 24/7, no backlog | Accountability: who answers for an agent's act? |
| 4 | Cost: marginal labour near zero | Skill erosion: juniors lose the work they learn on |
Six risks a serious adopter tracks
- Prompt injection: malicious content hijacking an agent's instructions.
- Cascading errors: one wrong step compounding through a chain.
- Data exposure: agents with broad access leaking what they touch.
- Runaway cost: loops without budgets or limits.
- Audit gaps: actions no one can reconstruct after the fact.
- Over-delegation: handing off judgement that was the business's edge.
The winning formula of the agent era is not full autonomy, it is human judgement, multiplied by tireless machine execution.
The centaur, not the robot: people setting direction, agents doing the legwork, systems checking the work.
What to Watch
Signposts, not predictions
Four dials worth watching
- Production %: real deployments, not pilots or claims.
- Task success: reliability, the 95 to 99.9 climb.
- $/task: unit economics, falling with compute.
- Incidents: failures and breaches, the trust ledger.
Five signposts for the next 24 months
- Does production catch up to pilots? The 11% number is the one to watch.
- Does reliability cross the threshold? Unsupervised operation in real workflows.
- Does outcome pricing stick? Per-task pricing rewires software economics.
- Does a public failure set rules? One big incident could define regulation.
- Do agents talk to agents? Inter-agent commerce would be a new economy.
Reference
Glossary and sources
Plain-language glossary
| Definition | |
|---|---|
| Agent | an AI system that plans and acts to complete tasks. |
| Copilot | AI that drafts while a human approves each step. |
| Orchestration | the software harness that runs an agent's loop. |
| Tool use | an agent operating software: code, browsers, APIs. |
| MCP | a standard protocol connecting agents to tools and data. |
| Guardrails | limits on what an agent may do without approval. |
| Human-in-the-loop | a person reviewing before actions execute. |
| Prompt injection | an attack that hijacks an agent via its inputs. |
Agents will feel disappointing for two more years and then suddenly indispensable, the standard arc of every platform shift.
The web in 1997, mobile in 2009, cloud in 2012: mocked as toys, then abruptly the default. Agents are on the same clock.
The chatbot era asked what AI knows. The agent era asks what AI may do, and every hard question in business, from trust to accountability, hides inside that single word: may.
The five conclusions to take away
- Action is the product: agents sell finished work, not answers.
- Reliability is the moat: the 95 to 99.9 climb is the whole game.
- Coding is the preview: every industry gets its version, in verifiability order.
- Most projects will fail: organisation, not capability, is the constraint.
- Own the workflow: value accrues to whoever owns the work being automated.
Sources & Further Reading
- Gartner: agentic AI forecasts, Hype Cycle and CIO survey (2025-26).
- MIT: study of AI agents across 100,000+ developers (2026).
- Google / Microsoft: disclosures on AI-generated code share.
- Stack Overflow / developer surveys: AI tool adoption and trust (2025-26).
- Industry forecasts: AI agents market sizing (2025-26).
- Anthropic / OpenAI: agent product documentation and safety frameworks.
- Figures marked 'estimate' or 'projection' are compilations; this field moves fast.
Sources cited
Gartner · MIT · Google · Microsoft · Stack Overflow · Industry forecasts · Anthropic · OpenAI · Developer surveys · Gartner, Apr 2026 (via Digital Applied, Jul 2026) · Deloitte Tech Trends 2026, Dec 2025 · McKinsey State of AI, Nov 2025 · Grand View Research, 2025 · Global Market Insights · MarkNtel Advisors
Keep reading
Research, not investment advice. Figures as of , from the sources cited.
Legal information and disclosures
These are my own views as of the update shown on this page. They can change without notice, and I have no duty to update them. Past performance does not indicate future results, and any investment can lose money.
This is for education only. It is not investment, legal, tax, medical or accounting advice, and it is not an offer to sell or a solicitation to buy any security in any jurisdiction. It does not consider your goals or circumstances.
Figures from company filings, public agencies and other third parties are believed to be reliable, but I have not independently verified them and cannot guarantee them. Forecasts and anything marked as an estimate rest on assumptions that may prove wrong.
Please do not copy or republish this material without my written consent.