Our services, in detail

Four services, starting with what the data actually contains.

Program 01 · Before anything is built

Data quality audits

We profile the data before designing anything, because the answer to most reporting problems is that two systems disagree or a field has been used three different ways over five years. Finding that first costs a fortnight and saves rebuilding a dashboard nobody trusts.

  • 2 to 4 weeks
  • Organisations
  • Fixed fee
  • Read access only

Start this program

Stage 1 · Minimum data

The smallest extract that answers it.

Stage 2 · Profile

Duplicates, gaps, coding drift.

Stage 3 · Report

What is reliable and what is not.

Stage 4 · Honest scope

Including fixing records first.

Stage 1 · The decisions

What people actually act on.

Stage 2 · Definitions

Written and agreed, measure by measure.

Stage 3 · Build

Small, then extended on evidence.

Stage 4 · Review

After a month of real use.

Program 02 · Built around a decision

Reporting and dashboards

A dashboard with forty tiles gets ignored within a month. We start from the decisions somebody actually makes weekly, agree a written definition for every measure, and build the smallest thing that answers them — because disagreement about what a number means is what kills reporting, not the chart type.

  • 3 to 8 weeks
  • Organisations
  • Fixed per phase
  • Access to the users

Start this program

Program 03 · Same answer every time

Pipelines and warehousing

Manual extracts produce a different total depending on who ran them and when. Automating that removes the variation, and the work is mostly in the error handling — what happens when a source is late, a field changes type, or a load half-completes. Silent failures are worse than loud ones.

  • 4 to 10 weeks
  • Organisations
  • Fixed per phase
  • System access

Start this program

Stage 1 · Sources

What feeds what, documented.

Stage 2 · Failure cases

Designed first, not patched later.

Stage 3 · Build

With logging you can actually read.

Stage 4 · Alerting

Loud failures, not silent ones.

Stage 1 · Documented

So another team could pick it up.

Stage 2 · Training

On the parts they will change.

Stage 3 · Definitions kept

A single list, maintained.

Stage 4 · Clean exit

Whenever you want it.

Program 04 · No dependency created

Handover and training

Models, queries, configuration and documentation are yours, and we would rather train your team than become a permanent dependency. A good engagement ends with somebody internal able to add a measure without calling us.

  • Included or ongoing
  • Client teams
  • Included at handover
  • Staff time

Start this program

Reporting nobody trusts?

A free first call on what the numbers are actually meant to decide.