Build

Data and dashboards

The right figure, in one place for everyone, updated on its own.

The problem with reporting is almost never the tool: it is that two people calculate the same indicator differently, and the meeting is spent working out who is right. We start by writing down the definition of each figure — what it counts, what it excludes, over what period — and we put it in the dashboard, next to the figure. Automation comes after that, and only matters if the figure is right.

The method

How we work

  1. 01

    We write down the definition of each indicator

    In black and white, validated by the people who use it. Everyone skips this step, and it is the only one that ends the arguments about numbers.

  2. 02

    We connect the real source

    Straight onto your production data, with no intermediate copy. Every manual copy is a place where the figure can drift without anyone noticing.

  3. 03

    We build the screen people actually open

    Few indicators, readable in ten seconds, on the device you will really look at — often a phone, sometimes a weekly email.

  4. 04

    We automate the delivery

    A report you have to remember to fetch does not get read. Scheduled sending, plus an alert when an indicator leaves its usual range.

What you get

Deliverables

  • check_circleThe indicator dictionary: definition, source, what is excluded
  • check_circleThe online dashboard, fed by your production data
  • check_circleScheduled reports, by email or as exports
  • check_circleOut-of-range alerts on the indicators that matter

Frequently asked questions

Do you use Power BI or Looker?
If you already have them, we connect to them. Otherwise we build the screen inside your own application: people are already logged in there, and one fewer licence is one fewer renewal.
Will the dashboard slow the application down?
It can, if written badly: an indicator computed over millions of rows on every view has a price. We pre-compute what can be pre-computed and measure the cost of each query before putting it live.
Can we go back through history?
Only if the data was kept. It is the first question we ask, because the answer is often no — and you then need to start measuring immediately in order to compare in six months.

Let's talk about your project

Thirty minutes is enough to tell whether we are the right fit. We reply within 48 hours, and we say no when it is not for us.