The Looker quote you receive is not the Looker bill you pay.
The licence covers the platform. LookML is where the budget quietly goes.
What's on the quote vs what lands
| Line item | On the quote? | Notes |
|---|---|---|
| Platform / instance fee | Yes | The number people compare |
| Per-user tiers | Yes | Viewer vs Explorer vs Developer |
| LookML maintenance | No | An engineer's time, permanently |
| Warehouse compute | No | Billed by BigQuery/Snowflake, not Google |
| Re-modelling on schema change | No | Arrives as sprint work |
| Migration if you ever leave | No | Definitions are in LookML, not portable |
The per-user tiers deserve attention: a "viewer" who filters a dashboard can reclassify as an explorer. Adoption success shows up as a licensing surprise.
The real cost driver
LookML was the right instinct — put metric definitions in reviewed code instead of scattering them across dashboards. Consistency improved and stayed improved.
The cost is that coverage equals authoring effort. Every new concept is a pull request. Every schema change is maintenance debt. Every question outside the model is a ticket, and the ticket is the actual user experience.
That is fine when the consumer is a human analyst who can wait two days. It stops working when the consumer is an AI agent asking things nobody pre-modelled, at machine rates.
How to build an honest comparison
Price three things, not one:
- Licence and platform fee
- The engineer who keeps the model current — the salary line nobody puts in the TCO
- The latency between a business question and a trustworthy answer
The third is the one with real money in it. Cipla cut decision latency by over 90% and IT report requests by 80% — neither number appears on any BI invoice.
The full breakdown — current published figures, how the tiers actually reclassify users, and a like-for-like TCO model — is here:
👉 Looker Pricing in 2026: What Google Publishes, What You Actually Pay
Originally published at colrows.com/blogs/looker-pricing
Top comments (0)