The global fleet management market is projected to exceed $52 billion by 2030. It is also one of the most fragmented software markets in enterprise technology, with hundreds of point solutions serving individual operational domains.
Electrification is about to reshape it.
The pattern: complexity multiplication creates new layers
Every major technology shift in enterprise software follows a pattern. When operational complexity multiplies beyond what existing tools can handle, a new layer emerges. Not a better version of the old tools. A coordination layer that sits above them.
Cloud computing created the cloud orchestration layer (Kubernetes). Microservices created the API gateway and service mesh. Multi-cloud created the infrastructure abstraction layer.
Fleet electrification is creating the fleet orchestration layer.
Diesel fleets had one primary operational variable: assign vehicle to route. Electric fleets have five: assign vehicle to route, manage state of charge, optimise charging schedule, balance energy costs, and coordinate depot bays. The number of operational variables has multiplied. The existing tools were not architected for this.
Why incumbents cannot build this
The natural question is: why will existing fleet management vendors not simply add orchestration features?
The answer is architectural. A scheduling platform is designed around the scheduling domain. Its data model, its user interface, its optimisation algorithms, all built for trip planning, blocking, and runcutting. When it adds a charging module, that module serves the scheduling workflow. It optimises charging to fit the schedule, not to coordinate charging with depot allocation, maintenance, and energy costs simultaneously.
The same applies in reverse. A charging management platform is designed around charger hardware. When it adds depot features, those features serve the charging workflow.
Orchestration requires a fundamentally different architecture: a unified data model that spans all operational domains, an event-driven system that updates in real time across every connected system, and an intelligence layer that reasons across the full operation.
That is not a feature. It is a platform.
The market opportunity
The EU Clean Vehicles Directive mandates 45% clean vehicle procurement by 2025, rising to 65% by 2030. The UK targets a fully zero-emission bus fleet by 2035. These are contractual obligations with penalty clauses, not aspirational targets.
Every electric bus procured under these mandates needs operational software that legacy tools were never built to provide. Charging optimisation, energy cost management, SoC-aware allocation, and depot orchestration are new requirements that emerged with electrification.
The orchestration layer is not replacing existing fleet management spending. It is adding a new layer on top. Operators will continue to use scheduling platforms, telematics, and maintenance systems. They will add orchestration to connect them.
The autonomous fleet dimension
The long-term thesis is even larger. When autonomous buses arrive, every decision currently made by a human driver moves to software. Depot allocation, route adjustment, charging coordination, maintenance scheduling. All become software problems.
We mapped 21 distinct capabilities required to run an autonomous fleet end-to-end. Eleven sit in the orchestration layer. Not in the vehicle. Not in the scheduling system. In the layer that coordinates everything.
The companies building the orchestration layer today are not just solving a current operational pain point. They are building the operating system that autonomous fleets will run on.
First movers and category creation
Every platform shift creates a category leader. In cloud orchestration, it was Kubernetes. In API management, it was a category that emerged once the integration problem became universal. In fleet operations, the shift is electrification, and the category is orchestration.
The window for category creation is open now. Fleet electrification is accelerating. The operational complexity gap is widening. The orchestration layer does not exist yet in most operations.
Greenbay is building it. We are live in production, expanding across the EU and UK, and working with a founding team that has over 15 years of fleet technology experience across routing, scheduling, autonomous vehicles, and demand-responsive transit.
The category is being created. The question is who will define it.