Services are the new software: Sequoia's thesis explained

Services are the new software: Sequoia's thesis explained
$6spent on services for every dollar spent on software
49.7%of agent tool calls are software engineering
10sectors analyzed on the opportunity map
340,000fewer accountants in the US in five years
Services are the new software: Sequoia's thesis on copilots vs autopilots
I also explain it in this eleven-minute video on my channel Articulator EN.

The thesis: sell the work, not the toollink

Every founder building an AI tool is asking the same question: what happens when the next version of Claude turns my product into a feature? According to Bek, they're right to worry. If you sell the tool, you're in a race against the model.

But if you sell the work, the race flips: every improvement in the model makes your service faster, cheaper and harder to compete with. The article's example makes it obvious. A company might spend $10K a year on QuickBooks and $120K on an accountant to close the books. The next legendary company won't sell the software. It will just close the books.

Two yearly cost bars: $10,000 for the accounting software, crossed out, versus $120,000 for the accountant, with the caption 'Will do the work'.
The budget is in the work, not in the tool.

Intelligence versus judgementlink

To work out which work AI can already do, Bek separates two things:

  • Intelligence: work that follows rules, even complex ones. Turning a spec into code, testing and debugging are rules.
  • Judgement: what takes experience, taste and instinct built over years of practice. Deciding which feature to build next, whether to take on tech debt, or when to ship before it's ready.
Split screen: writing code equals intelligence, in cyan, and what to build next equals judgement, in orange.
Writing code is mostly intelligence; knowing what to build is judgement.

Software engineering is mostly intelligence work, and that's why it got there first. A year ago, most Cursor users treated AI as autocomplete; today, more tasks are started by agents than by humans. The article says software engineering accounts for "over half" of AI tool usage; its own chart shows 49.7% of agent tool calls, with no other category reaching 10%.

Bar chart: software engineering at 49.7% of tool calls and every other category below a red 10% line.
The article's chart: almost half, versus under 10% for any other category.

Bek's conclusion: AI has crossed the threshold where it can do most of the intelligence work on its own and leave the judgement to people. Software engineering got there first, but it's coming to every profession.

Copilots and autopilotslink

That leads to the article's core distinction: a copilot sells the tool; an autopilot sells the work.

On the left, an airplane control yoke: the copilot sells the tool. On the right, an airplane: the autopilot sells the work.
A tool for the professional, or the outcome for the end customer.
Copilot

Puts AI in the hands of a professional, who decides what to do with it and owns the output. Harvey sells to law firms; Rogo, to investment banks. It was the right move while models were still developing intelligence and judgement.

Autopilot

Sells the outcome directly to whoever needs it. Crosby sells the NDA to the company, not to its outside counsel; WithCoverage sells insurance to the CFO, not to the broker.

The key is the money: in any profession, the work budget dwarfs the tool budget, and autopilots capture it from day one. The higher the intelligence ratio in a field, the sooner autopilots will win.

A small tool budget bar next to a huge work budget bar, captured by an airplane from day one, and an intelligence-work slider that brings the win forward.
The more intelligence in a field, the sooner the autopilot wins.

Convergencelink

Today's judgement will become tomorrow's intelligence. As these systems gather proprietary data about what good judgement looks like in their field, the frontier moves. Copilots and autopilots will converge, and in several categories that shift has already begun.

A spectrum from judgement to intelligence whose frontier moves toward judgement as proprietary data flows in.
With proprietary data, the frontier moves toward judgement.

That's why the starting point matters: it decides where an autopilot can win customers today, and where it starts compounding the data that will eventually let it handle judgement too.

The playbook: outsourcing as the wedgelink

For every dollar spent on software, six are spent on services. An autopilot's total market is all the labor spend in a category, insourced and outsourced. But the right place to start is where outsourcing already exists, because an outsourced task tells you three things:

1. It's done outside

The company already accepts that someone else does this work.

2. There's a budget

There's a budget line that can be cleanly replaced.

3. It buys an outcome

The buyer already pays for the result, not for hours.

The practical difference is huge: replacing an outsourcing contract with an AI-native provider is a vendor swap; replacing headcount is a reorg.

On the left, an AI-native provider replaces the outsourcing contract with a green check; on the right, a shaking org chart with a red cross: reorg.
Swapping a vendor is easy; reorganizing your staff is not.

So the playbook is: start with the outsourced, intelligence-heavy task, nail distribution, and expand toward insourced, judgement-heavy work as the AI compounds. The outsourced task is the wedge; the insourced work is the long-term market.

The three steps of the playbook next to a two-axis map: the starting point in the top right as the wedge and the whole map as the long-term market.
Start in the top right and grow toward judgement.

The example is Crosby, which started with NDAs: a well-defined task, mostly intelligence, that most companies already outsource to external counsel. The budget exists, the scope is clear, the ROI is immediate and the substitution is frictionless.

The opportunity maplink

Bek plots every services vertical on two axes, from judgement to intelligence and from insourced to outsourced, with its labor spend. He presents it as an illustrative map:

  • Autopilot territory (outsourced, intelligence): insurance brokerage, IT managed services, payroll, claims adjusting, accounting, healthcare revenue cycle, mortgage origination, tax advisory, transactional legal…
  • Next wave (intelligence still done in-house): supply chain and procurement, pharmacy back-office, medical and fund administration.
  • Copilot territory (outsourced, judgement): management consulting, design, executive search, PR.
  • Watch (insourced, judgement): recruitment, advertising, freight brokerage, clinical trials, cybersecurity…
