De-SaaS-ing

Arco's operational discipline of replacing per-user subscription software with API-first, compute-based infrastructure — direct integrations with underlying data and logic layers rather than the human-facing applications built on top of them.

De-SaaS-ing is not a cost-cutting exercise. It is an architectural realignment. The SaaS model was built on a reasonable assumption: that the primary user of software is a human who needs an interface, permissions management, a dashboard, and a support tier. Per-seat pricing exists to serve that human. When the primary operational unit shifts from a human worker to an autonomous agent, that pricing model becomes a structural liability — the business is paying for infrastructure designed for a user it no longer has.De-SaaS-ing eliminates that liability by connecting directly to the data and logic layer rather than the application built on top of it. Where a traditional firm subscribes to a CRM to manage customer data, an Arco business connects directly to the database. Where a traditional firm pays per seat for a workflow tool, an Arco business builds the workflow as an agentic loop with no UI layer required for routine execution. The distinction is not which vendor supplies the capability — it is whether the cost structure is tied to human access or to machine consumption.

First used: March 2026