About

Eighteen years in aviation software taught me what not to build.

I spent the first part of my career building the previous generation of this software — operational platforms for regional airlines and aviation operators. I built it, scaled it to production, and exited. Then I watched what came after.

What I learned is that the architecture was always the ceiling. Monolithic systems on RDBMS foundations can be extended and re-skinned, but they cannot be reinvented. Every new customer becomes a migration project. Every demand surge becomes a risk event. Every integration becomes a custom build that someone else has to maintain.

That's not a vendor problem. It's a structural one. In a distributed, AI-shaped world, it's a dead end no amount of new paint fixes.

Neil Middleton — Co-founder, UnityTrip

So I built UnityTrip from a clean sheet, deliberately the opposite:

Event-sourced and distributed

Not a single contended database that becomes the bottleneck for everything.

Multi-tenant from day one

Not a model where every new customer is a migration project.

Integration-first

Not a walled garden that makes every external integration a custom build.

Built to scale on demand

Not a system that scales by buying a bigger box and hoping.

The Market

A narrow world. An enormous, fragmented opportunity.

Aviation operations is a narrow world. Corporate travel is enormous — and chronically fragmented. Large organisations run separate systems for commercial booking, leased and chartered transport, expense, and approvals, with no single source of truth and budget leaking through the gaps.

The companies that own and operate transport assets are exactly the ones tourist-grade travel software was never built to serve. That's the gap I built UnityTrip to fill.

How We Work

Consultancy amplified by frontier AI.

UnityTrip is built and delivered by a deliberately small team applying frontier AI to deep domain experience. The model is a commodity input; the judgment that directs it — the aviation operations background, the architecture, a working command of each client's own vocabulary — is not, and the two cannot be separated without the value collapsing.

The doctrine is simple: frontier AI at build time, determinism at run time. AI amplifies the consultancy that designs, configures, and delivers — which is why modules arrive in weeks rather than the months a large consultancy quotes — while the engine that decides bookings stays deterministic, auditable, and explainable. No AI guesses at booking time.

Co-founder

UnityTrip runs in production today at enterprise scale in energy and resources, managing multi-modal workforce travel — booking, approvals, and expense — end to end. The platform first ran under the CorpFleet name (corpfleet.app) — one product, one team, one codebase — and I'm now taking that capability to the broader market as UnityTrip.

UnityTrip is founder and customer funded, cash-flow positive on long-term contracts — no debt, no VC, and no upstream balance-sheet event that sunsets the product.

UnityTrip is a member of the Microsoft AI Cloud Partner Program (ISV Success), hosted on Microsoft Azure and available on the Azure Marketplace.

Neil Middleton

Co-founder and CEO

LinkedIn →

Co-founder

Introducing distributed systems into travel is harder than it looks — many have tried and found the data model fights back. Benjamin designed UnityTrip's architecture from distributed-systems-first principles, which is why it holds in production where others haven't.

Benjamin Kappel

Co-founder and Principal Architect

Co-founder

Cindy leads business development and investor relations, connecting UnityTrip with the operators, partners, and investors who stand to gain most from the platform.

Dr Cindy de Villiers

Co-founder, Business Development and Investor Relations

LinkedIn →