The two-axis map with its four quadrants: autopilot territory, next wave, copilot territory and watch, each with its sectors and spend.
The four quadrants of the article's map.

Sector by sectorlink

The article walks through ten sectors. The figures are labor spend:

Insurance brokerage · $140-200B

The largest in autopilot territory. Standard commercial lines are highly standardized: the broker shops across carriers and fills in forms. Tens of thousands of small brokers, so nobody owns the customer. WithCoverage and Harper.

Accounting and audit · $50-80B

Outsourced, in the US alone. Roughly 340,000 accountants lost in five years while demand grew, and 75% of CPAs are nearing retirement. Rillet is building the AI-native ERP; Basis started as a copilot.

Healthcare revenue cycle · $50-80B

It sounds like judgement, but billing is almost pure intelligence: translating clinical notes into about 70,000 ICD-10 codes. Outsourcing is mature and outcome-based. Anterior is furthest along.

Claims adjusting · $50-80B

The other side of the policy: interpreting policy language against damage schedules and setting reserves with actuarial tables. Adjusters are aging out. Pace and Strala.

Tax advisory · $30-35B

Licensing is a regulatory moat, but 80-90% of the work is intelligence, and every new jurisdiction deepens the data moat. TaxGPT, Skalar and Ravical.

Transactional legal · $20-25B

Contracts, NDAs and regulatory filings, standard enough that quality can be verified. Harvey is moving toward autopilot; Crosby and Lawhive were born that way.

IT managed services · $100B+

Patching, monitoring, user provisioning and alert triage, repeated across thousands of identical environments. Nobody sells "your IT runs" directly to the company yet. Edra and Serval.

Supply chain and procurement · $200B+

Most enterprises only negotiate seriously with their top 20% of suppliers, and contract leakage runs 2-5% of spend. Abandoned work means found money. Magentic, AskLio and Tacto.

Recruitment and staffing · $200B+

Screening, matching and outreach are intelligence; closing a candidate and judging culture fit are judgement. The wedge is high-volume roles. Juicebox, Mercor and Jack & Jill.

Management consulting · $300-400B

Huge, but mostly judgement. The question is whether it can be split into an intelligence layer (data gathering, benchmarking) and a judgement layer (strategic recommendations). Bek doesn't name any standout startup yet.

The innovator's dilemmalink

In 2025, the fastest-growing AI companies were copilots. In 2026, many will try to become autopilots: they have the product and the customer knowledge. But they face the innovator's dilemma: their customer is the professional, and selling the work means cutting that customer out. That's the opening for pure-play autopilots.

An airplane flies through the gap a copilot leaves when it splits from its customers, captioned 'Pure-play autopilots'.
The gap copilots leave is for whoever is born an autopilot.
In one sentence

If you sell the tool, you compete with the model; if you sell the work, every new model plays in your favor. Start with outsourced, intelligence-heavy work and grow toward judgement.

What work in your field do you think an autopilot will take over first?

Sourceslink

Continue reading

Last posts -->

Have you seen these projects?

Gymnasia

Gymnasia Gymnasia
Expo
React Native
TypeScript
OpenAI
Anthropic

Fitness app with two agents that run entirely on the device, with no backend, so the user's data never leaves the phone. A BYOK conversational coach with local tools and a remote system prompt with offline fallback, plus a food estimator that pulls macronutrients out of a photo of the plate, with barcode scanning against OpenFoodFacts.

LangGraph Deep Researcher

LangGraph Deep Researcher LangGraph Deep Researcher
Python
LangGraph
FastAPI
React
TypeScript
Docker

Multi-agent research system built with LangGraph. A supervisor breaks your question down into topics and launches search sub-agents in parallel; each one compresses its findings before handing them to a writer agent that produces the final sourced markdown report. Live streaming over WebSockets, a configurable model per role and bring-your-own API keys that are never persisted server-side.

Tau

Tau Tau
Python
LangChain

Multi-agent tutoring system for secondary school students, with one agent per subject and course material written and validated by a team of teachers. It was used with real students at a private school in Spain and at a secondary school in Colombia.

View all projects -->
>_ Available for projects

Do you have an AI project?

Let's talk.

maximofn@gmail.com

Machine Learning and AI specialist. I develop solutions with generative AI, intelligent agents and custom models.

Do you want to watch any talk?

Last talks -->

Do you want to improve with these tips?

Last tips -->

Use this locally

Hugging Face spaces allow us to run models with very simple demos, but what if the demo breaks? Or if the user deletes it? That's why I've created docker containers with some interesting spaces, to be able to use them locally, whatever happens. In fact, if you click on any project view button, it may take you to a space that doesn't work.

Flow edit

Flow edit Flow edit

FLUX.1-RealismLora

FLUX.1-RealismLora FLUX.1-RealismLora
View all containers -->
>_ Available for projects

Do you have an AI project?

Let's talk.

maximofn@gmail.com

Machine Learning and AI specialist. I develop solutions with generative AI, intelligent agents and custom models.

Do you want to train your model with these datasets?

short-jokes-dataset

HuggingFace

Dataset with jokes in English

Use: Fine-tuning text generation models for humor

231K rows 2 columns 45 MB
View on HuggingFace →

opus100

HuggingFace

Dataset with translations from English to Spanish

Use: Training English-Spanish translation models

1M rows 2 columns 210 MB
View on HuggingFace →

netflix_titles

HuggingFace

Dataset with Netflix movies and series

Use: Netflix catalog analysis and recommendation systems

8.8K rows 12 columns 3.5 MB
View on HuggingFace →
View more datasets -->