Beaver Pumice Replaced Paper Dispatch
in 6 Weeks. Enterprise Didn't.
Enterprise dispatch vendors wanted 6 weeks just to finish the discovery phase. ResultantAI delivered a production-ready custom dispatch system - driver app, automated ticketing, real-time dashboard - in 6 weeks total.
The Operation
Beaver Pumice operates a pumice quarry and aggregate delivery business in Oregon. Fifteen trucks. Dozens of deliveries per week across job sites, construction projects, and supply yards throughout the region.
Like most aggregate and quarry operations, their dispatch ran on phones, whiteboards, and paper load tickets. Drivers got job details over the phone. Tickets came back crumpled and sometimes unreadable. The office re-entered everything manually. Invoices went out 2-3 days after delivery.
The operation was profitable - but the administrative overhead was scaling with every truck they added. Adding truck 16 meant adding more dispatch time, more re-entry, more billing delays. The math on growth wasn't working.
Before: The Paper Dispatch Problem
The Growth Ceiling
Every operation running paper dispatch hits the same wall: growth requires proportionally more dispatch labor. You can't add trucks without adding someone to manage them. At some point you're paying a dispatcher to shuffle paper instead of running routes.
For Beaver Pumice, the tipping point was clear. The question was whether to buy a $75K+ enterprise system - or build something custom that actually fit how they operated.
Why They Didn't Buy Enterprise Software
Enterprise Timeline
The first vendor needed 6 weeks just for discovery and scoping - before writing a single line of code. Total implementation estimate: 4-6 months.
Enterprise Cost
Ballpark pricing for an operation of their scale: $75,000-$125,000 upfront, plus $2,000-4,000/month in licensing. With zero ownership of the software.
Enterprise Fit
Systems built for ready-mix concrete or large-scale logistics don't map cleanly to pumice aggregate operations. Configuration would have been painful and partial.
Ownership Model
Every enterprise platform means you're renting software indefinitely. Stop paying, lose the system. Beaver Pumice wanted to OWN what they built.
What We Built
Three components. Fully custom. Built for how Beaver Pumice actually operates.
Digital Dispatch Board
One screen. Every truck. Every load. Dispatch assigns loads with drag-and-drop. Drivers see their assignment instantly on the app.
- Real-time load status per truck
- Drag-and-drop load assignment
- Site contact and delivery notes attached
- Weather and route alerts
Driver Mobile App
Driver opens the app and sees their next load. Tap to confirm. Navigate. Update status. Capture signature. Done.
- Load details auto-filled - no radio calls
- One-tap status updates: Loading → Hauling → On Site → Returned
- Customer signature capture on phone
- Photo upload for delivery verification
Automated Ticketing
Driver marks delivered. Ticket generates instantly with tonnage, materials, job site, and applicable rates. Exports to QuickBooks.
- Zero manual data entry on tickets
- Invoice same day - not 2-3 days later
- No billing errors from illegible paper
- QuickBooks sync in real time
The 6-Week Timeline
Results
“Different industry but same dispatch problems. Enterprise systems wanted 6 weeks just to scope it. ResultantAI delivered production-ready in 6 weeks total. Drivers adopted it faster than I expected - and I expected pushback.”
The Driver Adoption Question
Every operator asks this before they commit: what if the drivers won't use it?
At Beaver Pumice, the driver population skewed older - several had been hauling for 15+ years and weren't looking for a new workflow. We designed the driver app for exactly that profile: one screen, big buttons, minimal taps. If a driver can read a text message, they can use the app.
Training took 45 minutes per driver. By the end of week 5, all 15 drivers were using the app on live loads. No one reverted to paper. The last holdout - a 22-year company veteran - stopped calling dispatch for load details entirely by day 4.
The data tells you why: the app made their day simpler, not harder. No more waiting for the dispatcher to call back with an address. It was already on their phone.
If You Run Aggregate, Quarry, or Bulk Delivery Operations
This is not a concrete-only system
The Beaver Pumice build started from the same dispatch architecture we use for ready-mix. Aggregate, sand, gravel, pumice, fill - same core problems, same solution pattern.
You own the code
Beaver Pumice owns their system outright. No vendor dependency. No licensing fees. They can self-host it for $0/month or pay for managed hosting.
Same 6-week timeline
This isn't a 6-month ERP project. If your operation is 5-25 trucks, 6 weeks is the target. We've done it.
Running Paper Dispatch?
Let's Fix It in 6 Weeks.
Book a 20-minute assessment. We'll walk through your operation, calculate your exact ROI, and show you what a custom dispatch system looks like for your fleet.
Also see: Ready-Mix Concrete Dispatch · Wayne Conn Plumbing Case Study