NEW: Scale AI Case Study — ~1,900 data requests per week across 4 business units Read now →
Contents
Dashboards & BI
Business intelligence and dashboarding tools turn warehouse data into charts, dashboards, and reports that humans actually look at. The dominant platforms are Tableau, Power BI, Looker, Sigma, ThoughtSpot, QuickSight, and Apache Superset.
A business intelligence (BI) tool is the layer of the data stack where data finally meets a human eyeball. Everything underneath it — warehouses, pipelines, transformations, semantic layers — exists to put numbers in front of someone who needs to make a decision. The BI tool is what turns those numbers into a chart, a dashboard, a report, or (increasingly) an answer.
Think of it this way: if the data warehouse is the library, the BI tool is the librarian who hands you the right book. A good one knows where everything is, formats the answer cleanly, and doesn't make you write SQL to ask a simple question. A bad one drowns you in pivot tables and stale PDFs.
The BI category is older than almost anything else in the modern data stack. Cognos was founded in 1969. BusinessObjects in 1990. MicroStrategy in 1989. Most of those names still exist, mostly inside IBM and SAP, mostly running inside Fortune 500 finance departments. The "modern" BI era starts around 2003, when Tableau spun out of a Stanford research project and decided that dashboards should look pretty and respond to mouse clicks. Twenty years later, the category has fragmented into at least four philosophies that are still fighting it out.
There is no single "right" way to build a BI tool, and the dominant products represent fundamentally different bets about what users actually want.
1. The "drag-and-drop visualization" school (Tableau, Power BI). The premise: most users don't know SQL, but they know what a bar chart looks like. Give them a canvas, let them drop fields onto shelves, and the tool figures out the query. This was Tableau's revolutionary move in the mid-2000s and the model Power BI copied (and arguably perfected, by giving it away for free with Microsoft 365). It is still the most popular paradigm by headcount.
2. The "code-defined model" school (Looker). The premise: drag-and-drop tools create chaos because every analyst defines "revenue" differently. The fix is to define metrics once in code (LookML), version-control them in Git, and make every chart in the company derive from that single source of truth. Looker invented this category in 2012 and got acquired by Google for $2.6B in 2019. The semantic layer movement (dbt Semantic Layer, Cube, MetricFlow) is essentially a generalization of what Looker did.
3. The "spreadsheet" school (Sigma). The premise: business users already know Excel. Stop trying to teach them a new paradigm. Give them a spreadsheet UI that secretly issues warehouse-scale SQL underneath. Sigma is the leading example, and it's growing fast precisely because finance and ops teams don't have to learn anything new.
4. The "search-first" school (ThoughtSpot). The premise: even drag-and-drop is too much friction. Users should just type questions in plain English ("revenue by region last quarter") and get a chart back. ThoughtSpot pioneered this in 2012, well before LLMs made the approach practical. With the rise of generative AI, this is rapidly becoming the dominant philosophy — every BI vendor now ships some version of "ask a question, get a chart," and conversational analytics tools like TextQL are eating into the dashboard category from this direction.
There is also a fifth, parallel track: open-source BI. Apache Superset (originally built at Airbnb) and Metabase represent the "we don't want to pay $75/seat/month" alternative. Superset in particular has become the default BI layer for cost-conscious data teams running on Snowflake, BigQuery, or ClickHouse.
Underneath the marketing, every BI tool in the world does the same four things:
1. Connect to data sources. Almost always a SQL warehouse (Snowflake, BigQuery, Redshift, Databricks), sometimes Postgres or MySQL, occasionally a CSV. The connection mechanism is usually JDBC, ODBC, or a native driver.
2. Define a model. This is where philosophies diverge. Tableau calls them "data sources," Power BI calls them "datasets" (powered by DAX), Looker calls them "Explores" (defined in LookML), Sigma calls them "data models," Superset calls them "datasets." All of them are doing roughly the same thing: pre-defining how tables join, what counts as a metric, and what the columns mean in business terms.
3. Build visualizations. Bar charts, line charts, maps, tables, KPIs. The mechanics vary (drag-and-drop vs. code vs. SQL vs. natural language), but the output is the same.
4. Share and embed. Dashboards get sent over email, embedded in Confluence or Notion, surfaced in Slack alerts, or wrapped in iframes inside customer-facing apps. "Embedded analytics" is a multi-billion-dollar sub-category by itself.
Just like with data warehouses, every BI vendor defines the category in a way that flatters their own product. Reading the marketing without understanding the bias will mislead you.
Tableau wants the world to keep believing that beautiful, exploratory visualization is the heart of BI. That was true in 2010. Since the Salesforce acquisition in 2019 ($15.7B, the largest BI deal ever), Tableau has been slowly stagnating — losing share to Power BI on price and to Looker/Sigma on governance. Salesforce's strategy has shifted toward folding Tableau into the Einstein and Data Cloud story, which has confused customers and slowed product velocity.
Power BI wants you to think of BI as a Microsoft product. Their strategy is simple and devastatingly effective: bundle it with Microsoft 365 (now Microsoft 365 Copilot), price it at $10/user/month while Tableau charges $75, and let the Microsoft enterprise sales motion do the rest. Power BI is now the largest BI tool in the world by user count, and it's not close.
Looker wants BI to be governed, version-controlled, and centralized through a semantic layer. After the Google acquisition in 2019 ($2.6B), Looker became increasingly tied to Google Cloud and BigQuery, and its independent momentum has slowed. The LookML idea, however, won — it's the conceptual ancestor of every modern semantic layer.
Sigma wants BI to feel like Excel. Founded in 2014, it's the fastest-growing of the cloud-native BI tools and has become particularly popular with finance, ops, and "Excel power user" personas who never adopted Tableau or Looker.
ThoughtSpot wants BI to disappear into a search box. They were early to the "natural language query" idea and are now repositioning around AI agents (their "Spotter" product). They've struggled commercially against Tableau/Power BI but their thesis — that humans want answers, not dashboards — is increasingly being validated by the AI wave.
QuickSight wants you to use whatever AWS already gives you. It exists primarily so AWS customers don't have to pay Tableau, and its main selling point is deep integration with the AWS data ecosystem and aggressive per-session pricing.
Superset wants BI to be free, open, and warehouse-native. It's the default choice for engineering-heavy data teams who view paid BI as a tax.
Three things to know about where this category is in 2026:
Power BI is winning the volume war. Not because it's the best product, but because Microsoft's bundle is irresistible to enterprise IT. The Tableau-vs-Power-BI debate is mostly over outside of design-conscious analyst teams.
The dashboard itself is under attack. Conversational AI is doing to dashboards what dashboards once did to static reports. The future is fewer pre-built dashboards and more questions answered on demand — by ThoughtSpot Spotter, by Power BI Copilot, by Tableau Pulse, and by independent agents like TextQL.
The semantic layer is decoupling. The Looker insight — define metrics once, use them everywhere — is leaving the BI tool. Tools like dbt Semantic Layer, Cube, and MetricFlow now sit between the warehouse and the BI layer, letting you swap BI tools without breaking your KPIs. This is bad news for BI vendor lock-in and good news for everyone else.
TextQL Ana sits adjacent to — and increasingly above — the BI layer. Instead of building a dashboard for every possible question, TextQL Ana lets users ask questions in natural language and get governed answers backed by the same semantic models that power Tableau, Looker, or Power BI. Ana reads from your existing BI metadata (LookML, Tableau data sources, dbt models), respects warehouse permissions, and produces answers that match your dashboards. The result: business teams stop filing dashboard requests, analysts stop building one-off charts, and the BI layer becomes the system of record for definitions, not the only place users go to get answers.
See TextQL in action