Skip to main content

Zoho Analytics Bets on Context Before Agents

Three agents illuminate a business network; image by TW with some help from Claude and ChatGPT
Zoho rebuilds Zoho Analytics around an ontology, a semantic layer and a multi-agent Ask Zia. The move lands in a market where everybody, from SAP to Microsoft, now fights over business context.

AI agents without business context are confident guessers. They do not know what "revenue" means in your company, which customer record is the right one, or which supplier belongs to which purchase order. With its new release of Zoho Analytics, Zoho draws the consequence and builds the context first, then the agents on top.

What Zoho announced

On October 28, Zoho announced a major new version of Zoho Analytics. Zoho now calls it an Agentic Analytics platform and positions it as the trusted intelligence layer for businesses. The release rests on four pillars:

  • Trusted data and business context. A new ontology models canonical business entities such as customers, orders and invoices, their relationships and their mapping to source tables. A semantic layer, which Zoho calls a business glossary for AI, standardizes descriptions, synonyms, agent instructions and metric definitions. Zoho states that both are native to Zoho Analytics, require no separate data platform or cloud data warehouse, and are compatible with Apache Ossie, the open semantic standard. More than 30 new connectors, including SAP, join the existing 500-plus.
  • Agentic analytics and actions. Ask Zia becomes a conversational super-agent that orchestrates six prebuilt sub-agents for analysis, data modelling, visualization, data preparation, coding and SQL. Customers choose between Zoho's own LLM and a frontier model on their own key. Custom agents, grounded in the same semantic models, connect to MCP servers and other tools and can trigger workflows. One demo showed an agent creating purchase orders in SAP ERP.
  • Intelligence everywhere. A Zoho Analytics MCP server in remote and local variants, a command line interface and a Claude plug-in make Zoho Analytics usable without its own user interface, which Zoho calls headless BI. Agents can also be embedded, white-labelled, into customers' apps and portals.
  • Governed AI. A data catalog with lineage and impact analysis, AI observability that shows which agents ran, what they accessed and what they cost, and a sandbox with versioning and rollback.

More than 50 further capabilities, from pixel-perfect reports to scenario analysis and Jupyter notebooks, round out the release. Zoho states that more than 100,000 businesses use Zoho Analytics daily and more than 22,000 pay for it directly. Zoho keeps prices unchanged and adds Zoho LLM credits to every plan. The roadmap points to dynamic business context, decision intelligence and, in 2027, a lakehouse for structured and unstructured data.

The bigger picture: everybody wants to own the context

The analytics market agrees on its destination faster than on who will get there. Gartner describes it in its June 2026 Magic Quadrant as a market that "moves toward agentic AI, governed semantics, and AI-augmented decision support." The dashboard does not disappear, but it loses its place at the center: TechTarget sees AI reducing enterprise reliance on reports and dashboards and pushing BI vendors to find a role inside AI workflows.

The semantic layer, once an internal convenience of BI tools, has become AI infrastructure, and ontologies have gone mainstream. SAP put a knowledge graph into Business Data Cloud in early 2025, Microsoft followed with Fabric IQ late that year, and even Dell now targets an enterprise knowledge graph for 2027 (diginomica). Data platforms, BI vendors, application suites and hardware vendors all claim the context layer. diginomica's Jon Reed is not impressed yet: "All of these vendors' context layers are missing important pieces and are incomplete" (diginomica).

SAP is the reference case among application vendors, and its argument is the closest to Zoho's: whoever runs the processes of record knows what the data means. At SAP Connect in October, SAP's knowledge graph spanned more than seven million data fields, half a million tables, 50,000 APIs and 400 data products. Christian Klein called APIs and MCP servers "table stakes" and located the intelligence in the ontology (aheadCRM). SAP also shows the other side of owning the process of record: third-party agents are to come in through SAP's agent gateway, not write back directly. About one vendor's direct write-back demo, Klein said "that demo will never come true" (aheadCRM), in line with SAP's API Policy 4/2026 (aheadCRM).

Three more shifts complete the picture. Openness has become a buying criterion: the Open Semantic Interchange entered the Apache Incubator as Apache Ossie in July, backed by more than 50 organizations. BI goes headless, as Google showed for Looker at Next '26 and Tableau with its new platform; William McKnight described the logic as external agents that "reach in and retrieve trusted numbers" (TechTarget). And platforms squeeze standalone BI: Domo sold its AI and data platform business to Progress Software for $400 million in July (Constellation Research).

Zoho's release maps onto most of these shifts. Some it leaves unaddressed, among them agent-to-agent interoperability, zero-copy data sharing and open table formats, unstructured data as context, master data, and how its agents fit application vendors' fenced APIs.

Where Zoho lands

