Coming later is not the same as missing

Software demos love the word "roadmap". A slide full of integrations. A promise that DVLA will "just sync". A payroll feed that will "plug in soon". The desk leaves the meeting thinking the product already does those things. Three months later, the real work still lives in inboxes and spreadsheets — because the live product never matched the pitch.

For UK HGV and industrial agencies, that gap is expensive. You do not have spare capacity to absorb it. You have consultants who need to place drivers this afternoon.

Day one still has to run the desk

A recruitment system for this niche has a job before it has a polished automation story. Candidates need a way to apply. Licence and Right to Work documents need somewhere to land. Workers need a record that holds licence categories, CPC and tachograph expiry, and check status in plain view. Clients and jobs need to stay separate from candidate data. Placements need to be schedulable without a whiteboard or a Friday-night spreadsheet.

That is the spine. If that spine is weak, no API logo on a marketing page will save Monday morning.

Haulbase is being built so that spine is live at launch: job board, registration, worker, client, and job management, plus scheduling and placement tracking. DVLA and Right to Work status are tracked manually on the worker, with documents uploaded and reviewed in one place. You see status next to the person. You do not chase a PDF through last month's email to answer a basic question.

That is not "half a product". It is the part agencies actually use every day — honest status on one record, inside the same system as jobs and placements.

What "coming later" actually means

Automated DVLA licence check API integration comes later. Automated Right to Work identity verification comes later. Payroll and umbrella company integrations come later.

Those are real pieces of work. They are also the pieces most vendors blur into the present tense. We would rather name them as later than sell a product that does not exist yet.

Manual status tracking at launch still matters. A consultant can record that a DVLA check was done, keep the document on the worker, and see Right to Work renewal dates without opening three tools. The desk can trust "available" a little more because compliance is on the record, not adjacent to it in a side tracker. Automation should reduce typing. It should not be the only reason the data model finally makes sense.

The same honesty applies commercially. PAYE and umbrella placements are different things in the product from day one. That is not the same as live payroll feeds or umbrella company APIs on day one. The model comes first. The integrations follow. Pretending otherwise is how agencies buy a roadmap and keep Excel for the truth.

Why agencies get sold the future instead of the present

Generic CRM and Salesforce-shaped pitches lean on configuration and future connectors. The demo shows custom fields. The proposal mentions "DVLA integration" and "Right to Work verification" as if they were switches. Underneath, the platform still thinks in generic candidates and inventable tags until someone teaches it otherwise — often at several thousand pounds of consultancy, then again every time the process changes.

When the automation slips, the workaround returns. Status drifts back into inboxes. CPC expiry returns to a spreadsheet. The placement board stays in Drive because the CRM version never felt safe under pressure. The roadmap did not fail because the team was lazy. It failed because the live system never became the place the desk trusted.

Pre-configured for HGV means the opposite sequence. Licence categories, compliance fields, clients, jobs, and placements are already shaped for how the desk works. Then automation layers onto a record people already use — not onto a blank canvas you were meant to believe in until the APIs arrived.

Built for the desk that feels the gap first

Haulbase is built for UK HGV and industrial recruitment agencies — not enterprise licensing theatre dressed up as a niche product. For that desk, "coming later" only works if "live at launch" already removes the scavenger hunt: one pipeline from job board to placement, compliance on the worker, nothing useful typed in twice.

Built with real agency back-office experience — ten years of watching renewals, checks, and placements drift into whatever tool was fastest that day. The product should start closer to that reality than a consultant's best guess after renaming objects on a generic platform.

UK-hosted, with UK GDPR as a baseline, not an afterthought. Still pre-launch. The waitlist is how you hear first as we get closer — and how agencies help decide what deserves to move from later into sooner.

Clear now, clearer later

Drivers will still need checks. Documents will still expire. Integrations will still matter. What you should not need is a sales deck that treats unfinished automation as if it were already running your Monday.

If you have bought a roadmap before and kept the spreadsheet anyway, you're the reason we're building Haulbase this way.