iCabbi vs Autocab — deep dive on UK + Ireland taxi dispatch incumbents

iCabbi (Dublin-headquartered, founded 2010) and Autocab (Manchester-headquartered, acquired by Uber in 2020) share more than they differ. Both are quote-only with multi-year contracts; neither publishes pricing on the website. Both ship rule-based auto-dispatch rather than generative AI Copilot. Both have dense partner ecosystems for booker-channel integrations. Both have UI patterns rooted in 2014-era information density rather than modern dispatch console aesthetics. The two systems are commodity-equivalent for most operators.

Where they diverge structurally is ownership and roadmap. Autocab being Uber-owned shapes the platform direction toward Uber-feeder integration and Uber-account-side commercial relationships. iCabbi remaining independent of any ride-hailing parent gives it operating freedom that some operators value. Both, however, are unequivocally legacy systems by 2026 standards.

Both iCabbi and Autocab run quote-only multi-year contracts typically running 24-36 months with 4-8% annual escalation clauses. Operator-reported run-rate costs at 50 vehicles range from £1,200-£1,800/month all-in once setup, integration, and per-driver fees net out — vs TaxiCloud's published Pro Max at £349/month for the same fleet size. The pricing transparency gap is one of the most-cited migration triggers in modern alternative evaluation.

iCabbi typically requires 7-10 working days for cutover; Autocab 8-10. The full migration deep-dive content is at /migrate/icabbi and /migrate/autocab covering the data export path, parallel-run window, and competitor-specific gotchas. Most operators evaluate with a parallel-run weekend on the airport or executive segment first.