The same stack in every office
A spreadsheet for placements. A legacy waste tool bought years ago. QuickBooks. A phone number the customers have memorized. Every operator I sit with runs some version of it.
About
The person you talk to is the person who builds it.
ProDispatch has one founder, a working board, and a handful of operators who let me stand in their dispatch mornings. This page sticks to what is true right now.
Why this exists
One dumpster. Three tabs and a personal cell.
Watch a dispatcher move a single roll-off. The placement lives in a spreadsheet. The truck lives on a whiteboard somebody photographs at 6 a.m. The invoice lives in QuickBooks, and the customer lives on the dispatcher’s personal phone. Four systems for one asset, and none of them agree by lunch. That morning is the whole reason this company exists.
Assets that sit are invisible
Field-service software thinks a job ends the day it starts. A roll-off that sits on a site for three weeks is not a job, it is a placement, and most tools have no word for it.
The day travels by text
Routes go out over text into county roads where texts do not arrive. The driver guesses. The office finds out at 5 p.m. what actually happened at 9.
The founder
No layer between you and the person who writes the code.
I build ProDispatch. The board, the field app, the texting, all of it so far. I got here the slow way: sitting in dispatch offices, watching sharp operators run real fleets on tools that ignore half of what they rent. The industry filed them under niche and moved on. That read is wrong, and this product is the argument.
When you book a call, it is with me. When you email, I answer. When the board gets something wrong, the person who hears about it is the person who can fix it.
How the work happens
Operators run their real day on it. The board answers for itself.
Bring the ugly day
Founding operators bring real routes, real trucks, real edge cases. Nobody demos a script.
The loop is weekly
What breaks on a Tuesday call is on the list that week. Short loop, on purpose.
Shown, not told
Ask what the product does and you get the board on screen, moving. Not a slide about it.
Read this before you trust us
What this page does not have.
Software sites earn trust with a team grid, a logo wall, and a press page. This one has none of those, and faking them would be worse than the gap.
A team grid
One founder. A team page with a single face is decoration, so there is no team page.
A customer logo wall
Founding operators run the product in private while it earns its keep. Logos appear when they say so, not before.
A funding announcement
Money is not proof the board works. The board moving is proof the board works.
A company history
The history is short and you are reading it.
What is here instead: a board you can watch, and a founder you can call.
Bring the day that breaks your setup.
Thirty minutes with the founder, no deck. Walk your worst dispatch morning through the board and judge what you see.
Book a call with the founder