Video | Tableau | Industry trends | Tool strategy | Data visualisation

Cost Per Query: Your dashboards are about to look expensive

Consumption pricing is coming to Tableau Next, and once a dashboard has a cost per query, best practice quietly becomes whatever is cheapest to run.

Watch on YouTube
  • Tableau's pricing has shifted from fixed seats and cores to cloud convenience and now to consumption, where the more you use the more you pay.
  • Cost per query means every chart, filter click and interaction becomes a chargeable event - one dashboard with four charts used by ten users at five interactions can generate around 500 billable activities in a day.
  • Tableau Next connects to Data Cloud in real time with no extract concept, so caching works differently and queries are constantly running in the background.
  • Salesforce wants to consolidate previously separate invoices (Tableau, Snowflake, AI credits, dbt) into a single Salesforce bill, which makes the true cost of running dashboards far more visible and involves new stakeholders like IT.
  • Consumption pricing risks decoupling visualisation best practice from cost-driven practice, pushing teams toward simpler, cheaper charts to minimise queries.

Tim argues that consumption-based pricing, arriving with Tableau Next, will turn every chart, filter click and interaction into a billable event — and once dashboards have a visible cost per query, cheapest-to-run risks quietly replacing viz best practice as the design priority.

This is an opinion piece tracing how Tableau's pricing model has evolved and what changes when Salesforce puts consumption pricing behind Tableau Next dashboards. No hands-on demo — it's a walkthrough of a pricing shift and its knock-on effects for how people build dashboards.

The Breakdown
  • Seats and cores were fixed cost 1:08

    Tableau's original model was licences plus server compute you bought once: usage didn't change your bill, so however many queries ran or dashboards loaded, cost stayed broadly flat.

  • Cloud made hosting someone else's problem 2:06

    The move to Tableau Online/Cloud was framed as convenience — Tableau managed the infrastructure, which lowered the barrier for smaller organisations, but it was the first quiet step away from fixed, self-owned cost.

  • Consumption crept in through add-ons 2:41

    Features like Prep Conductor's credit system and Einstein Analytics already charged by usage; AI tooling accelerated this because every model query genuinely costs money, cementing 'the more you use, the more you pay' as a pricing pattern.

  • Snowflake's compute/storage split is the template 3:53

    Snowflake charges mainly for storage plus compute only when a warehouse spins up to run a query — you save when idle but pay more during demand surges; this scale-up/scale-out consumption model is the pattern Tableau Next is following.

  • One Salesforce invoice replaces several separate ones 6:06

    Previously Tableau, Snowflake, AI credits and dbt costs sat in different budgets (IT, analytics, marketing) and nobody saw the full picture; Tableau Next routes everything — including Data Cloud — through a single Salesforce bill, making the true cost suddenly visible and pulling in stakeholders like IT who weren't previously part of Tableau conversations.

  • Every interaction becomes a chargeable event 10:47

    In Tableau Next, a dashboard with four charts, ten users and five interactions each can generate roughly 500 billable query events in a day, before counting alerts and subscriptions — because there's no extract concept, everything queries Data Cloud in real time with a different caching model than desktop/Snowflake users are used to.

  • Cost pressure risks decoupling best practice from cost-driven practice 13:20

    Once a dashboard's running cost is visible and variable month to month, teams under budget pressure may gravitate toward simpler, cheaper-to-query charts purely to control cost, rather than what's genuinely best for the audience.

  • Start asking what a dashboard is actually worth 14:23

    Tim's suggestion: start estimating cost-per-query on your dashboards now, so when Tableau Next pricing lands you can compare it against the value the dashboard actually generates, rather than reacting cold to an unfamiliar invoice.

Worth Knowing
  • Tableau Next has no extract concept — everything connects to Data Cloud live, so caching behaves differently from the desktop/Snowflake world.
  • Consumption pricing already exists in pockets of Salesforce (e.g. Einstein Analytics), so this won't be new to users coming from that world.
  • This is opinion and forward-looking — Tim is flagging a likely shift and its risks, not describing a launched pricing sheet.
Use It When

Useful framing if you're about to justify Tableau Next (or any consumption-priced BI tool) to finance or IT, or if you want to get ahead of cost-per-dashboard conversations before a variable invoice lands on someone's desk.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.