How to add autonomous vehicles to an existing taxi fleet
Adding autonomous vehicles to an existing taxi fleet means running two kinds of cars in one operation: human-driven vehicles that keep earning today, and driverless vehicles that join the same dispatch queue as the technology and regulation allow. The integration path has four stages: audit the current operation, deploy a fleet platform that handles hybrid dispatch, upgrade the depot for electric charging and sensor care, and retrain part of the staff from driving to fleet operations. Taxi companies that follow this path keep their two strongest assets, local demand and local infrastructure, while the driving itself gradually shifts to machines. The prize is the cost curve: analyst models put robotaxi operating costs on a path toward $0.25 to $0.35 per mile, far below the $1.50 to $2.00 per mile of human-driven ride-hail, and the operators who integrate early capture that margin first.
Why integrate instead of waiting it out?
Robotaxi services grew from novelty to volume in about two years: Waymo went from roughly 50,000 weekly rides in May 2024 to 500,000 by March 2026, and Apollo Go carried 3.2 million fully driverless rides in the first quarter of 2026 alone. When this wave reaches a new country, the local companies that already run dispatch, depots and customer relationships are either partners for it or bypassed by it. Integration is how an incumbent stays the operator instead of becoming the displaced party.
Stage 1: what does a fleet audit cover?
The audit maps the operation you already have, because the hybrid fleet inherits it. Four questions matter:
- Zones and demand: where do orders concentrate by hour, and which zones have the simple road patterns autonomous vehicles handle best?
- Dispatch flow: how do orders reach cars today, and through which app or switchboard?
- Depot reality: parking, power capacity, space for chargers, cleaning line.
- Economics: cost per kilometer of the current fleet, as the baseline the autonomous cars must beat. Our breakdown of robotaxi economics shows which numbers to collect.
Stage 2: how does hybrid dispatch work?
The core move is putting human-driven and autonomous vehicles into one queue under one fleet management software layer. The platform routes simple, well-mapped trips to autonomous cars and keeps complex ones, airport runs with luggage help, unmapped villages, unusual pickups, with human drivers. Riders see one service; the platform decides which kind of vehicle serves each order.
Hybrid dispatch also de-risks the rollout. The autonomous share starts at a few percent of orders inside a small geofence and grows only as reliability data accumulates. No customer-facing switch gets flipped; the mix shifts gradually.
Stage 3: what changes at the depot?
Robotaxis in current deployments are electric, so the depot gains chargers, a scheduled cleaning line (nobody wipes the seats between riders anymore) and a calibration bay for sensors. Charging windows get planned against the demand forecast so vehicles top up during quiet hours. The full daily cycle, charging, cleaning, maintenance, sensor checks, is covered in charging and depot planning.
Stage 4: what happens to the people?
Roles shift rather than disappear at fleet level. Dispatchers become fleet operators watching telemetry. Experienced drivers make strong remote assistance operators, the people who answer a car's question when it meets a strange intersection, because they know the city's edge cases. Mechanics add high-voltage and sensor skills. In Waymo's published model, remote support runs near 70 assistants for roughly 3,000 vehicles, which shows the shape of the new staffing pyramid: fewer people per car, higher skill per person.
What does the sequence look like end to end?
| Stage | What runs | Exit criterion |
|---|---|---|
| Audit | Current fleet, measured | Zone map, cost baseline, depot plan |
| Platform | Human fleet on the new dispatch | Dispatchers fluent, data flowing |
| Pilot AVs | Small geofence, few vehicles | Stable utilization, clean incident log |
| Scale | Growing AV share in the mix | Unit economics beat the human baseline |
The platform stage deserves emphasis: adopting the fleet software before any autonomous vehicle arrives means the organization learns the tools on familiar cars, and the eventual AV pilot lands in a running operation. Timing depends on the market; our analysis of when robotaxis reach Georgia maps the preconditions for one specific country, and the broader digitalization story is in taxi digitalization in Georgia.
Where aiTAXI fits
aiTAXI is a robotaxi fleet management platform by aiNOW (Tbilisi, Georgia), built around exactly this integration path: hybrid dispatch, telemetry, remote assistance and depot planning in one console that an existing taxi company can adopt before its first autonomous vehicle arrives. The platform is in early access, and the robotaxi fleet management platform pilot program is open for Georgian taxi operators.
FAQ
Do I need to buy autonomous vehicles to start?
No. The audit and platform stages run entirely on the existing human-driven fleet. The point is to be operationally ready before the vehicles are purchasable in your market.
Will autonomous cars replace all my drivers?
Not in any realistic planning horizon. Hybrid fleets keep human drivers for complex trips and peak coverage for years, while some staff move into fleet operations, remote assistance and depot roles.
Which vehicles will the platform support?
A vehicle-agnostic platform integrates with whichever AV systems enter your market. Committing to a fleet layer does not lock you into one car manufacturer.
What is the first concrete step for a taxi company?
A fleet audit: zones, demand curves, dispatch flow, depot capacity and the cost baseline. It costs planning time, produces the integration roadmap, and every later stage builds on it.