What's this about?
Thariq's provocation: take your existing SaaS product, make it headless, let agents use it directly, and charge per interaction — especially for enterprise customers. His point is that most SaaS companies already have everything needed and simply haven't shipped the interface agents want.
What exactly does "headless" mean?
A normal SaaS product is a website — the interface is the product. Headless means exposing the underlying capability through an API with no UI attached, so something other than a human can drive it. Agents currently interact with such products badly: they either drive the web interface by simulated clicking, which is slow and brittle, or they use an API built for developers writing integrations, not for an agent working autonomously. The gap Thariq is pointing at is a deliberate agent-facing surface, priced per interaction rather than per seat.
Why is this worth noticing?
- The per-seat pricing problem is the real content. If agents do the work, seat-based pricing collapses — you don't buy a seat per agent. Per-interaction pricing is the obvious replacement, and vendors who move first set the norm.
- It connects to the week's MCP data. State-modifying tools rose from 27% to 65% of tool use, meaning agents are already acting on external systems — mostly through interfaces nobody designed for them.
- The obvious objection goes unaddressed. A headless product loses the interface where most SaaS companies do their upselling, retention and brand-building, which may be exactly why nobody's pressing the button.