From dispatch apps to autonomy: taxi digitalization in Georgia
Taxi digitalization in Georgia has moved through two eras and is entering a third. The first era ran on street hails, phone dispatchers and negotiated fares. The second arrived with ride-hailing apps, which made Bolt the dominant platform in the country and turned Tbilisi into an app-first taxi market with fares local guides put around 1.5 to 2 GEL per kilometer. The third era is fleet software: telemetry, data-driven dispatch and operations tooling that prepares a company for vehicles without drivers. The market is large enough to matter, with 18.4% of all drivers in Tbilisi working as taxi drivers and more than 85,000 registered taxis. Each era compressed faster than the one before it, and the companies that led each transition took the passengers. This article traces the three eras and shows what the third one asks of a Georgian fleet owner.
What did the app era change in Georgia?
Apps standardized pricing, cut the negotiation, and made demand measurable for the first time. Tbilisi formalized the supply side through its category A permit system, and drivers organized their whole workday around app queues. The structural lesson from that decade: platform shifts in this market happen fast and completely, because both riders and drivers switch for small, immediate gains. A market that switched once will switch again.
What is still analog inside an app-era fleet?
The rider-facing layer digitized; the fleet itself mostly did not. Vehicle condition lives in the driver's head. Fuel and maintenance decisions are personal habits. Utilization between orders is guesswork. A fleet owner with 50 cars usually cannot answer basic questions: cost per kilometer per vehicle, idle share by hour, which zones earn and which burn fuel. That data gap is the third era's work, and closing it is worth doing even with zero autonomous vehicles on the horizon, because measured fleets run cheaper than intuited ones. The tooling is described in our guide to robotaxi fleet management software, which manages human-driven fleets with the same modules.
Why does fleet software decide the autonomous era?
Robotaxis arrive as a software-plus-operations business. The global operators prove the shape: Waymo coordinates 500,000 paid rides per week through a fleet platform, and Apollo Go's export move into South Korea shows the technology travels through partnerships with local operations. When that wave reaches Georgia, the driving system will come from a global vendor, and the local question becomes: which Georgian company can actually operate a mixed fleet, with dispatch, telemetry, a depot and trained staff? The answer is decided years earlier, in the fleet-software era. The preconditions and signals for the Georgian market specifically are mapped in when robotaxis reach Georgia.
What does the era transition look like in practice?
| Era | Dispatch | Fleet knowledge | Who wins |
|---|---|---|---|
| Street and switchboard | Phone dispatcher, street hail | None, per-driver | Whoever owns the phone number |
| App era (today) | Ride-hailing platform queue | Rider side digital, fleet side analog | The dominant app |
| Fleet-software era | Hybrid queue, human plus AV ready | Telemetry, cost per km, zone data | Operators with data and depots |
The practical sequence for a Georgian fleet owner mirrors the integration path in adding autonomous vehicles to a fleet: audit the operation, adopt the platform on today's human-driven cars, plan depot power, and let the autonomous share start at zero. Every stage pays for itself in the current business through utilization and cost visibility, which removes the usual objection that preparing for autonomy is speculative spending.
Where aiTAXI fits
aiTAXI is a robotaxi fleet management platform by aiNOW (Tbilisi, Georgia), built in Georgia for this exact transition: a fleet console that runs today's human-driven fleet and is designed to add autonomous vehicles when they reach the market. The robotaxi fleet management platform is in early access, and the pilot program recruits Georgian taxi companies that want to lead the third era rather than react to it.
FAQ
Why should a Georgian fleet owner care about robotaxis now?
Because the preparation is profitable on its own. Fleet telemetry and data-driven dispatch cut costs in the current business, and they happen to be the same infrastructure the autonomous era requires.
Did apps kill the traditional taxi business in Georgia?
They absorbed it. Drivers moved onto app queues and fleet owners adapted. The same absorption logic applies to the next shift, which is why being early to the fleet-software layer matters.
What is the first digitalization step for a small fleet?
Measurement: cost per kilometer per vehicle, utilization by hour, demand by zone. A month of clean data changes fleet decisions immediately and builds the baseline for any autonomy conversation.
Will the dominant ride-hailing app also run the robotaxis in Georgia?
Possibly, and global patterns suggest partnerships between platforms, vehicle vendors and local fleets. Local operators with depots, data and trained staff hold a seat at that table; unprepared ones do not.