Vertical SaaS platforms are built for industry specific workflows — how one industry actually gets things done, sequencing and exceptions included. Their edge is a deep understanding of industry rules and workflows that took years to build, but AI is requiring a redesign of the Vertical SaaS model.
Four pressures, at once
The screen. Agents want the data, not the interface — and the SaaS roadmap is painfully adding onto a UI that an NLP interface could serve directly.
The use cases. Features product teams once ignored, or that needed custom workflows, are now within reach of AI plus automation.
The delivery model. Software can ship faster but LLM vendors and SIs are prototyping similar features for enterprise buyers.
Build vs. buy. Buyers are testing hosted and sovereign AI, and rethinking build vs. buy to avoid lock-in.
Fig. 01 — Four independent pressures converging on the incumbent at once.
What it is
Not an architecture. A go-to-market, a product, a customer-success model, a governance model, and an ecosystem play.
Solving the four pressures above takes more than a chat window and an MCP server bolted onto your data.
Turning on MCP makes your data reachable by somebody else’s agent. That’s useful — but what an outside agent can actually do with read access is limited: look something up, summarise it, compare it, run a what-if, write up what it found. Detect, suggest, simulate. Real value, and also the ceiling.
Detect→Suggest→Simulate
reading data
→
Escalate→Commit→Enforce→Verify
changing things
Becoming the system your customers actually run the business on means going further — pulling the right playbook for the situation, deciding what to do, doing it, and checking that it worked.
00 · Qualification gate
Run before pillar 01. VAO isn’t the right fit for every SaaS company, or for every use case inside one that qualifies. Rule out three things first:
Horizontal SaaS. This is built around industry-specific workflows, not general-purpose tools.
Use cases where every expert already agrees on the right call. If competent people, given the same inputs, land on the same answer every time, that's a calculation — not a decision an agent needs to make.
Use cases where all you actually need is a query and a report. Looking things up and summarising them is real value. It isn't a system of action.
What’s left is the target: a decision that recurs, on data the system already holds, where good judgement can reasonably go more than one way — and where someone needs a system of action not just a system of record.
What the buyer wants the product to do: answer, decide, or act
Defining limitations and identifying non-covered use cases
Understanding where value compounds for Vertical SaaS once models and connectors are commodities
Mapping and scoring use cases to either Agentic Orchestration (drawing on the qualitative decisioning of agents) or Optimisation (calculation of a cost-effective solution based on predictions)
Defining VAO's coverage across a portfolio of AI agents, models, studio including schedulers and builders
Sizing the pricing and value of agentic products and Solution Consulting Methodology: what products are deployed, and what strategies are learned from humans and taught to agents