← Back to homeCase Study

Cutting forecast error in half with a unified data pipeline

How a fragmented, spreadsheet-bound forecasting process became one trusted pipeline — and halved forecast error along the way.

Case Study·May 2026
Cutting forecast error in half with a unified data pipeline

A mid-market distribution business was running one of its most important numbers — the demand forecast — across a dozen disconnected spreadsheets. Each region kept its own version, reconciled by hand, and by the time the figures reached leadership, nobody entirely trusted them.

The symptoms were familiar: stock in the wrong places, decisions delayed by "let me check that number," and a planning team spending more time assembling data than thinking about it.

The challenge

What we did

We didn't start with a model. We started with the plumbing.

Unified the data

We consolidated the regional sources into a single governed pipeline — automated ingestion, validation, and a documented flow from raw input to final figure.

Made the numbers trustworthy

Reconciliation checks, freshness monitoring and tests now run automatically, so a broken input is caught before it reaches a decision rather than after.

Rebuilt the forecast on solid ground

Only once the data was reliable did we improve the model itself, with a clear evaluation harness so every change could be measured instead of argued.

The results

‒48%
forecast error
days → min
reconciliation time
1
source of truth
The model got the credit. The data pipeline did the work.

The lesson generalises: most forecasting problems are data problems wearing a modelling costume. Fix the plumbing and the accuracy tends to follow.

Have a forecast nobody trusts? That's usually where we start.

Work with us

Have a project that needs this kind of thinking?

Tell us where you're stuck. We'll tell you, honestly, whether and how we can help.

(start a project)