TheSoftware LensSee engineering differently
Agentic EconomyBy Imtiaz Hassan

The Agentic Economy, Explained

Enterprises will hire AI agents by the task, by the decision, by the signed outcome. This page is the plain-language version of that idea: what it is, the terms that describe it, and where to go deeper.

Why it mattersFor CEOs, CTOs, CIOs and business owners

Your AI spend is about to stop buying seats. In the Agentic Economy, agents hire a piece of work, pay for the outcome and get a signed receipt. This page is the plain-language version of the idea, in five minutes.

Summary
  1. Seats stop making sense. AI agents do not log in. They hire a capability for one job, use it once or a million times, and move on.
  2. Procurement starts to look like staffing. Discover, trial, hire for one job, review the performance, release. The staffing agency is the right picture.
  3. Trust moves from promise to evidence. Every decision leaves a signed receipt both sides can check. Ask any AI vendor for the receipt.
  4. Your systems are the raw material. Anything you already run that can be described, bounded and metered becomes something agents can hire.

Bottom line. Capability, not access, is the new unit of trade.

Below: the full article, for technical teams ↓
Watch the episodeHire the AI Agent | SaaC, the End of SaaSThe Software Lens on YouTube →

"Capability, not access, is the new unit of trade."

What it is

For twenty years software was sold by the seat: a named person, a login, a monthly fee, whether they used it or not. That model assumed the user was a human sitting at a screen.

The main user of software is now, increasingly, an AI agent acting on a person's or a company's behalf. Agents do not sit. They do not log in and browse. They need a piece of work done, they find something that can do it, they use it once or a million times, and they move on. Selling them a seat makes no sense.

So the unit of trade changes. Instead of buying access to an application, you hire a capability: a bounded piece of work, described in a form a machine can read, priced per use, with a signed record of every outcome. I call this SaaC, Software as a Capability, and the economy that forms around it the Agentic Economy. The simplest picture is a staffing agency. You do not buy a contractor; you hire one for a job, measure the work, and release them when the job is done or the work is not good enough.

The two episodes that introduce this are Hire the AI Agent: SaaC, the End of SaaS and SaaS to SaaC Model and the AIM Pattern. The written version is From SaaS to SaaC.

Why it changes business, not just software

Three things move at once. Pricing moves from seats to outcomes: you pay when the work is done, and you can see what you paid for. Procurement starts to look like staffing: discovery, a trial, a contract for one job, a performance review, and a release clause. And trust moves from promise to evidence: instead of a vendor's assurance, every decision the system makes leaves a signed record that both sides can check.

For a company that builds software, this turns every internal system into a potential capability that other companies' agents can hire. Yesterday's IT cost line becomes a revenue line. The companies that work this out first will not be competing with SaaS vendors; they will be the staffing agencies of the Agentic Economy.

Important definitions

Six words carry the whole model.

  • Capability. A piece of work an agent can hire, the way a company hires a contractor for one job. You buy the outcome, not a seat. (From SaaS to SaaC)
  • Manifest. The capability's CV: what it does, what it will never do, what it costs, how well it performs, and who stands behind it. (The Anatomy of a Capability)
  • Hire-token. The contract for one job: who hired the capability, for what purpose, under which rules, in which country.
  • Receipt. The signed timesheet for every single decision: what went in, what came out, which rules were applied, which versions ran, signed by both sides and kept where nobody can edit it.
  • Registry. The agency's book: where capabilities are listed, compared, hired and rated on their track record. (The Four Moats)
  • OLA. The operating level a capability promises in its manifest and is measured against on every receipt. Hire it, measure it, release it if it falls short.

How a hire works

An insurer's claims agent needs a fraud score for one claim. It looks in the registry, finds a capability whose manifest says it scores fraud for insurance claims within declared limits, hires it with a token that states the purpose and the country, sends the claim, receives the score and a signed receipt, and releases the hire. Three hundred milliseconds. Nobody in the room. The receipt goes to an archive. The capability's performance on that call feeds its track record in the registry, which decides whether the next agent hires it.

Multiply that by every task a company does, and by every company, and you have an economy: capabilities as the goods, receipts as the settlement, registries as the market.

What it means for you

If you run a company: your AI spend should buy outcomes with evidence attached, not seats. Ask any vendor for the receipt.

If you run technology: the systems you already have are the raw material. Each one that can be described, bounded, metered and made to emit receipts becomes something agents can hire, inside your company first and outside it later.

If you build software: the product is the capability, the manifest is the shop window, and the track record is the moat. Nobody can buy your two years of signed, measured results.

Go deeper

The Agentic Economy series on this site works through each part in order: the three pillars, the commercial grammar of HIRE, MEASURE and RELEASE, the four moats, regulatory posture, how the EU AI Act is reflected in all of it, and what happens when capabilities compose across industries. The published parts are linked from the box at the top of this page; the rest are coming.

If you prefer to watch, the two episodes are on YouTube: Hire the AI Agent and SaaS to SaaC Model and the AIM Pattern.

← Back to The Software Lens library