メインコンテンツに戻る

Your AI agents are only as smart as your business data

Dashboards grounded the last decade of human decisions. Headless business intelligence will ground the next decade of agentic decisions.


Zuye Zheng headshot

Zuye Zheng

Chief Data Architect at Zendesk

更新日 2026年10月18日

Graphic with text building intelligence for AI

Business intelligence was built to help people turn data into decisions. Dashboards gave teams a way to explore performance, investigate problems, and decide what to do next. But important analytical questions may soon never be asked by a person. 

AI agents ask questions. They investigate problems, validate their reasoning, and use those answers to guide their actions.

Like people, AI needs its decisions grounded in evidence. Businesses invested in analytics because important decisions should be based on facts rather than intuition. As AI takes on more responsibility, that same principle applies. Preventing hallucinations is no longer just about generating better answers. It's about ensuring the decisions and actions AI takes are grounded in the right information.

Today, that grounding often comes from unstructured knowledge. AI agents search help center articles, internal documentation, conversation history, or the web to retrieve the facts they need before responding. 

Preventing hallucinations is no longer just about generating better answers. It's about ensuring the decisions and actions AI takes are grounded in the right information.

The next frontier of agentic intelligence 

The tables that power dashboards contain what NVIDIA CEO Jensen Huang has described as the “ground truth of business”. They explain how an organization operates: how performance is measured, where work is happening, how customers behave, and how AI agents themselves are performing.

Giving AI access to that data is only the first step. Preparing structured data for an agentic workforce requires making it searchable and the meaning behind that data explicit, so AI can ask better questions, reach reliable conclusions by finding the right data, and confidently ground its actions in the answers.

Why structured data needs context

Business data rarely explains itself. A help center article usually contains both the information and its meaning. If it says "customers have 30 days to return an item," an AI agent can use that information directly.

Structured data works differently. A dashboard might report an average resolution time of 71 minutes, but the number alone says very little. Is it good or bad? Is it typical for Mondays? Has the definition of resolution time changed? Does it apply to every support channel?

People naturally bring this context with them. They understand how metrics are defined, which comparisons matter, and what the business considers normal. AI needs that same understanding made explicit.

Like humans, LLMs also struggle to retain precise knowledge over time. During pretraining, exact facts are compressed across trillions of tokens rather than stored for direct retrieval. As researchers behind DeepSeek's recent architecture paper observed, "transformers lack a native primitive for knowledge lookup, forcing them to inefficiently simulate retrieval through computation."

This is why context engineering has become so important. Techniques like retrieval-augmented generation (RAG) provide AI with the specific business context it needs at the moment a decision is made, reducing hallucinations by grounding responses in reliable information rather than relying solely on model memory.

The same principle applies to structured business data. AI needs access to a database along with the business context that explains how data was generated, how metrics are defined, what relationships exist between datasets, and how the organization interprets performance.

Recent research from Anthropic illustrates just how important this context is. Simply giving an AI agent access to structured business data resulted in just 21% accuracy on the company's internal analytics evaluations. Anthropic found the biggest improvements came from adding business context through governed semantic layers, curated skills, and maintained documentation, lifting accuracy to more than 95%. Anthropic also found that this knowledge needs continual maintenance. As businesses evolve, metric definitions change, new data sources are introduced, and workflows adapt. Without keeping that knowledge current, accuracy declined significantly over time.

OpenAI reached a similar conclusion when developing its in-house data agent. Success depended on curated business context created by domain experts—capturing intent, semantics, business meaning, and known caveats that couldn't be inferred from the data alone.

The implementation will differ across organizations. It might take the form of skills, semantic layers, context engineering, or self-improving memories. The underlying principle is the same: AI needs more than access to business data. It needs the meaning behind that data.

The future of business intelligence

We need a different way of thinking about business intelligence. Dashboards remain essential for people, but AI needs business intelligence that's available wherever decisions happen. Structured data, semantic context, and institutional knowledge all need to become machine-readable so AI can reason over them reliably.

This is the shift toward headless business intelligence. Preparing for that future means making the meaning behind your business data as accessible as the data itself, so both people and AI can make decisions with confidence.

Dashboards made business data useful to people. Headless business intelligence will make it actionable for AI.

Zuye Zheng headshot

Zuye Zheng

Chief Data Architect at Zendesk

Zuye leads Agentic Analytics and Zendesk’s new Data Platform. He’s shaping how people and AI work with data and take action on it, starting with the information in Zendesk. Before joining Zendesk, he co-founded HyperArc and led analytics at Salesforce and Tableau, where he helped launch Salesforce Reports and Einstein Analytics. When he’s not joining data, he likes joining wood—and hopes to spend more time doing it post-ASI.