What a 30 day FaultPilot pilot actually looks like
One fleet, one crew, thirty days. What we set up, what we measure, what it costs, and what you walk away with either way.
Why a pilot and not a free trial
A free trial of maintenance software tells you almost nothing. A couple of people poke around a demo environment with fake machines, nobody changes how they work, and after two weeks everyone goes back to the radio and the paper job cards. Then the question of whether it actually works on your site never gets answered.
A pilot is a different thing. Real machines, a real crew, real faults, and a number at the end that you can put in front of your manager. That takes proper onboarding and proper support, which is why we charge for it and why we keep it small.
The shape of it
Thirty days. One fleet and one crew. $5,000 flat, no lock-in, and if you go ahead the pilot fee comes off year one. If you don't, you've spent five grand to find out with certainty, on your own gear, whether this works for your operation. Most sites spend more than that on a single misdiagnosed sensor.
Before anything gets installed, we sit down and agree on what a win looks like. Usually that means two numbers: time to diagnosis and time to repair, measured on your machines during the pilot. Your numbers, agreed up front, so there's no marking our own homework at the end.
Day one and day two
Day one is ours. We import your machine list, load the licensed OEM docs you give us, and walk your crew through the app on site. If you have old fault records we can bring those in too, so the fleet's memory isn't blank from the start. There's no new hardware and no IT project. It runs on the phones and tablets your crew already carries, iOS and Android, and it works offline underground.
Day two, your crew is running it. Logging faults, getting ranked causes and step-by-step checks out of Trace with the source shown next to each step, and handing over shifts with the full history attached. From there our job is support and staying out of the way.
What we ask from you
Three things. Your machine list. Your licensed OEM documentation, because Trace only works from real sources and we don't scrape manufacturer IP. And a supervisor who actually wants the pilot to get a fair run. That last one matters more than the other two put together.
What you get at the end
A measured before-and-after on time to diagnosis and time to repair, on your own machines, plus a month of clean fault records and handovers you keep either way. Every fault exports to a PDF with the full handover chain, steps, photos and notes, ready for your CMMS. Your data is yours whether you continue or not.
If the numbers don't stack up, you walk away with the data and we part as mates. If they do, you already know what you're buying, because you've watched your own crew use it for a month.