BI Strategy · October 2026

The BI Disruption —
The Wave Worth Catching

Traditional BI tools are being disassembled into three separate concerns — extraction, semantic foundation, and rendering. The 12–18 month window to own this transition is now.

Every client on Databricks or Fabric is sitting at this intersection right now
§1 — The Setup

Two disruptions. One intersection.

This isn't one market shift. It's two happening simultaneously — and where they cross is the opportunity.

The Convergence Argument

Agentic data engineering is the synthesis of two simultaneous disruptions — not one. Understanding both is what makes the methodology argument commercially precise rather than generic AI hype.

Disruption 1 — DE Workflows
2023–24: AI-assisted DE — LLMs writing SQL, dbt models, documentation. Human still in the loop.
2025→: Agentic DE — agents autonomously orchestrating, repairing, and adapting pipelines without human steering.
Disruption 2 — BI Consumption
2025–26: The output contract for data engineers has changed. Data is no longer built for dashboards — it is built for AI-native interfaces (Genie, Claude Dashboards, Cortex Analyst). AI-available ≠ AI-consumable.
Enabling Force — Semantic Infra
2025–26: Semantic layers are becoming cloud defaults — Unity Catalog, Snowflake Horizon, Fabric Semantic Models. The substrate exists. The practice that makes it your semantic layer — not the platform's generic one — is what's missing.

The implication: Every client on Databricks or Fabric is sitting at this intersection — agentic DE arriving from above, BI disruption arriving from below. The engineering discipline that connects them is CE + IE. That is your white space.

8%
of new enterprise reports use GenAI today (Gartner 2026)
The acceleration is ahead, not behind.
60%
of self-service analytics users will use LLMs for ad hoc analysis by 2028 (Gartner)
90min
for a telecom to surface more insights via vibe analytics than they generate in 90 days (MIT Sloan)

§2 — The Architecture

BI is splitting into three layers

The tools that bundled extraction, semantic logic, and rendering together for 20 years are losing that advantage. Each layer is now a separate market — and Impetus plays across all three.

Layer 1 — Extraction
Unlock KPIs from Legacy Reports
Impetus · Entry Point

Business logic buried inside Cognos Framework Manager, SAP BO Universes, Tableau calculated fields, and MicroStrategy metrics — extracted by AI reader agents, mapped to a unified business glossary, lineage reconstructed, formulas documented. The KPI inventory that makes Layer 2 possible.

Cognos SAP BusinessObjects Tableau MicroStrategy AI Reader/Writer Agents
↓ KPIs and business logic land here
★ Layer 2 — Semantic Foundation
Governed Metric Definitions — Defined Once, Served Everywhere
★ Impetus Anchor

KPIs unlocked in Layer 1 land here — defined once in YAML or MetricFlow as revenue, churn, risk exposure, regulatory capital — and served to any renderer via REST, GraphQL, or MCP. The semantic layer is the durable asset. Metric governance is ongoing, not a one-time project. This is where the client relationship deepens.

Context Engineering applies here

CE encodes not just what a KPI is, but what it means to the business — units, grain, filters, edge cases, business calendar rules. IE adds intent: when an agent should trust a metric, when to escalate, what stop rules apply. Without CE + IE at this layer, NL-to-SQL produces confident wrong answers on real enterprise estates.

dbt MetricFlow Databricks Metric Views Snowflake Semantic Views OSI / Apache Ossie (emerging)
↓ same foundation powers both outputs
Layer 3 — Rendering
Two output lanes. One foundation.
The BI tool is now just a rendering surface. Swap it without touching the semantic layer.
Impetus · Proof Point
Conversational BI
Ask. Get an answer.

Natural language interfaces for executives and ad hoc analytics. No dashboard, no analyst in the middle. Prompt → visualisation → insight.

Claude Dashboards Databricks Genie Cortex Analyst Fabric Copilot Looker Agents
Governed Render
Pixel-perfect. Auditable.

Regulated reporting — BCBS 239, COREP, SOX, IFRS — stays as controlled, certified output. Same semantic foundation underneath. Governance and auditability intact.

Regulatory Reports Executive Scorecards Customer Embedded Audit-ready Output
The Impetus Play — Across All Three Layers
Layer 1 · Entry Point
Unlock the KPIs

