AI Agents Are Coming for Ops Work, Not Just Code

For the first three years of the generative AI wave, the loudest use case was coding. GitHub Copilot, Cursor, Claude Code, and Anthropic’s own developer tooling defined the category. The implicit market thesis was: engineers adopt first, then everyone else follows.

Anthropic’s Cowork data points the other way.

On 7 July 2026, in How people are using Claude Cowork, Anthropic published Cowork usage data: the largest category of sampled Cowork sessions is business process and operations, at 33.4%. Software development is 8.7% and DevOps and infrastructure 7%. The sample is 1.2M sampled sessions over three weeks, from more than 600,000 organizations. Cowork is Anthropic’s non-terminal product; most coding happens in Claude Code, so this is the shape of Cowork use, not of all AI agent use.

This is first-party usage data rather than a marketing anecdote: the shape of Cowork usage, reported by the company that runs Cowork. If you are a solo founder, an SMB owner, or a mid-market ops lead trying to figure out where to spend your first €10K on AI agents, this split is worth weighing.

What Anthropic actually disclosed

The specifics from Anthropic’s How people are using Claude Cowork (7 July 2026):

• 1.2M sampled sessions over three weeks (11–31 May 2026), classified into 20 categories of work.
• More than 600,000 organizations in the sample.
• Business process and operations: 33.4% of sampled sessions, the largest category.
• Software development: 8.7%. DevOps and infrastructure: 7%.
• Every number is a share of sampled sessions, and the taxonomy classifies the work being done, not the job title of the person doing it.

Separately, Anthropic’s December 2025 survey of 500+ technical leaders found that more than half of organizations (57%) now deploy agents for multi-stage workflows, and that “80% of organizations report their AI agent investments are already delivering measurable economic returns.”

Two things to notice about that split.

First, it is directionally consistent with independent surveys. Upwork’s State of AI Within SMBs in 2026 (10 June 2026) found the use cases most SMB leaders are actively piloting agents for are decision support (41%), information retrieval (36%) and workflow automation (34%).

Second, it maps to what Anthropic charges for. Claude Enterprise pricing is per-seat, and the seats are being bought by ops, finance, and marketing budgets — not engineering budgets. That is a much larger addressable market and Anthropic knows it.

Why the code-first assumption was wrong

Three reasons the industry got the shape of the market wrong for two years:

1. Developers were the loudest early adopters, not the most valuable.
Engineers try new tools fast, tweet about them, write blog posts. That created the illusion of a coding-dominated market. Meanwhile, a finance analyst quietly automating monthly reporting was invisible on X but was reclaiming hours every month.

2. Coding is a legible ROI story. “Ship features faster” is easy to sell to a VP of Engineering with a budget. “Get 6 hours a week back for our controller” is a harder story to tell to a CFO who has never bought AI. So the coding tools were priced, packaged, and pitched first — but the demand curve was always larger on the ops side.

3. Agent tooling reached “good enough for ops” later than “good enough for code.” Code has fast, cheap feedback loops (tests, compilers, human review). Ops workflows require reliable tool use, memory, and coordination that only became stable in the Claude 3.5 → 4.x → 5 window. Once the reliability arrived, ops workflows became practical to automate.

If you are still buying AI agents on the assumption that this is a developer-first category, you are budgeting against the world of 2024, not 2026.

Three implications for how SMBs should buy

Implication 1: Your first agent is almost certainly not in your engineering department.
Even if you have engineers, they are the wrong first team to build for. The ROI density is higher elsewhere: finance closing the books, sales research briefs, support triage, HR onboarding, legal contract review. Find the function with the most repetitive knowledge work per head and start there.

Implication 2: Stop budgeting AI as an IT line item.
If your AI budget lives inside IT, it is under-scoped. IT budgets are sized for infrastructure, not for buying back human time across departments. Move the AI agent budget to the operating budget of the function that will use it. Rebill IT for the infrastructure component (API costs, security review). That way the budget is sized against the hours the function buys back, not against IT’s infrastructure line.

Implication 3: Choose who actually sells AI agents to business by ops fluency, not engineering pedigree.
An engineering-heavy AI shop will build you a technically clean agent that solves the wrong problem. An ops-fluent shop will spend the first two weeks embedded with the team that will use the agent, then build a technically simpler thing that actually gets adopted. In 2026, adoption is the binding constraint, not model capability. Pick accordingly.

How to pick your first non-code agent

If the data says your first agent should be non-code, the practical question is: which non-code workflow? A four-part test that maps well to the Workforce Starter build pattern:

Criterion	Green	Yellow	Red
Repetition	Runs daily or weekly, same shape	Runs monthly	Runs quarterly or ad hoc
Volume	≥4 hours/week per person	1–4 hours/week	Under 1 hour/week
Data source stability	Same 2–3 systems (Gmail, HubSpot, Notion)	4–6 systems	7+ systems or custom formats
Judgment complexity	Rules-based with occasional exceptions	Rules with frequent exceptions	Mostly judgment, no rules

Four greens = ship this quarter. Two greens and two yellows = ship after a light discovery. Any red = pick a different workflow first.

The workflows most SMBs land on when they run this test: inbound lead research briefs, invoice extraction and coding, first-line support triage with routing, weekly reporting drafts, meeting note structuring and action-item extraction. All non-code. All ops work.

The one case where code-first still wins

Two conditions where investing in code-agents first still makes sense:

1. You are a software company selling to developers. Your engineering velocity is your product. Coding agents (Claude Code, Cursor) are direct product-quality investments, not ops overhead. The ops-first argument does not apply to you the same way.

2. You have a legacy modernization backlog that is the strategic bottleneck. If your business runs on a codebase that no one can maintain and code-agents can materially accelerate the modernization, that is a legitimate first spend. Rare, but real.

Everyone else should start in ops.

What to do this quarter

Three concrete steps if you are convinced by the data:

1. Audit where your knowledge workers spend their time. Two weeks, informal, not a McKinsey diary study. Ask each department lead: “What is the workflow that eats the most of your team’s time and produces the most similar-looking outputs?” The answer is your first agent candidate.

2. Skip the AI strategy deck. With this much market data available, another 12-week strategy engagement is not what you are missing. Deploy one narrow agent, learn from the actual deployment, and let the strategy sharpen against real data. See AI Agent vs AI Consultant for the sequencing argument.

3. Ask your finalist vendors to show you a non-code case study. If their strongest reference is a code deployment, they are calibrated for engineering buyers. You are buying for operations. Pick differently.

---

For two years, the engineering conversation has been the loudest. Anthropic’s Cowork data points the other way: in Cowork, operations work is the largest category and software development a much smaller one. For most SMBs, that is a good reason to look at operations first when deciding where the first AI agent goes.

If you want help pressure-testing which non-code workflow in your business is the highest-value first agent, the 30-minute discovery call is designed for exactly that question.

---

Key terms in this post: AI agent · agentic AI · Workforce Starter · tool use · Claude Cowork