Business functions
Supply Chain
Planning and execution across systems that were never designed to talk to each other.
Where it hurts
The week these teams actually have, in their own words. If two of these are yours, the rest of this page is about you.
Fragmented visibility
Status assembled by email.
Exception handling
Every delay handled manually, from scratch.
Our work
What the work runs on
The products these engagements were built on, most used first.
Ways to start here
Fixed-scope engagements we have run against exactly this kind of problem.
Diagnostic
Process Mining Diagnostic
Six weeks of event-log evidence answering where the cost actually sits, often upstream of the process you were told to fix.
Fixed scopeDuration: 6 weeks
Blueprint
Integration Blueprint
Three weeks mapping the systems, the data contracts and the failure modes, before anyone writes integration code.
Fixed scopeDuration: 3 weeks
From the practice
9 min read
Process intelligence
What process mining tells you in the first 90 days
Usually: that the expensive problem is upstream of the one you were asked to fix.
6 min read
Agentic AI
When not to use an AI agent
If the rules fit on one page and never change, an agent is an expensive way to run an if-statement.
7 min read
Automation strategy
Your automation backlog is a list of opinions
Most backlogs rank candidates by who asked loudest. Event logs rank them by what they cost.
7 min read
Technology transformation
You do not need to replace the system to fix the process
Most of the pain attributed to a legacy platform is actually in the gaps between platforms, and gaps are far cheaper to close than cores are to replace.
How we see it
Demand signals, supplier commitments, logistics status and the reconciliation between all three.
Talk to us
Bring us one Supply Chain process and we will tell you what it would take.
Not a proposal: a read on whether the thing you have in mind is worth automating at all, what it costs, and where it usually goes wrong in this function.
2 case studies



