90% of Claude Cowork sessions aren't coding — what that says about who you're actually building AI tools for

Anthropic's own usage data from 1.2 million sampled Claude Cowork sessions shows business process and operations work is the single largest category at 33.4%, with software development making up just 8.7% — echoing Epic Systems, where over half of Claude Code usage now comes from non-developer roles.

Anthropic has published usage data drawn from 1.2 million anonymised Claude Cowork sessions across more than 600,000 organisations, and the breakdown cuts against the assumption that AI coding tools are mainly an engineering department’s concern. Business process and operations work — pulling scattered updates into a report, building onboarding checklists, reconciling spreadsheets — is the single largest category at 33.4% of sessions. Content creation and copywriting comes second at 16.4%. Software development accounts for just 8.7%. The same pattern shows up at Epic Systems, the healthcare software company, where Anthropic reports that over half of internal Claude Code usage now comes from non-developer roles — including a pharmacist who built a fully interactive prototype without writing a line of code themselves.

The read-across for anyone commissioning software isn’t that coding tools have become unimportant — Claude Code and its peers are still the fastest-growing category in the AI tooling market. It’s that the buyer for AI-assisted development capability inside a business is no longer just the CTO evaluating a coding assistant. It’s operations leads, clinical staff, finance teams and product managers who now expect to be able to describe what they want and get something functional back, and who are increasingly the ones deciding whether a business’s internal tools get built properly or get left as a patchwork of AI-generated prototypes nobody owns.

So what

That shift raises the stakes on what “AI-assisted” should mean for a commissioned build: not just faster developer output, but software and internal tools designed so non-technical teams can extend or request changes safely, without every prototype becoming unmaintained shadow IT. If your organisation already has non-developers building things with AI tools and nobody has thought about where that meets production-grade software, that’s worth a conversation before it becomes a support burden. See our AI-assisted development work, or get in touch to talk through turning ad hoc AI prototypes into something your team can actually rely on.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work