From SaaS to SaaC: How We Help Software Companies Sell Capabilities to AI Agents
Your next customer may be software. We help you package and price what you sell so an agent can find it, use it and pay for it.
About this page. Aitina Tech’s R&D wing applies the research of Imtiaz Hassan, published as The Software Lens, in client work and in our own product. This page is the applied view: what the pattern is, how we build it, and what an engagement looks like. The full research is on The Software Lens.
AI agents do not sit in seats. Increasingly they call your product on a customer's behalf, never see your user interface, and skip products they cannot read. SaaC, Software as a Capability, is the delivery model that matches that caller: sell what your software can do, described in a form an agent can read, and charge each time it does it.
From the research
“A usage meter bolted onto SaaS is not enough; agents choose the products they can read, call and trust.”
What we take from it. The product changes before the price list does. We begin with the capabilities a customer would pay for, and the pricing follows from how agents actually call them.
How we apply it
We start with the product, not the pricing. Each thing your software does that a customer would pay for becomes a capability with a machine-readable description, the rules it will not break and a receipt for every call. That is the unit an agent can discover and hire, and it is also the unit you can meter. The user interface stays for the people who want it; it stops being the product.
Then the commercial model follows the technical one: per-use or per-outcome pricing instead of per-seat, usage metrics that mean something when the caller is a machine, and documentation that is executable rather than a PDF. We have done this shift on our own product, so the sequencing (what to expose first, what to keep behind the interface, how to run both models for a period) comes from experience rather than theory. The technical side is our API and MCP development and software architecture work; the commercial side is advisory.
What an engagement looks like
Typically a two-week assessment: which of your features are capabilities in waiting, what an agent would need to read to hire them, what changes in pricing and metrics, and a sequenced plan. Delivery can follow, one capability at a time, alongside the product you already run.
The research behind it
This page is Aitina Tech’s applied account of From SaaS to SaaC: Why the Delivery Model Has to Change, by Imtiaz Hassan, published on The Software Lens. The full argument, the diagrams and the worked examples are there; this page is what we do with it for clients.
Watch the episodeSaaS to SaaC Model | AIM Pattern | The AI Era ShiftThe Software Lens on YouTube →