Veezu took driver management in-house and saved £200,000 a year

Agency dependency was slowing acquisition-led growth

Veezu was growing quickly through UK-wide acquisitions, but its driver management system was still dependent on an external agency. The business needed control over software that sat right in the middle of driver onboarding, compliance, invoicing, and support.

That created three problems at once. Ongoing costs were high, feature delivery was slow, and the business had limited technical control over a system that touched compliance, onboarding, invoicing, and driver communication.

The process around the system was not scaling either. Teams relied on spreadsheets and manual checks to manage driver records, legal documents, agreements, payment visibility, and support conversations. That might work for a smaller fleet. It does not work cleanly when the business is acquiring operators and needs consistent processes across thousands of drivers.

Building the platform and the engineering function

I was brought in as Lead Software Engineer to establish an internal engineering function and deliver a new in-house platform.

At the start, I worked as the sole engineer alongside a key Director. I owned the architecture, delivery plan, and early engineering standards, then helped grow the team with permanent and contract support once the platform had clear foundations.

Veezu needed more than Laravel delivery. They needed someone who could build the product, reduce agency dependency, set up safer engineering habits, and make decisions that would stand up to ISO27001-aligned processes.

An in-house Laravel platform for driver operations

I built a custom Laravel and PHP platform backed by MySQL.

The system covered backend business logic, an internal admin portal for staff, a driver-facing web application, and a mobile application. It automated onboarding, legal document upload and verification, agreement acceptance with audit history, driver earnings visibility, and invoicing.

I also integrated iCabbi so dispatch and driver data stayed synchronised, and Zendesk so support messaging could happen inside the driver experience rather than being handled as a disconnected channel.

The critical workflows were protected with unit and feature tests using Pest. That mattered because onboarding and invoicing are exactly the parts of the system where quiet mistakes become expensive.

Replacing a live dependency without copying the mess

The main challenge was replacing a live operational dependency without creating a bigger one.

The platform had to absorb real business rules from multiple acquired operators, while still giving Veezu a cleaner shared process. A direct copy of every local workaround would have preserved the mess. A neat greenfield model would have ignored how the business actually worked. The right answer sat between those two.

Migration was another risk. Driver records, documents, agreements, and payment data had to move into the new platform without losing trust from staff or drivers. That meant alpha and beta phases, careful iteration, and enough test coverage to keep critical workflows stable while the product changed.

The engineering process mattered too. Bringing the work in-house only saved money if the new team could safely extend the system afterwards.

More control, faster growth, and £200,000 saved each year

The platform supported more than 20,000 active drivers and removed Veezu’s dependency on the external agency, saving more than £200,000 per year.

It also gave the business more control over a platform it depended on every day. Continued acquisition-led growth no longer needed the same proportional increase in admin work, and the full migration was completed within three months of launch.

Our Laravel platform now handles over 20,000 active drivers and saves us over £200,000 a year on external agency costs. It gives us more control over a system the business depends on.