'/%3e%3ccircle%20cx='98'%20cy='41'%20r='9'%20fill='%2322D3EE'/%3e%3c/svg%3e){kind=small}
'/%3e%3cellipse%20cx='520'%20cy='260'%20rx='360'%20ry='132'%20stroke='%238B93B0'%20stroke-opacity='0.18'%20stroke-width='1'%20transform='rotate(-16%20520%20260)'/%3e%3ccircle%20cx='520'%20cy='260'%20r='46'%20fill='%23111A38'%20stroke='%2322D3EE'%20stroke-opacity='0.35'/%3e%3ccircle%20cx='920'%20cy='80'%20r='6'%20fill='%2322D3EE'/%3e%3c/svg%3e)
From spreadsheet chaos to one KPI dashboard
Challenge
Leadership reporting was stitched together by hand from ERP exports and a sprawl of spreadsheets. Numbers disagreed between departments, and a single monthly pack took days to assemble.
Approach
We consolidated the sources into a warehouse with an ELT pipeline of tested, version-controlled transformations, and agreed one contract per metric with leadership so a KPI means the same thing everywhere. Data-quality and freshness checks run before anything is published, and self-served BI dashboards replaced the manual pack so teams pull the current number instead of waiting on an export.
Architecture
ERP + spreadsheets → ELT (dbt) → modeled warehouse → quality & freshness checks → BI dashboards
dbt · PostgreSQL · Airflow · Metabase — metric contracts, tested transformations, Great Expectations checks
Results
- Monthly reporting cut from days to under an hour*
- One agreed, version-controlled definition per KPI
- Leadership self-serves live dashboards instead of requesting exports
* Illustrative figure from a representative engagement, shown to convey typical scope. Replaced with client-verified numbers before publication.