iCabbi and Cordic split UK + Ireland taxi dispatch installed base in different ways — iCabbi dominates Ireland and London corporate work, Cordic dominates UK regional Hackney and chauffeur work. This comparison covers feature parity, pricing posture (both quote-only multi-year), Cordic's distinctive vehicle-class enforcement gap that drives most Cordic migrations, and the structural friction profile of moving off either platform to a modern alternative like TaxiCloud.
1. Market positioning
iCabbi (Dublin, founded 2010) anchors Irish dispatch market and London corporate-account work. Cordic (UK regional, founded earlier) anchors regional Hackney + chauffeur work — strong in Edinburgh, Glasgow, Manchester chauffeur tier. Both quote-only multi-year contracts; neither publishes pricing.
iCabbi's 2026 product direction emphasises corporate-account integration; Cordic emphasises chauffeur-class dispatch. Both lag modern alternatives on AI Copilot integration.
2. Vehicle-class enforcement gap
Cordic's most-cited migration trigger across our pilot fleets is structural vehicle-class enforcement — Cordic flags vehicle class as dispatcher-text-notes rather than structural records. Premium S-Class bookings cross-assign to E-Class vehicles when dispatchers miss the class flag during peak load. Modern dispatch (TaxiCloud) makes vehicle-class enforcement structural at the assignment step.
iCabbi handles vehicle-class better than Cordic — class is a structural attribute on iCabbi — but lacks the AI Copilot soft-optimisation layer that surfaces explainable assignment recommendations.
3. Migration profile
iCabbi → TaxiCloud: 7-10 working days. Data export robust; iCabbi's data model maps cleanly. Cordic → TaxiCloud: 6-9 working days with vehicle-class structural promotion as a key migration scope. Both migrations available white-glove on TaxiCloud Pro and above.
About the author
Regan Marshall
Lead, Operator Strategy, TaxiCloud
Regan Marshall works with UK and Ireland fleet operators on dispatch strategy, AI Copilot adoption, and migration planning. Reach out at regan@taxicloud.ai.