Data and analytics

Analytics and dashboards

You have dozens of dashboards and still argue about the numbers in every meeting. Sales has one revenue figure, finance has another, and the chart someone built last year has not been opened since. We help you agree on what to measure, then build the few dashboards that run the business.

What we do

Agree on the numbers. We sit with the people who use each metric and write down one definition: what counts, what does not, which date, which currency, which timezone. Active customer, revenue, churn. The definitions go into a short catalogue and into the SQL, so the dashboard and the document cannot disagree.

Build dashboards for decisions. Each dashboard has an audience and a question it answers. We show every number next to a target or a previous period, so a reader can tell good from bad at a glance. We keep pages short and fast to load. If a chart needs a paragraph to explain, we redesign it.

Set up self-service properly. We work with tools such as Looker Studio, Metabase, Power BI or Superset, and we adapt to what you already use. We prepare clean tables with business names, set permissions, and train the people who will build their own reports. Self-service on messy data just produces wrong answers faster.

Answer the one-off questions. Why did conversion drop in March? Which customers buy twice? Ad-hoc analysis in SQL or Python, written up in plain language, with the query attached so you can rerun it.

Retire what nobody reads. We check usage logs and turn off dashboards nobody opens. Fewer dashboards means fewer numbers to argue about and less to maintain. We also add a simple usage check, so the next unread dashboard is easy to spot.

Fix the data when the numbers look wrong. A dashboard is only as good as the tables under it. Because the same team works on the pipelines and the platform, we can follow a strange number all the way back to the source system instead of guessing. If a figure moved because a job failed or an event stopped arriving, you hear that before the meeting.

How it usually goes

Many teams start with the three-week KPI dashboard sprint. We agree on the handful of numbers that run the business, define them once and build one live dashboard on top. It is a small scope, and it shows quickly whether the data underneath can be trusted.

From there, some teams extend the same approach to sales, product and operations. Others take it over themselves with a few hours of review a month.

A good fit if

  • Different teams report different numbers for the same metric.
  • Leadership asks for a figure and waits days for it.
  • You pay for a BI tool that few people open.
  • You have the data but nobody has time to look at it properly.

Questions we get

Which BI tool should we use?
Usually the one you already pay for. Tools such as Looker Studio, Metabase, Power BI and Superset can all do the job for most companies. The choice matters less than having clean data underneath and agreed definitions. If you have nothing yet, we pick based on your data stack, your budget and who will maintain it.
What makes a good KPI dashboard?
It answers a small set of questions for a specific audience, shows each number against a target or a previous period, and uses definitions that are written down. It loads fast and is read regularly. If a dashboard does not change any decision, it should be retired.
How many KPIs should a company track?
Leadership usually needs five to ten numbers, not fifty. Each team can have its own handful, as long as they roll up to the company ones. More metrics on one page means less attention on each.
What is self-service BI?
Self-service BI means people outside the data team can answer their own questions with a reporting tool, without writing SQL or filing a ticket. It only works when the underlying tables are clean, documented and named in business terms. Otherwise people get fast answers that are wrong.

Tell us what's broken.

A few sentences is enough. We reply within one working day and the first call is free.