In my full research note, I measure the release against my September 2024 assessment of Zoho Analytics and against the competition. A few pointers:

  • Zoho closed most of the gaps I identified in 2024, from recommendations to model choice. Paying customers grew at about 9% a year since 2023, which is solid, but not spectacular.
  • On timing, Zoho is in the pack, not ahead of it. Its real difference is structural: it owns many of the applications that generate the data, so a Zoho customer gets context without a data platform project.
  • Openness runs mainly one way for now, the relationship to Zoho's Unified Context Layer is open, and there is an SAP-sized risk in that purchase-order demo.
  • Prices stay unchanged and now include Zoho LLM credits, which keeps Zoho far below Power BI, Tableau and ThoughtSpot per user, but there are caveats buyers should know before they sign.

In short, it’s a move, not a leap. The report explains why, what the ontology tax is, and what Zoho customers, multi-platform enterprises and SAP shops should do now.

You can read and download the full research note here.



 

Labels:

Comments

Post a Comment

Last Year's Top 5 Popular Posts

You are only as good as your customer remembers

As you know, I am very interested in how organizations are using business applications, which problems they do address, and how they review their success. In a next instance of these customer interviews, I had the opportunity to talk with Melissa Gordon , Executive Vice President, Enterprise Solutions at Tidal Basin about their journey with Zoho. You can watch the full interview on YouTube. Tidal Basin is a government contractor that provides various services throughout the government space, including disaster response, technology and financial services, and contact centers. Tidal Basin started with Zoho CRM and was searching for a project management tool in 2019. This was prompted by mainly two drivers. First, employees were asking for tools to help them running their projects. Second, with a focus on organizational growth and bigger projects that involved more people, Tidal Basin wanted to reduce its risk exposure and increase the efficiency of project delivery. This way, the compa...
Post a Comment
Read more

SAP Draws a Perimeter around Agentic AI and What That Means for the Rest of US

The most consequential enterprise AI governance document published this year arrived in late April with surprisingly little fanfare. SAP's updated API Policy, version 4/2026 , is a short document in plain English. The clause that is most interesting is Section 2.2.2. It restricts how autonomous and generative AI systems are permitted to interact with SAP APIs. Read literally, it has the potential to change the architecture of agentic AI projects across every SAP customer landscape. Read carefully, it is also more interesting than the lock-in headlines suggest. The policy targets a specific category of AI behavior, not AI as such. It connects to commercial mechanics that go well beyond API stability. And the literal text, in its current form, will probably not survive the next two policy revisions intact. There is a lot to unpack. I will walk through what the policy actually says, how the SAP-watching community is reading it, what the rest of the major enterprise vendors are doin...
Post a Comment
Read more

The Illusion of Value: Why Salesforce’s Agentic Work Unit is the New "Bad Query" of the AI Era

The News On February. 25, 2026, Salesforce announced a pricing and metrics update . During the company’s Q4 FY2026 earnings call, CEO Marc Benio ff, together with CMO Patrick Stokes , unveiled the Agentic Work Unit (AWU). Positioned as a metric to quantify the labor performed by autonomous digital systems, Salesforce defines an AWU as one discrete task accomplished by an AI agent. According to Salesforce, this discrete task represents the exact moment " raw intelligence is converted into real work ". It is not a fixed unit but measured as a processed prompt, a completed reasoning chain, or an invoked tool. Salesforce explicitly designed the AWU to move the industry conversation away from the raw consumption of Large Language Model (LLM) tokens. As Benioff noted, tokens only measure "how much an AI talks," whereas the AWU is intended to measure actual business execution. The scale of this rollout is massive. Salesforce reported that its platform has already processe...
Post a Comment
Read more

LLM Showdown: Comparing ChatGPT, Gemini, and Grok for Automated News Research

The analyst’s day is full of research. Now, this is the age of AI and AI is here to help, isn’t it? As everyone is talking about copilots and AI agents, why not using the tools at hand to do a little research on research. NB., no one really has a good definition of an AI agent, so this might become an additional topic for research. But I digress. Imagine the following project at hand, which is not only interesting for analysts, btw, but also for a variety of roles in the corporate world. Let’s call it vendor (competitor) monitoring. The job is the following: Research reputable sites for news about a number of vendors, relating to a set of keywords. Reputable sites are high quality news sites, high quality tech publications, high quality analyst sites and, of course the news pages of the vendors in question. Limit the time frame of the search matching to the cadence of my information requirement, e.g., “yesterday” for a daily update or “last week” for a weekly update. Provide a summary ...
Post a Comment
Read more

The CDP is dead – long live the CDP!

In the past few years, I have written about CDPs, what they are and what their value is – or rather can be. My definition of a CDP that I laid out in one of my column articles on CustomerThink is:  A Customer Data Platform is a software that creates persistent, unified customer records that enable business processes that have the customers’ interests and objectives in mind. It is a good thing that CDPs evolved from its origins of being a packaged software owned by marketers, serving marketers. Having looked at CDP’s as a band aid that fixes the proliferation of data silos that emerged for a number of reasons, I have ultimately come to the conclusion and am here to say that the customer data platform as an entity is increasingly becoming irrelevant – or in the typical marketing hyperbole – dead.  Why is that? There are mainly four reasons for it.  For one, many an application has its own CDP variant already embedded as part of enabling its core functionality. Any engageme...
Post a Comment
Read more