We managed permit books for a living. Then we built one.
VPB comes out of a working trucking compliance consultancy, not a startup accelerator.
In short
VPB was built by a working trucking compliance consultancy, not a software startup. The team managed permit books for client fleets (chasing renewals, assembling driver files, standing at roadside) and built VPB for their own clients first. The document categories, required-document logic and roadside flow come from that practice.
The tool we kept wishing existed.
For years, our consultancy did fleet compliance the way everyone does it: binders, spreadsheets, renewal calendars, and phone calls that start with "do you have a current copy of…"
We watched good operations eat fines for documents that were sitting, expired, in a cab. We watched dispatchers spend afternoons re-sending the same insurance cert. We looked for software that matched how compliance work actually happens, and everything we found was either a bloated fleet-management suite or a file cabinet with a login.
So we built VPB. First for our own clients. Then, when it held up, for everyone else.
Why a consultancy-built tool is different.
We know the workflow, not just the concept.
Every screen in VPB maps to a job someone actually does, because we've done it.
We speak safety manager, not product manager.
The app uses the words your people already use.
We run our own clients on it.
VPB isn't a demo for us. It's how we work.
The tool comes with people behind it.
Compliance questions don't stop at software. Ours doesn't either.
Our values
Do the job right.
Compliance doesn't reward creativity. It rewards being current, complete, and findable in ten seconds.
Keep it simple.
Every feature earns its place. If it doesn't help a fleet stay compliant or a driver pass an inspection, it's not in the app.
Answer the phone.
We're trucking people. When you call about a permit problem, you get someone who knows what an IFTA sticker is.