Services-as-Software

For every dollar of software spend there are six or more dollars of services spend sitting next to it, and AI just made that services budget attackable by startups. The next trillion-dollar company sells the work, not the tool.

The Thesis

Sequoia partner Julien Bek's "Services: The New Software" thesis (2026): the software market is a fraction of the services market. QuickBooks costs ten thousand a year; the accountant who closes the books costs a hundred and twenty thousand. One to twelve. Most verticals run closer to one to six. Every software founder chases the tool budget. The real money is in the labor budget.

AI inverts the economics. A company that sells the outcome (meeting booked, NDA shipped, insurance policy closed) improves every time the model improves - cost of delivery drops, price stays put, margin widens, data moat deepens. A company that sells the tool is in a permanent race against the model and must stay upstream of it forever.

After Automation: Demand Moves To Judgment

Dan Shipper's "After Automation" is the best counterweight to the simplistic "agents replace the team" version of services-as-software. Every automated aggressively across coding, writing, design, support, and email; the company still grew from 4 to almost 30 humans. The mechanism is not sentimentality. Cheaper expert-shaped output increases the number of attempts, drafts, tickets, rewrites, support decisions, proposals, thumbnails, and product ideas that now need a human to frame, judge, route, and turn into a real operating process. Source: Every/Dan Shipper, 2026-05-21

The useful taxonomy is two modes of agent work. Agent employees are delegated actors in Slack or product workflows: support bots, proposal drafters, digest generators, research agents. Agent operating systems are Codex/Claude Code/Cowork-style environments where the human and multiple agents share one workspace. Both modes still need humans, but for different reasons: employee agents need maintenance and ownership; OS-style agents need a human "sandwich" around the task to set the frame, verify the output, and decide the next move. Source: Every/Dan Shipper, 2026-05-21

This is why services-as-software does not remove taste, skill, or management. It makes weak output abundant. Models commoditize the visible residue of old expertise, so default model output becomes easier to produce and easier to ignore. Differentiation moves to what is alive in the present: a specific customer, codebase, deadline, taste standard, risk surface, or blocked project. The human edge is not typing faster; it is knowing what should be asked, what should be rejected, and what should become a durable workflow. Source: Every/Dan Shipper, 2026-05-21

The benchmark lesson is the same. When a model saturates a benchmark frame, the cheap thing becomes attempting that framed work everywhere. If a "senior rewrite" benchmark becomes easy, more people request rewrites; the valuable work shifts to deciding whether to rewrite, what invariants to preserve, what rollback looks like, who reviews it, and whether the migration is worth the blast radius. In Kevin's stack, that means skills, doctors, evals, harnesses, and capsule routing are not optional garnish. They are the human judgment layer made executable. Source: Every/Dan Shipper, 2026-05-21

Copilot vs Autopilot

Two models that look similar but behave completely differently underneath.

The key insight: one model compresses your business, the other compounds it.

The ColdIQ Playbook (Zero to $7M ARR)

Liam Darmody left an $80K operations job at Worldcoin. First client paid $3K/month. Seven million ARR, four hundred B2B clients, thirty-plus people, bootstrapped. The six-step playbook:

1. Pick one outsourced line item inside one industry. Three filters: already outsourced (existing budget line), mostly intelligence work (pattern recognition, not strategic judgment), services spend > software spend.
2. Land first clients yourself. No website, no deck, no funnel. Record every sales call. The objections from the first ten calls become the sales page copy.
3. Do the work by hand and document everything. Resist building the tool. The manual period is the training set. Four artifacts from day one: markdown SOP per task, Loom per cursor-based workflow, decision log per client, failed-campaigns file.
4. Price like a service, report like a product. Sell the outcome. Build dashboards, telemetry, and reports the way a SaaS company would. Upfront setup fee + monthly retainer tied to outcome metric + performance bonus.
5. Replace yourself on delivery before scaling anything else. Hire order: delivery operator → technical automator → head of delivery. No marketer, salesperson, or COO until delivery runs without you. You are the ceiling.
6. Compound the data moat before the software. Save every input (raw + cleaned), every output (tagged with outcome), every reasoning trace from human judgment calls, every client objection and the response that closed it. Eventually agents run delivery while humans run judgment.

Why This Matters for Ideation

When evaluating new product ideas, this framework provides a core filter:

• Is there a services budget 6x+ the software budget? If yes, there's an autopilot opportunity.
• Is the work intelligence-heavy (pattern recognition + rule application)? If yes, AI can attack it.
• Can you run it by hand first? The manual period produces the data moat no pure-SaaS competitor can buy.
• Does model improvement help or hurt you? If you sell outcomes, better models = wider margins. If you sell tools, better models = existential threat.
• What blocked project does this unblock? A buyer rarely pays because an abstract capability exists. They pay when an important project is stuck behind work, tokens, speccing, integration glue, or risk. See Blocked Projects Create Buyers. Source: User, 2026-06-29

