About Conundrum
We solve the operational problems other people can't untangle.
A conundrum is a problem with no obvious answer. Fifty trucks, thirty thousand customers, inconsistent service times, a disposal site that is about to close, and a mandate to cut mileage without adding labor. That is not a GIS problem or a data problem or a routing problem. It is all three at once, and it is what we do.
- Weekly StPR
- Pre-change baseline
- Baseline StPR
- 22.2
- Week 14 StPR
- 27.6+24%
- Weeks to stabilise
- 4
What we believe
The plan has to survive a real Monday.
Model the whole system
Miles, time, capacity, day codes, service windows, and driver constraints are one problem. Optimising one of them in isolation is how routes get technically efficient and two hours late.
Work in your tools
ArcGIS, Python, and whatever routing software you already run. You should not need us to keep the plan alive after we leave.
Measure until it holds
A baseline before, weekly metrics after. If the change drifts, we want to know before your drivers tell you.
How an engagement runs
Assess, model, implement, measure.
- 01
Assess
Stop history, day codes, service boundaries, constraints. We establish the baseline before touching a route.
- 02
Model
Scenarios built on the whole system, so fixing one thing does not quietly break another.
- 03
Implement
We work next to dispatch and drivers through go-live. The plan has to survive a real Monday.
- 04
Measure
Weekly metrics against the baseline until the change holds. If it drifts, we find out why.
Who you'll work with
The people who scope it are the people who build it.
Conundrum is a small team of operations and analytics practitioners. The people who scope your problem are the same people who build the model and stand next to your dispatchers when it goes live.
Talk to us
Describe the problem. We'll tell you what we'd need to see.
No pitch deck. A short conversation about your operation and whether we can help.
Get a Route Analysis