The field app is offline-first.
The route loads before the truck leaves the yard. Photos, signatures, notes, and asset scans get captured with no signal and sync when it comes back. Nobody calls the office to ask where to go next.
For owners and ops managers
Three systems isn’t a stack.It’s a tax.
Dispatch in one tool, invoicing in another, ETAs from your personal phone. Every handoff between them costs money, and none of it shows up as a line item. This page is the argument for one board.
The status quo
Five line items that disappear.
None of these appear in your P&L by name. All of them are in there.
- A second dispatch system, because the first one doesn’t do fencing.
- Overage and damage fees nobody got around to billing.
- Support tickets to an incumbent that never calls back.
- ETA texts answered from your personal phone at 9pm.
- Hearing “the dispatcher didn’t know” after a missed pickup.
Status
ProDispatch is in development with its founding operators and is not generally available yet. The board below is the board from that build. Automatic ETA texts, the offline field app, and QuickBooks sync are in development, and founding operators run each piece as it lands.
Control
The yard runs off one board.
Your dispatcher works one screen for every truck and every asset type. Drag and drop, filter by site, driver, asset, status. At 7am the board answers the three questions that matter: what is out, what moves today, what comes back.
Today’s board, Tue14 stops / 5 trucks / 0 unassigned
TRK-04M. Reyes30yd roll-off, dropEllington Field, Gate 3En route, ETA 9:10a
TRK-07D. Okafor2x restroom, weekly serviceKaty, Site 12Serviced 7:58a
TRK-02J. Salas240ft temp fence, setGrand Pkwy segment BOn site
TRK-05A. Nguyen20yd roll-off, swapPearland, Broadway StScheduled 1:30p
The board sends the ETA text at assignment, en route, and drop.
Your customers stop calling.
The board sends ETA texts on its own at assignment, en route, and drop. The 9pm text to your personal phone becomes the board’s job, not yours.
The arithmetic
You already know these numbers.
No vendor percentages, no case-study math. The figures below are yours, from last month. Fill in the blanks and the argument makes itself.
Idle assetsassets sitting at finished sites × daily rate × days before anyone notices= $ a month
Unbilled feesoverage and damage events last month × the fee that never reached an invoice= $ a month
Re-keyed hourshours a week moving jobs between systems × a dispatcher’s hourly cost= $ a month
After-hours phonecustomer texts answered after 6pm × what an hour of yours is worth= $ a month
Run any line with your real figures: Split-system cost calculatorRevenue-leak estimatorIdle-asset utilization calculator
The total is what running two or three separate systems costs you today. It is the number to hold this product against.
Why this exists
Field-service software doesn’t know about asset placement.
Jobber and Housecall Pro are built around visits: a tech shows up, does the work, leaves. A dumpster that sits on a site for two weeks isn’t that job. ServiceCore and Docket live on the waste side; fencing and containers aren’t their lane.
ProDispatch is built around the one thing everything you rent has in common: an asset placed at a site for a stretch of time. That is why cans, fences, and restrooms fit on the same board.
The vendor question
You’ve heard the one-platform pitch before.
Fair. The claim only counts if it survives your operation: every asset type on one board, a driver in a dead zone, a QuickBooks file that already balances. Bring the worst week you’ve had this year and test the claim against it on the call.
What you can count on
The terms are simple on purpose.
- SMS included, not bolted on as an upsell.
- QuickBooks Online sync included.
- Founder-led onboarding, not a ticket queue.
- One conversation, not a quote gauntlet.
Bring last month’s numbers.
30 minutes with the founder, no deck. We run your arithmetic together, and you keep the spreadsheet either way.
Book a call with the founder