Enterprise software: written once, runs for years. That is ending. Instead it will be assembled.
Enterprise software used to be written once and run for years. That is ending for a specific class of applications, and most of what is written about vertical versus horizontal AI misses why.
Most of the writing so far treats this as a menu choice. Pick a vertical AI vendor that knows your industry, or a horizontal one that knows every industry a little, or blend both inside the software you already run. Gartner’s own numbers back that framing. Up to 40 percent of enterprise apps will carry a task specific agent by 2026, up from under 5 percent in 2025. That is agents bolted onto software already built the old way. Not the interesting part of the story.
The interesting part is what a vertical AI layer paired with a horizontal workflow engine actually replaces. The build itself.
Think of a commercial kitchen. The chef’s judgment, what makes a good sauce, when a piece of fish is done, does not change from one night to the next. What changes is the line, which ticket comes first, which station picks it up, who plates it, how it reaches the table. A restaurant does not rebuild its kitchen every time the menu changes. It keeps the line and swaps the recipes.
That is the split now available to enterprises. A vertical GenAI layer supplies the judgment, the domain rules, the read on a contract clause or a claim file or a customer complaint. A horizontal workflow engine supplies the line, routing that judgment across the systems that need to act on it, and logging every step so someone can check the work later. Commission those separately from a dev team, the old way, and you are back to an 18 month build. Assemble them, and you are running the process by next quarter.
Three things make this a real shift, not another AI headline.
First, the vertical layer is already running full processes end to end for named customers, not just chatting. Sierra, built for customer service, crossed 100 million dollars in annual recurring revenue seven quarters after launch, reached roughly 200 million dollars in ARR by May 2026, and now counts more than 40 percent of the Fortune 50 as customers. Harvey, built for legal work, has more than 25,000 custom agents running document review, due diligence, and contract drafting across 1,300 organizations, and crossed roughly 300 million dollars in ARR by June 2026. Enterprises are not paying for smarter software. They are paying per resolved ticket, per reviewed contract. That only works if the work is done end to end, not drafted and handed to a person to finish.
Second, this shows up first where the process is manual, judgment heavy, and margin pressured, which is exactly the BPO industry’s profile. Concentrix closed almost 100 deals for its agentic product line last quarter and expects to cross 120 million dollars in annual recurring revenue from it this fiscal year. TTEC now describes its own business in terms of outcomes delivered for clients, not seats staffed. Two public companies are booking real revenue against this pattern already, not a pilot buried in a slide.
Third, and this is the one most coverage skips, the combination changes who gets asked to build something in the first place. A claims team that used to file a ticket with IT for a bespoke intake tool now assembles a workflow instead. The judgment stays with the vertical layer. The routing and the audit trail sit with the horizontal engine. Nobody writes a requirements document and waits for a release.
None of this means the technology is settled. Gartner’s own research also predicts that over 40 percent of agentic AI projects will be canceled by the end of 2027, and counts only about 130 of the thousands of vendors calling themselves agentic as having the capability to back the claim. The rest have rebranded a chatbot or an old rules engine. That is a real number. It deserves an answer, not a dismissal.
The answer is not a smarter judgment model. Most canceled projects fail because nobody can say afterward why the agent did what it did, which is a governance problem, not an intelligence problem. A workflow engine that logs every step, every decision, every handoff, and can show that log to an auditor or a regulator, is what turns a black box pilot into something a bank or an insurer will actually run in production. The projects getting canceled skipped that layer. They did not get the judgment wrong.
So the real decision in front of a CIO or a COO is not which AI vendor to shortlist. It is whether the next process on the list, the one currently run by hand or by software commissioned three years ago, still needs to be built at all, or whether it can be assembled from a judgment layer and an execution layer that already exist.
Pick one process in your organization that fits that description, manual, judgment heavy, expensive to keep rebuilding every time the rules change. Name it. That is the only menu that matters this quarter, not another vendor comparison.
