NADIR / Platform / 04 of 04
Closing the loop, and the part we will not build.
Five of the six steps between a repair order and a verified vehicle belong to software. One of them belongs to a technician and a calibration bay, and we have no intention of taking it.
The loop
Five of six.
Detect, flag, dispatch, recheck and close are ours. Recalibrate is not, and the arc into it is drawn dashed for that reason. There is a version of this company that tries to own the bay, and we think it is a worse company: it competes with the network that would otherwise be a distribution channel, and it converts an advisory product into one with physical liability.
What we do instead is make the handoff legible. The work order that leaves the platform names the tolerance, the measured deviation and the deadline, so the bay receiving it does not have to re-derive the problem. The loop closes when the recheck comes back, not when the invoice does.
Coverage
Reach, not distance.
A deadline is a drive-time problem, not a map-distance problem. A depot sixty kilometres from a bay on an open road is closer than one twenty kilometres away across a city at four in the afternoon. Coverage is drawn as a ninety-minute reach for that reason, and it makes the uncomfortable case visible: one depot sits outside every ring, and the SLA cannot honestly be offered there yet.
The recheck is what makes any of it provable. A recalibration produces a receipt; a recheck produces a residual that returns to baseline and stays there. Without the second one you know a bay was visited, which is a different claim entirely from knowing the vehicle is correct.
Honesty
What is built, and what is not.
Shadow scoring and evidence bundles are shipped. MTTFF-RE pilots and the on-premise edge pack are in pilot with real fleets. The bay dispatch API and recheck automation are planned and do not exist, and they are drawn as dashed outlines rather than filled bars because a filled bar for unbuilt work is the oldest lie in a product roadmap.
We would rather you buy the first two and be pleasantly surprised by the rest than the reverse. Every pilot conversation starts by establishing which column a capability is in, and a capability in the third column is not something we will price.
NADIR emits evidence and work orders. A human and a calibration bay do the rest.
If any part of this page reads as though the software fixes the vehicle, that is a writing failure on our part rather than a roadmap.
Want this pointed at your fleet?
We are onboarding fleets and repair networks a few at a time. Tell us what you run and we will reach out.