Built for waste and bin operators whose run sheet and invoice are two different documents, and whose only proof a site was serviced is that nobody rang to complain. Fixed-price builds in ten business days, or an Ops Care plan that keeps shipping fixes every month.
Every route business I audit shows the same five bleeds, in different proportions. The first two are the expensive ones: work you cannot prove, and a run only one person can complete. The audit tells us which is dominant in yours.
A site says it was missed. You are fairly sure it was not, because the run says so and your driver is reliable. But the run is a sheet, the driver has gone home, and all you can send back is an assurance. An assurance does not beat a written complaint, so you wear the credit, or you go back for free.
A site gets added mid-contract. A bin gets swapped and nobody updates the schedule. Two systems disagree about whether an address is active, and only one of them has evidence behind it. If the run sheet and the invoice are maintained by two different people, the gap between them is work you are doing for free.
Which addresses, in what order, which gate code, which bin lives behind the fence, which site to skip over Christmas. It is all in one head. A sick day costs a day of revenue, a new driver takes months to be useful, and you cannot take a proper holiday.
The driver hits four exceptions before ten o'clock and tells you about two of them at the depot. The contaminated load that should have been charged, the site that has not put a bin out for three weeks, the access that keeps failing: all of it is billable or fixable, and all of it evaporates by Friday.
Industrial estates, rural runs, basement bin rooms. An app that needs four bars is an app that loses a morning of records every time the truck goes somewhere awkward, and the driver stops trusting it after the second time it eats their work.
Same five Bolt On Ops packages every operator gets. This is the waste-run-specific map.
Every fix below sits on top of the software you already run. Nothing gets ripped out.
Your current software nearly works. The bits that don't are where the spreadsheet, the text-message thread, and the Sunday admin live. I build the missing piece, integrate it cleanly, and leave the rest of your setup alone.
Good for getting the truck to the address; weaker on proving the service happened and reconciling what was serviced against what was invoiced. I build that layer on top and hand the data back clean. Your routing stays where it is.
Plenty of good operators are, and it works right up until the second truck. The upgrade path is clean: capture the run and the proof first, then the billing reconciliation, without ripping out what already works.
Keep it. The gap is not the accounting package, it is that nothing tells it which sites were actually serviced this cycle. That reconciliation is the piece that usually pays for the build.
Live tools, not videos. Click through, kick the tyres, steal the ideas.
The one that matters here. Servicing that had been going out unbilled, evidenced once every service carried a time, a location and a photo. Written up with the numbers.
Open the demoWhat the driver sees: today's run in order, access notes, two-tap exceptions, photo capture. Offline-first, because half a run has no signal.
Open the demoThe office end of the same data: the run on a schedule, the crew view, and the invoice queue filling itself from what actually happened.
Open the demoTalk to the AI receptionist in your browser, like a customer would. It answers, works out the job, flags the urgent ones and captures the lead — 24/7, in your business's name. If it ever can't pick up, the missed-call text-back still fires.
$165/mo inc GST, free on Ops Care Standard and Pro. If it doesn't catch you a job in your first 30 days, you don't pay that month.
One price, month to month. No lock-in, no setup fee, cancel any time. See how it works
I'm Brad Stribley. I run Oscar White (commercial cleaning) and Ranges Cleaning Co. (residential), both of which are recurring-route businesses with different bins on the back. I have rebuilt a run around one cancellation, chased a client who swore a site was missed, and built the tools for my own crews first.
Waste is not my own trade, and I am not going to pretend otherwise. What I do know cold is the run shape: recurring sites, a driver holding the round in their head, and work that becomes invisible the second it is finished. That is the same problem in a bin truck as it is in a cleaning van, and it is the one I have built for repeatedly.
The waste-specific version came from building it for a real waste operator, which is on the Howyabin case study rather than in a claim on this page.
No, and I will tell you when the answer is no. If your routing works, keep it. The gap on most waste runs is not getting the truck to the address, it is proving the service happened and reconciling what was serviced against what was invoiced. I build that layer on top and hand the data back clean.
It has to, or it is useless. Industrial estates, rural runs and basement bin rooms are exactly where the record matters and exactly where the reception is not. The pattern I build is offline-first: the phone holds the run locally and syncs when it gets signal, so a driver never loses a morning of work to a dead zone.
Less than they do now, or it will not stick. Arrived, serviced, photo where it matters, exception in two taps. If capturing a site takes longer than a few seconds it will be skipped on a bad day, and a half-filled record is worse than none because you start relying on it.
They will if you use it that way, so do not. The record exists so a driver can prove they serviced a site when a client says otherwise, and so nobody has to ring the boss to find out what a site needs. Framed as backing them, it gets filled in properly. Framed as timing them, it does not.
It depends entirely on how tight your records already are, and I am not going to guess at yours. What I can tell you is what happened for one waste operator: once every service carried a time, a location and a photo, around $30,000 a month of servicing was evidenced as going out unbilled. The system did not find money that was not there, it made visible work that was already being done for free. The detail is on the Howyabin case study.
I own the source and licence the running application to you, which is what keeps the price where it is: the codebase compounds across clients instead of being rebuilt from scratch each time. You get your own environment, your own data, and an admin role over it. There is a buyout option if you want the source outright, and a source-escrow commitment if Bolt On Ops ever winds up.
30-minute call. One-page written finding inside 48 hours. Three prioritised fixes ranked by impact, with rough hours-saved estimates and a 30/60/90 day action plan. If there's a fit, I recommend an Ops Care plan or one of the five packages. If there's no fit, you keep the findings anyway. Available across Victoria.