There are good off-the-shelf products for waste haulers, and if one fits your operation you should buy it. This page is for the operators it does not fit: the yard whose rate structure the product cannot express, the hauler whose zone and tonnage rules still need a spreadsheet alongside the software they pay for. We have built both sides of this, dispatch and the scale house, and both are in production now.
On the roll-off side, dispatching a job went from about ten minutes of phone calls and writing on a board to under a minute, and the board that took three people to run now takes one. Invoice timing did not move, because that was never the software's to fix.
A drag-and-drop board covering a full day of deliveries and pickups across the fleet, with pricing settled before an order is confirmed.
Software wired into the scale itself, so weights are captured rather than transcribed. Inbound waste and outbound material run as separate flows.
One searchable place for accounts, contacts, contracted rates and discounts, connected to the tickets and the invoices rather than beside them.
Reports built from real tickets and filtered by date, customer, material or driver, exportable the moment someone asks you for evidence.
Almost always because of pricing rules. Waste pricing is local, negotiated and full of exceptions: per-ton over an allowance, zone surcharges, contamination charges, per-customer contracted rates, different treatment for inbound and outbound. Products handle the common shapes and make you handle the rest by hand, which is how a yard ends up with a good piece of software and a spreadsheet that corrects it. Custom software is worth it at the point the exceptions are the business.
Both systems are available as working demos you can click through without booking a call. They are frontend rebuilds with the client branding stripped and fictional data, but the screens and the flows are the ones running in production.
Buy, if a product covers your pricing rules and your workflow without a spreadsheet propping it up. The products in this market are mature and cheaper than building. Build when the exceptions are the business: unusual rate structures, two divisions with different rules, hardware the product will not talk to.
Yes. We have a billing system in production driven by live weigh-scale hardware, where the scale supplies the weight directly rather than an operator typing it in. The integration depends on what the indicator exposes, and that is one of the first things we check.
That is exactly the shape we have built. Roll-off dispatch and billing on one side, scale house ticketing and billing on the other, with shared customer records underneath, so an account is one account across both and one invoice run covers it.
One price for the build, agreed at discovery and written down before you sign, with a first production version typically four to eight weeks out. A single piece, dispatch on its own or a scale integration for software you already have, is a much smaller job on both counts.
Describe what you’re building, what it has to do and when it needs to be live. You’ll get back the architecture we’d use, the trade-offs, and a realistic timeline, before anything is signed.