Define 'revenue' once, in one place, and every dashboard, notebook and AI assistant that asks for revenue gets the same number.
One shared recipe book the whole kitchen cooks from, instead of everyone remembering the dish slightly differently.
Self-serve without it reliably produces six definitions of revenue and a standing meeting to reconcile them.
Self-serve analytics fails in a predictable way: everyone gets access to the warehouse, everyone writes their own version of the metric, and within a year the organisation has six definitions of revenue and a standing meeting to reconcile them. A semantic layer is the fix — a governed model sitting between the warehouse and every consumer, holding the metric definitions, the join paths and the permitted dimensions. Tools query the layer rather than the tables, so the definition is enforced by construction rather than by discipline.
A semantic layer holds metric definitions, join paths and dimensions in one governed model, and every consumer — BI, notebooks, embedded apps, LLM assistants — queries it instead of raw tables. That guarantees one definition of each metric, removes the need for every user to know the schema, and gives a single place to enforce row-level access.
Semantic Layers in the Age of AI are 100% Needed — Alex The Analyst, 6:11