"It works, don't touch it" - Gartner's SaaS-is-over thesis and the new dangerous sentence in tech

In plain terms

Two headlines, one theme. Gartner published a note declaring the "end of SaaS" (ITmedia): the argument is that "which UI is easiest to use" as a selection criterion is dead, because increasingly no human touches the UI - an agent does. Separately, an essay circulating widely this week argues that "it works, don't touch it" is now the most dangerous sentence in tech - because legacy systems that resist modernization become the exact bottleneck agentic AI cannot bypass.

Both are the same argument told from opposite ends of the org.

What's changing

Gartner's "end of SaaS" is aggressive framing but points at a real shift. The vendor pitch for the last 15 years was: cleaner UX, faster onboarding, mobile-first. If the buyer becomes an autonomous agent orchestrating tasks across a stack of tools, then:

• APIs matter more than UIs. Products with strong, permissioned APIs win; products with pretty UIs and weak automation surfaces lose.
• Data models matter more than screens. An agent reading a well-modeled entity graph outperforms an agent parsing HTML.
• Pricing per seat becomes untenable. If one agent operates on behalf of a whole team, the seat-based SaaS moat evaporates.

The "don't touch it" essay is the inverse: legacy systems that were "good enough" in a human-interaction world become actively hostile in an agent-interaction world. Every undocumented workaround, every silent side-effect, every "the system won't let you do X but Sarah in Accounting knows the trick" - none of that transfers to an agent.

Under the hood

What "agent-ready" architecture actually requires:

• First-class API for every operation the UI exposes (still shockingly rare)
• Entity models with stable identifiers (versus screen-scraped state)
• Deterministic side-effects (agents can't reason about "sometimes this button also triggers an email")
• Explicit permission scopes for non-human principals (agents need OAuth-shaped identities that don't map cleanly onto today's IAM)
• Idempotent write endpoints (agents will retry; your API needs to handle it without duplicating orders)

So what

For decision-makers: the "SaaS is dead" claim is exaggerated but the direction is real. Any purchase decision in 2026 should score vendors on API completeness before UI polish. For builders: refactoring for agent-readiness is the highest-leverage modernization work of the next 24 months. Legacy systems where "it works, don't touch it" prevails will be the ones that agents route around - and that's how the vendor becomes irrelevant without a single lost customer signaling it.