A diagnostic doesn't start with our opinions. It starts with your database: every table, every column, every null, until the data itself says where the margin is hiding. This is what one operator's extract surfaced, and where each question led.
What should every route actually be priced at?
Static tariffs against route-level reality. The pricing analysis is in progress.
In analysis
A Flow Dynamics diagnostic is a fixed-scope engagement. We take an extract from your transport management system, work on hardware inside your estate, and return with evidence: where cost is leaking, how large each leak defensibly is, and what it would take to close it.
It begins with exploratory data analysis, the unglamorous pass that everything else depends on. Before any model runs, we need to know what your data actually says, and just as importantly, where it can't be trusted.
The operator behind this series is anonymised. Every figure across these pages comes directly from the diagnostic notebooks. Nothing has been adjusted for presentation.
The first week is an audit of the database itself. Six passes, each one a filter that decides what the later analysis is allowed to rely on.
Every table and column catalogued, typed and mapped to the operation it describes.
What's recorded versus what's reliable. Columns that look useful and turn out to be empty are removed before they can mislead.
Descriptive statistics on every continuous variable: ranges, outliers, and the values that shouldn't be possible.
Volumes over time, seasonality, and the outliers that distort any average built on top of them.
Do the coordinates tell the truth? Sites, destinations and map points cross-checked against each other.
What's charged versus what's on file: the pass that exposes missing tariffs and loose mappings.
By the end of the first pass, the extract had raised its own problem statements: deck space moving empty, haulier rates that didn't reconcile with the rate cards, and tariffs missing from a majority of routes. Each one became a hypothesis to be tested against the operator before any deeper work began.
Both deep dives in this series began life as a single anomaly in the first pass. The 41.7% fleet finding started as an odd shape in a load distribution. The haulier finding started as a rate column that wouldn't reconcile. The diagnostic's job is to notice, then to prove or kill the hypothesis with the operator's own numbers.
Each deep dive takes one problem statement from the first pass and follows it until the number stops moving. These are published in full, charts and caveats included.
A Flow Dynamics diagnostic runs this first pass on your data, on your infrastructure. Nothing leaves your estate. Fixed fee, fixed scope, invoiced on completion. You end up with evidence, not a sales deck.
Talk to Flow Dynamics