Shared metrics
Align teams on definitions and calculations.
Numbers you can act on.
Shared metrics, useful dashboards and teams who can make sense of their data.
The situations in which clients most often call us on this subject.
Align teams on definitions and calculations.
Put useful information within reach of decision makers.
Help business teams explore trusted data.
Simplify reports and make refreshes reliable.
What we deliver
We start with the decisions you need to make, then define metrics, build analytical models and design reporting around your business teams.
We choose with you, based on what your team already knows how to run. No imposed technology.
The technical questions we get in a first meeting, with our candid answers.
Rarely. In most audits the problem sits upstream: diverging definitions of the same metric, calculations redone in every dashboard, data that is never tested. We centralise calculation rules in a semantic layer (dbt models, versioned metrics) that Power BI, Tableau, Looker or Metabase then consume. Changing tools without that work just moves the problem.
With one sheet per metric: business definition, exact formula, sources, filters, frequency, owner, and the edge cases settled (does a cancelled order count? as of which date?). The sheet is versioned next to the code that computes the metric, and a test checks that the two stay aligned.
By separating what is certified from what is exploratory. Certified models (governed, tested, documented) are the only basis for official dashboards; business teams explore freely from those models, never from raw tables. An exploratory metric that gains importance goes through a short certification path, not an IT ticket.
Two uses hold up in production today: natural-language questions on certified data (text-to-SQL constrained by the semantic layer, never on raw tables) and generated dashboard commentary reviewed by a human. Without a reliable semantic layer the model produces plausible, wrong answers; that is why we start with the foundations.
A project, a question, a doubt about an architecture: email us or book a slot. The first conversation is for understanding, not selling.