This thesis pairs with Agent2Agent (A2A) (Agent-to-Agent protocol) as a current paradigm: A2A defines how agents coordinate; Services-as-Software defines what those agents should be doing - delivering outcomes, not assisting humans with tools.

Skills as Onboarding is the internal operating version of the same thesis. Anthropic's sales-ramp example packages top-rep behavior as an MCP connector plus five Claude skills, so new reps inherit procedure, tool access, and review criteria instead of waiting through a traditional ramp. That is not a SaaS feature in isolation; it is a service workflow compiled into executable memory. Source: X/@jasonlk, 2026-05-23

Long Live Hard SaaS is the counterweight to naive "AI kills software" thinking. Even when code generation gets cheaper, customers still pay vendors to absorb product-time, bugs, integrations, maintenance, and operational risk. Services-as-software expands the market by selling outcomes; hard SaaS persists by removing the maintenance burden for users. Source: raw/notes/saas-bug-moat-slack-thread-2026-06-22.md

The Convergence Point

Bek's long game: judgment turns into intelligence as the dataset grows. Three years of running the work gives you an asset no competitor can bootstrap. The transition from "humans do the work with AI assistance" to "agents run delivery while humans run judgment" happens quietly in the background for years before anyone outside the company notices.

The YC-founder anecdote is a thin but concrete org-design example of that transition: the company reportedly hires only product engineers and runs seven custom AI agents for the non-engineering functions, with a dashboard proving the work exists. Treat it as field evidence for the services-as-software operating shape, not a universal hiring recipe: product engineers still own the work definition, dashboards, integrations, and judgment loops. Source: X/@fin465, 2026-05-18

---

Timeline

• 2026-06-30 | Added Dan Shipper's "After Automation" as the demand-expansion mechanism: agents make expert-shaped work cheap, then increase demand for human framing, judgment, evals, and workflow systems. Source: Every/Dan Shipper, 2026-05-21
• 2026-07-04 | Source-reviewed the "7 custom AI agents" YC-founder anecdote as field evidence for agent-first org design: product engineers still own the system while purpose-built agents carry non-engineering workflows. Source: X/@fin465, 2026-05-18
• 2026-06-29 | Added Kevin's blocked-project buying rule: the practical demand signal is a project already blocked by work, tokens, speccing, integration glue, or risk. Source: User, 2026-06-29
• 2026-06-14 | Referenced in Bit Harmony — Aspects/PBC composition as infrastructure for modular product surfaces (composable delivery vs monolith copies). Source: User, 2026-06-14
• 2026-06-13 | Linked from Build, Don't Buy (build-for-self is the mirror of sell-the-outcome) and Agents as Service Workers (as a Service) (a "service worker" is a worker paid for the outcome it delivers). Source: User, 2026-06-13
• 2026-06-22 | Linked to Long Live Hard SaaS as the "why SaaS still survives" complement: AI may compress implementation, but maintained product correctness and user-friction removal remain valuable. Source: raw/notes/saas-bug-moat-slack-thread-2026-06-22.md
• 2026-05-23 | Anthropic replaced the traditional sales ramp with an MCP connector plus 5 Claude skills per rep (Eleanor Dorfman). Promoted as Skills as Onboarding. Source: X/@jasonlk, 2026-05-23
• 2026-05-22 | Howie Liu's Hyperagent committed $10M ("Founding 500") to back 500 agent-first startups. 7,140 bookmarks. Source: X/@howietl, 2026-05-22
• 2026-05-21 | ClickUp cut headcount 22% citing AI productivity; CEO Zeb Evans says reviewing agent-authored code beats reviewing human code, and ~15 engineers rebuilt the frontend in a week. Follow-up docs link promoted as ClickUp MCP Server, the concrete SaaS integration surface behind the workflow claim. 13,952 bookmarks. Source: X/@DJ_CURFEW, 2026-05-21
• 2026-05-21 | Counter-signal: Every (@danshipper) automated everything with agents yet grew 4 to 30 humans since GPT-3; cheap expert competence raised demand (Jevons effect). Source: X/@danshipper, 2026-05-21
• 2026-05-18 | A YC founder reports hiring only product engineers and running 7 custom AI agents for every other function. Source: X/@fin465, 2026-05-18
• 2026-04-30 | Referenced in Early Business Exploration - margin compounding vs. tool compression as a filter for low-cost, pre-commitment business brainstorms. Source: User, 2026-04-29; wiki cross-ref, 2026-04-30