Adam Hainsworth-Potter

Addooco is an MSP, and this project was tied to a new joint venture with a dispatch software provider. The business needed a production-ready telephony platform to support the new company, while also proving it could build and run software products alongside its existing managed IT and infrastructure services. If it failed, Addooco would have missed a strategic growth opportunity.

As Head of Software Engineering, I was brought in to get the project off the ground, initially as the sole engineer on the management platform. I owned the architecture, coordinated delivery between Addooco, the telephony contractor and the dispatch vendor, and built the system so it could be handed over safely to a new internal team I hired and setup. A major constraint was that both upstream systems were still being developed, so schemas were changing throughout delivery.

I built the multi-tenant management platform in Laravel and PHP, with a React frontend using Inertia.js. It integrated with the core telephony system via API to manage resources like agents, queues and routing logic, and used webhooks plus Redis caching and queues to support low-latency call handling. I also integrated the dispatch API for bookings, estimates and customer data, exposing this to the IVR AI through an MCP server. I set up GitHub Actions CI/CD, Sentry, protected release workflows, and a 95%+ automated test suite including browser smoke tests.

The platform reached MVP in one year. It handled 300+ concurrent calls per organisation, with clear headroom to scale further.

Veezu were heavily reliant on an external agency to maintain their driver management system, which led to high ongoing costs, limited technical control, and slow feature delivery. As the business expanded rapidly through UK-wide acquisitions, the lack of development velocity became a blocker for compliance, onboarding, and operational scale.

I was brought in as Lead Software Engineer to establish an internal engineering function and deliver a new in-house platform. Initially working as the sole engineer alongside a key Director, I owned the architecture, delivery plan, and the foundations for ISO27001-aligned engineering processes before growing the team with permanent and contract support.

I built a custom Laravel and PHP platform backed by MySQL, covering backend logic, an internal admin portal for staff, and a driver-facing web application plus mobile application. The system automated onboarding, legal document upload and verification, agreement acceptance with audit history, earnings visibility, and driver invoicing, replacing spreadsheet-based workflows that could not scale. I wrote a full suite of unit and feature tests using Pest which protected critical onboarding and invoicing workflows, and supported safe iteration. I also integrated iCabbi to synchronise dispatch and driver data, and Zendesk to enable in-app messaging and support.

The platform supported 20,000+ active drivers, enabled continued acquisition-led growth without proportional increases in staffing, and removed dependency on the external agency, saving over £200,000 per year. The build ran through alpha and beta phases, with full migration completed within three months of launch.

When I joined Can Studios, they had recently lost a senior Laravel engineer, which created a knowledge gap and increased delivery risk across their Training Post eLearning platform. At the same time, their largest and most commercially important client needed bespoke functionality tied to their own systems and workflow, with a real risk of churn if it could not be delivered.

My responsibility was to keep the existing multi-tenant platform stable, while delivering the client-specific features without impacting other customers or introducing a forked codebase. I also supported infrastructure upgrades, as the platform was running on Ubuntu and MySQL versions approaching end of life.

I proposed and implemented a tenant-specific extension approach using a bespoke Laravel package. The package was conditionally loaded per Training Post instance, ensuring the core Laravel application remained independent and unaffected for other clients. I built the module as a self-contained feature set with its own routes, controllers, views, migrations and background jobs.

The package included a secure REST API integration, SAML SSO, data mapping into existing records, and custom export tooling. Quality was supported through PHPUnit tests and Laravel Dusk browser tests, alongside close collaboration with QA and weekly client check-ins.

The result was a stable delivery cadence, a retained key client with contract renewal, and a platform moved onto supported Ubuntu and MySQL versions for ongoing security patching.