WHITEBOXX / GUIDE

Services as software:
what it means for enterprise buyers.

Services as software describes companies that sell the result of work, delivered mostly by software and AI agents, instead of a tool your staff must operate. This guide explains the idea, where it came from and how to judge a vendor that uses it.

By Aman Khanna · Published · Updated

What is services as software?

Services as software is a business model in which a company delivers work that used to be bought as a service, such as research, reporting or claims handling, mainly through software and AI agents. The buyer pays for the work done, not for seats in a tool.

Traditional SaaS sells the tool, and your staff still do the work inside it. Traditional services sell people’s time. Services as software sits between the two. Software does most of the work, and people check results, handle exceptions and adapt the system to the customer.

Where the term comes from.

Foundation Capital popularised the phrase “service-as-software” in 2024. It argued that AI would let software companies compete for spending that had gone to service firms. In March 2026, Sequoia partner Julien Bek published “Services: The New Software”. He argued that companies spend about six dollars on services for every dollar on software, and that the next very large companies would sell the work rather than the tool.

HFS Research uses the term for the way IT and business services firms are rebuilding their offers around AI. All three share one idea: the budget at stake is the services budget, which is much larger than the software budget.

THREE MODELS

SaaS, services and services as software compared.

THREE MODELS
SaaSServicesServices as software
What you buyAccess to a toolPeople’s timeThe work, done mostly by software
Who does the workYour staffThe provider’s staffAI agents and software, checked by people
How it is pricedPer seat or by usageDay rates or retainersPer task, per outcome, or a subscription and project fee
Fit to your processYou adapt to the toolFully adaptedAdapted, within what the system supports
What grows as you growSeatsHeadcountRuns of the same system

Why it is happening now.

AI agents can now complete defined pieces of knowledge work, such as gathering data, running an analysis or drafting a report, with a person reviewing the result. Work that used to need an analyst’s time can be delivered at closer to software cost.

Buyers are also questioning per-seat pricing. If an agent does work that five people did inside a tool, the vendor sells fewer seats. Vendors are responding by charging for usage, for outcomes, or for a mix of subscription and project fees.

The risk: a services firm in disguise.

Some providers call themselves services as software but deliver mostly with people. That is not wrong, but it costs more as you grow and is harder to keep consistent. Investors call this the services trap. If every new customer needs new custom code, twice the customers need twice the engineers.

Ask the provider what share of the work the software does, what is reused from one customer to the next and how their cost per customer has changed over time.

BEFORE YOU BUY

Questions to ask a services-as-software vendor.

  1. 01

    What exactly do I pay for?

    A task, an outcome, a subscription, a project, or a mix. Ask for a worked example with real numbers.

  2. 02

    What does the software do, and what do people do?

    Ask to see one run, from input to result, with the human steps marked.

  3. 03

    How do I check a result?

    You should be able to see the sources, calculations and steps behind each result.

  4. 04

    What happens when my process changes?

    Find out who changes the system, how long it takes and what it costs.

  5. 05

    What do I own at the end?

    Code, configuration, data and outputs. Put it in the contract.

Where Whiteboxx fits.

Whiteboxx sells a platform and the engineering to extend it. Evidence OS does the repeatable work: retrieving data from 562 sources, running execution agents and recording each run. Our forward deployed engineers extend it for each customer’s process.

You pay a subscription for the platform and a scoped fee for the extension. The parts we build for one customer, such as a data connection or a workflow step, are designed so the next project can reuse them.

See how pricing works