Keep the O-licence, and keep
the margin.
Tachograph analysis, drivers' hours, walkaround checks and maintenance records — plus the job and invoicing side, on one system.
We've lived this.
You already know where the money leaks and where the licence risk sits. Usually they are the same jobs.
Tacho cards get downloaded late, infringements are spotted weeks after the event, and by then the conversation with the driver is pointless.
Walkaround checks are on paper in the cab, so a defect reported on Monday reaches the workshop on Friday, if at all.
Inspection and brake-test due dates live in a spreadsheet that one person maintains and everyone else hopes is right.
Subcontracted loads are agreed on the phone, and the POD, the rate and the invoice never quite reconcile.
What we'd build for you
Tacho and drivers' hours engine
Digital tachograph files parsed automatically, drivers' hours and working-time rules applied, infringements surfaced while they still matter — not a month later.
Roadworthiness evidence pack
Walkaround checks with photo defects straight to the workshop, inspection and brake-test scheduling with due-date alerts, and a complete audit trail for a DVSA visit.
Jobs, subcontracting and PODs
Loads in, allocation out, subcontractor rates recorded against the job, POD captured on the driver's phone and attached to the invoice automatically.
Quote to invoice, VAT correct
Rates, surcharges and waiting time calculated on the job, invoices raised per job or on a monthly statement, and a clean two-way sync with your accounts package.
Real numbers,
not a pitch deck.
Fixed prices.
No surprises.
Your brand, your domain, your app-store accounts.
6–12 weeks, scoped around your traffic office and your customers.
Tacho, hours, checks and maintenance, alongside your existing system.
Verifiable, not aspirational.
Honest answers.
Where we're genuinely uncertain we say so — and we ship a working spike in 2 weeks for you to test before you commit.
Do you parse real tachograph files, or is this a form someone types into?+
Real files. The engine reads driver-card and vehicle-unit downloads and applies drivers' hours and working-time rules to what it finds. It is the same engine running in our own compliance platform.
Are you a DVSA Earned Recognition validated IT supplier?+
No, and we will not imply otherwise. The engine does the work Earned Recognition asks for, but validation requires a real operating haulier to back an application, and the KPI reporting layer is not built yet. If becoming that reference operator interests you, that is a conversation worth having — the first one gets a serious discount.
We already use a tacho analysis bureau. Does this replace them?+
It can, or it can sit alongside them. Plenty of operators keep the bureau for the analysis and use us for everything the bureau does not touch — checks, maintenance, driver records, jobs and invoicing. We would rather sell you the half you are missing than rip out something that works.
What happens to the data if we leave?+
You export it, and the code is in your repository from the first commit if you had a bespoke build. No escrow, no hostage-taking.
Find the infringement
while it still matters.
Fifteen minutes on the phone. Tell us your fleet size and how you handle tacho today, and we will tell you what we would build and what it costs.