Toolbelt OS
The operating system for a field service shop
A service shop does not run on deals. It runs on jobs with a truck attached — where the second stop of the day is cheaper to serve than the fifth, where one invoice hides three completely different money lines, and where the work you go back and redo for free never appears on any report. Toolbelt OS is built around that, instead of around a generic calendar.
Dispatch that shows its reasons
Ranks every tech on distance, primary trade, whether the part is already on their truck, history with that customer, callback record and overtime risk — with the reasoning visible, so a dispatcher can argue with it.
Proof of service
Arrive and depart with time and place, tasks, photos and a signature. Offline capture keeps the original time when there is no signal in the crawlspace.
Licences and permits gate the work
An expired card pulls a tech off dispatch. Permitted work cannot close without its permit number — that gap is the finding that costs a contractor a licence.
Three money lines, kept apart
Labor over tech cost, parts over supply-house cost, and the trip fee. Flatten them into one number and you cannot tell which one is losing money.
The callback number
Work redone free because something you did failed. Costed every week, and counted by tech — because a pattern usually means training, not laziness.
Truck stock
What is on each truck, what the week's jobs will consume, and which jobs are about to become two trips.