Extract buried business logic from Cognos, SAP BO, Tableau, MicroStrategy. Build the KPI inventory. Create the asset that makes everything else possible.

★ Layer 2 · Anchor
Govern the Semantic Foundation

CE + IE methodology applied. Metrics defined once, served to any renderer. Durable client relationship — metric governance is ongoing, not a project. This is where IP lives.

Layer 3 · Proof Point
Prove Both Output Lanes

Wire conversational BI and governed regulated output from one foundation. Business case is visible here. The client sees the value before the project ends.

The Critical Constraint

BI development is not being eliminated — it's being redirected: from building dashboards to building semantic models that AI surfaces automatically. An enterprise that deployed AI analytics without a governed semantic layer saw adoption collapse to 12% in six months as conflicting metric definitions destroyed user trust. The semantic layer is the most valuable BI investment of the next three years.


§3 — What's Live Now

AI BI tools in production today

This is no longer a roadmap conversation. Clients are being pitched these tools right now.

Claude Dashboards
Anthropic · Beta Oct 9, 2026

MCP-connected live dashboards from natural language. Sources: Databricks, Snowflake, BigQuery, Salesforce, Amazon Redshift, ClickHouse. Can export to BI tools. Governance flagged as a concern for enterprise production use.

Databricks AI/BI Genie
Databricks · GA 2026

Chat + dashboard + NL query, fully integrated. Powered by Databricks Metric Views (GA 2026) and Genie Ontology. Agents can now monitor metrics and trigger downstream actions.

Snowflake Cortex Analyst
Snowflake · GA 2026

NL-to-SQL grounded in YAML Semantic Views (GA 2026). Internal benchmark: >90% SQL accuracy with a governed semantic model. Without it: similar low accuracy as any raw NL-to-SQL approach.

Looker BI Agents
Google · Next '26 · April 2026

Grounded in LookML semantic layer. Native MCP server for agent access. Agentic Workflows that monitor metrics and surface recommendations autonomously. Published to Gemini Enterprise.

ThoughtSpot Spotter Semantics
ThoughtSpot · March 2026

Dedicated semantic layer with deterministic reasoning, aggregate awareness, and governed business definitions. ThoughtSpot now positions itself as an "Agentic Analytics Platform."

Copilot in Microsoft Fabric
Microsoft · Generally Available

"A report author you collaborate with." Deep integration with Power BI semantic models. Generates DAX, builds visuals, explains measures. Strongest in Microsoft-stack enterprises.

Vendor Moves — 2026
January 2026
dbt Labs, Snowflake, Salesforce/Tableau

Launch OSI (Apache Ossie) — open standard for portable semantic layer definitions. First version of the specification published. No product ships native import/export yet.

March 2026
ThoughtSpot

Spotter Semantics launched — deterministic reasoning layer, aggregate awareness, governed definitions. Platform rebranded as "Agentic Analytics."

April 2026 — Google Next '26
Google / Looker

Looker BI Agents with native MCP server. Agentic Workflows monitoring metrics autonomously. Agents draw from up to 5 explores simultaneously, published to Gemini Enterprise.

2026 — GA
Databricks + Snowflake

Databricks Metric Views and Snowflake Semantic Views both reach General Availability. Warehouse-native semantic layers are now production-grade — but not portable between platforms.

October 9, 2026
Anthropic

Claude Dashboards public beta. MCP-native, connects to Databricks, Snowflake, BigQuery, Salesforce, Redshift, ClickHouse. Generates live, interactive dashboards from natural language.


§4 — The New Interaction Paradigm

Vibe Analytics

The term is new. The pattern is accelerating.

"Vibe Analytics" — MIT Sloan / Michael Schrage

Coined by MIT Sloan's Michael Schrage (MIT Sloan Management Review, 2025). The core idea: eliminate the traditional translation layer between business questions and technical analysis. The user describes what they want to an LLM — the tool builds the visualisation, exploration, or app. No SQL. No analyst queue. No waiting three days for the wrong chart.

It's the analytics version of vibe coding: the user's intent becomes the interface.

"A Southeast Asian telecom surfaced more financially relevant insights in 90 minutes than it typically generates in 90 days."

MIT Sloan Management Review, 2026

