Techaisle Analyst Insights

Semantic layers are not new. Large enterprises have spent the past decade building them inside data warehouse programs, staffed by data engineers and funded as multi-year projects. What has been missing is a version that a 400-employee manufacturer with a two-person BI team can stand up and maintain. Zoho is going after exactly that buyer with the October 28 release of Zoho Analytics, and the midmarket is the right lens for judging it.

Zoho is repositioning Zoho Analytics, used daily by 100,000 businesses, as an agentic analytics platform built on native semantic and ontology layers, a multi-agent Ask Zia, headless access through MCP, and governance designed for agents. Early commentary has centered on whether business context makes AI agents more reliable. It does, and Techaisle has long held that you cannot sell AI without data. For SMB and midmarket firms, the more consequential question is who could afford that context before this release, and the answer is very few.

The midmarket has been priced out of trusted AI

Core midmarket firms (100 to 999 employees) carry enterprise-style data complexity: an ERP, a CRM, an e-commerce platform, a payments provider and, after an acquisition or two, a second ERP. They rarely carry an enterprise-style data team. When these firms put an AI assistant on top of their data, it answers from raw tables, and two departments asking the same question get two different numbers. Pilots impress in the demo and stall in production; the condition Techaisle calls Pilot Purgatory.

Most commentary on the Surface Laptop Ultra and the first wave of RTX Spark PCs from ASUS, Dell, HP, Lenovo, and MSI has focused on the machine. Is it a MacBook Pro rival? How long does the battery last? Can it game? Those are fair questions for a reviewer and the wrong questions for anyone deciding where AI spending goes over the next 3 years.

My view is that the October 7 launch is 3 bets packaged as 1 device. Microsoft and NVIDIA are betting that AI cost will migrate from a metered cloud bill to an owned asset on the desk, that the governance of autonomous agents belongs inside the operating system, and that the developer's laptop decides where production AI eventually runs. The hardware earns the headlines, but the bets will decide whether this category lasts, and each one carries different consequences for buyers, channel partners, and the two companies' rivals.

What was actually launched

RTX Spark pairs a 20-core Grace Arm CPU with a Blackwell GPU carrying 6,144 CUDA cores, sharing up to 128GB of unified memory and rated at up to 1 petaflop of FP4 compute. The Surface Laptop Ultra starts at $2,599 and the Surface RTX Spark Dev Box at $5,999, with OEM laptops shipping from October 16. Alongside the silicon, Microsoft made Microsoft Execution Containers (MXC) generally available in Windows 11. MXC is a policy layer that defines which files and network destinations an agent can reach, and the operating system enforces those limits rather than the agent itself. GitHub Copilot, OpenAI Codex, OpenClaw, Replit and LM Studio already support it.

That paragraph of plain facts is where the real story sits.

Bet 1: Turning a metered bill into an owned asset

Google's Gemini at Work announcements put one agent, called Gemini, behind every surface a company uses. The agent is meant to be given an outcome rather than instructions, and to return finished work, running across a company's tools and systems for hours or days when the job needs it. Google also separated the agent from the model running underneath, so Gemini can hand a step to Anthropic's Claude when Claude is better suited, with other private and open models to follow. Google is competing on identity, policy, memory, and cost control, and treating the model as a part it is prepared to source from a rival.

For firms with 1 to 10,000 employees, the market Techaisle tracks, model quality is rarely what holds agents back. The harder questions are whether agents stay affordable once usage scales, whether the CISO will let them run, and who will operate them, and Google's launch speaks to those more directly than its enterprise customer stories suggest.

Lock-in moves from the model to the context

Model leadership changes hands several times a year, and few customers want to rebuild their agents each time it does. Gemini's model choice addresses that risk: the agent picks the model for each step, today from Google's own Gemini family or Anthropic's Claude, with other models to follow. Google owns one of the best model families and still built Gemini so customers can choose another. That is a confident bet on the agent, and it works because the switching cost has moved to what the agent knows.

Google is connecting Gemini to its Knowledge Catalog, an existing Google Cloud service, so that every agent works from the company's own business definitions. The catalog holds one agreed definition for each business term and reads metrics from the systems where the company already maintains them. Gemini's memory runs from the task at hand to a record of how the organization does its work, and the agent writes some of its own skills as it goes. After a year of use, that body of definitions, history, and skills is far harder to move than a model is to swap.

Every wave of automation reaches a point where the limiting factor shifts from what the machine can do to how much human attention it consumes. Mainframes reached it with operators; data centers with administrators; the cloud with the engineers who once managed fleets of servers by hand. Each time, the breakthrough came from moving the knowledge of what to do next out of a person's head and into a system that could carry it.

AI agents have now reached that point. An agent can competently write code, reconcile an invoice, or triage a support ticket. Yet, the work around the task still falls to a person: deciding the next step, remembering what was agreed an hour ago, insisting on a review, sending the findings back for a fix. Anyone who has worked alongside a coding agent all day knows the pattern. The output arrives quickly, and the human spends the day steering it.

That supervision cost rarely appears in a business case, and it quietly decides whether agentic AI scales. Techaisle data shows 59% of midmarket firms now prioritize agentic AI in their budgets, and AI-driven algorithmic decision-making has doubled to 20%. Leading-edge midmarket firms running custom agentic ecosystems have reached 144 agents for every employee, and small businesses 59. At that density, an agent that needs a human prompt every few minutes stops being leverage, and the human becomes the bottleneck the agents were meant to remove. Kiro workflows, introduced by AWS on September 30, are one of the first serious attempts to engineer that supervision cost out of the product. They are worth studying for what they reveal about where agentic AI is heading.