"MCP tools gave agents a standard way to discover schemas and run queries — vibe analytics as MCP-native analytics."

MotherDuck / Vercel framing, 2026
Why Vibe Analytics Needs the Semantic Layer

Most vibe analytics demos work on a clean star schema with five tables. Enterprise estates have 50,000 tables, three conflicting definitions of "revenue," and a semantic layer nobody has maintained since 2019. A governed semantic model is the only thing that makes Genie, Cortex Analyst, and Fabric Copilot safe to put in front of an executive. Almost none are. That is the entry point.


§5 — The Market Split

What survives. What's new. What's gone.

Gartner's 2026 Market Guide draws a clear line: not all of BI is going conversational.

The Gartner Bifurcation (Market Guide, 2026)
"By 2028, 60% of self-service analytics users will use general-purpose LLMs for ad hoc analysis, while production reporting stays on traditional BI platforms." — Gartner via ThoughtSpot Market Guide
✓
Survives: Certified dashboards — executive scorecards, regulated reporting (BCBS 239, SOX, IFRS), customer-embedded analytics. Governance and auditability requirements demand a controlled definition layer. These don't go away. They get a better foundation.
★
New category: AI-generated ephemeral dashboards — vibe analytics, MCP-native, conversational. Claude Dashboards is the first entrant. ThoughtSpot Spotter and Looker Agents are the established-vendor plays. This is where the growth is.
✗
Being replaced: Ad hoc Power BI / Tableau / Looker report building. Business users asking one-off questions will go to NL interfaces, not open a report editor. The "build me a dashboard" request is going away. The "what's happening with X" question is going to an agent.

★ §6 — WHERE WE PLAY

Semantic BI Modernisation —
not report migration

Most vendors offer an as-is tool swap — move the dashboards from Tableau to Power BI, same problem, new invoice. The opportunity is the semantic modernisation play: extract the KPIs, govern the foundation, and serve both output lanes from it.

Dimension As-Is Migration (tool swap) ★ Semantic BI Modernisation
What moves Reports, pixel for pixel KPIs, business logic, metric definitions
Output Same reports in a new tool Conversational BI + governed regulated renders — from one foundation
Lock-in New vendor, same problem OSI-portable semantic layer — swap renderers without rebuilding
Regulatory reports Migrated as-is, still manual Stay — but now fed by the same governed semantic layer as conversational BI
Timeline to value Long — report by report Phased — semantic layer first, both output lanes follow
AI-readiness None — raw tables still the query surface Built in — semantic model is the governed query surface for all agents
Vendor pitch resistance Vulnerable — next tool swap already coming Durable — foundation is vendor-agnostic
⚡ The Window

Clients are getting pitched conversational BI by Databricks and Snowflake right now. Some are saying yes before they understand what it takes to make it work on a real estate. When it breaks — and on a raw, ungoverned estate it will — someone gets called in to fix the semantic layer. That call is the entry point. The window to be that someone is 12–18 months before the market learns to ask for it upfront.


§7 — The Portable BI Play

The experience is leaving the tool

The lock-in that Tableau, Power BI, and Qlik rely on lives in their semantic layer. Move that layer out, make it portable, and the BI tool becomes a rendering surface you can swap. OSI is early. The opportunity to own the portability layer is now.

Most Mature
dbt Semantic Layer (MetricFlow)

Define metrics once in YAML alongside dbt models. MetricFlow generates SQL for every downstream tool. Flows to Tableau Cloud, Power BI, Looker, Genie via REST, GraphQL, and SQL. Requires paid dbt Starter or Enterprise tier.

GA — Most Adopted
Warehouse-Native
Databricks Metric Views

GA in 2026. Integrated with Genie and Unity Catalog governance. Deep Databricks-native. Not portable to Snowflake or other platforms.

GA 2026
Warehouse-Native
Snowflake Semantic Views

GA in 2026. YAML-based, powers Cortex Analyst. Snowflake-only. Not portable. LookML carries the same warning — meaningful vendor lock-in.

GA 2026
Open Standard — Emerging
OSI / Apache Ossie

Launched January 2026 by dbt Labs, Snowflake, and Salesforce/Tableau. Targets portable authorship of semantic definitions across platforms. No product ships native import/export yet. The standard exists — the ecosystem is catching up.

Emerging · Jan 2026