unthinkable
Case study · A consortium of 180+ limousine and taxi operators, Qatar

Passengers in Qatar book a taxi in a few taps and watch it arrive, from operators who own the app.

Qatar's limousine operators wanted passengers to book their cars directly, at a fair fare, with drivers paying only a small commission instead of the rising cut taken by multinational ride-hailing apps.

QatarPublic transit & mobility (live tracking, ticketing, ride-sharing)

What changed

10,000+taxis and drivers registered (as reported)
180+travel businesses associated (as reported)
100,000+passengers served (as reported)
100+bookings handled per minute (as reported)
40%lower operational costs using Amazon EKS (as reported)
77%less developer effort to launch or update the app, through microservices (as reported)
What stood in the way

What stood in the way.

What stood in the way
  • Most of Qatar's limousine businesses relied on multinational ride-hailing apps that raised commissions and cut fares, so margins shrank and some operators closed.
  • More than 180 operators formed a consortium to run their own booking app, and needed a partner to help shape the product, not only code it.
  • The platform had to grow as more travel businesses joined, without the consortium paying for capacity up front.
What changed
  • 10,000+taxis and drivers registered (as reported)
  • 180+travel businesses associated (as reported)
  • 100,000+passengers served (as reported)
  • 100+bookings handled per minute (as reported)
  • 40%lower operational costs using Amazon EKS (as reported)
  • 77%less developer effort to launch or update the app, through microservices (as reported)
What we built

What we built.

  • Native Android and iOS apps for passengers: schedule a ride, book for someone else, add several drops, see the driver's details and rating, and review past trips and fares.
  • Native Android and iOS apps for drivers: register with licence and vehicle papers for admin approval, go online, accept a request within one minute, navigate to the rider and see the ETA.
  • Matching that picks the nearest available driver within a set radius, breaks ties on rating and rides served, and widens the search when no one is near.
  • A demand map for drivers, with push notifications for new, cancelled and reached rides.
  • A web dashboard for owners with live vehicles, trips, earnings and commission, plus driver verification, surge, coupons and vehicle categories.
  • Fare rules the admin sets per vehicle type: base fare, distance, waiting time, stops, cancellation time and surge.
  • Around 10 microservices on AWS, run with Kubernetes on EKS, so the system grows with drivers and passengers and the client pays only for what it uses.
  • A Discover & Frame workshop at the start, with user stories, process flows and clickable prototypes before the build.
  • Android
  • iOS
  • AWS
  • Amazon EKS
  • Kubernetes
  • Microservices
What it shows

What this work shows about us.

We know how a ride gets matched

Radius, rating, rides served, a one-minute accept window and a wider search when no driver is near: the dispatch rules of a taxi business, written into the product.

Every side of the ride

Passengers, drivers and owners each have their own app, from booking and navigation to fares, commission and fleet stats.

Built to grow with the consortium

Microservices on EKS carry 100+ bookings a minute (as reported) and let more operators join without a rebuild.

Want to build a similar ride-hailing app? Tell us what you want to change. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with the right team.

Start your plan ↗
If we built it today

If we built it today, with AI.

This work came before today's AI. If the consortium of taxi operators in Qatar asked us now, this is what we would add, step by step.

Quote

An agent would explain a fare before the passenger books, from the tariff and surge rules the owner set, and answer why a price changed. The fare rules still run as code.

Booking

An agent would take a booking by message, including a scheduled ride or one for someone else, and confirm the driver once matched. Matching still follows the consortium's rules.

Tracking

An agent would tell a waiting passenger where the car is and when it will arrive, without the passenger calling the driver.

A delay

An agent would notice when no driver accepts within the window, widen the search and tell the passenger what is happening. Owners still decide surge and fleet rules.

Ask Unthinkable

Want this for your business?

Tell us what you run or what you're building. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with a senior AI engineer.

Send us a note instead

Required

Thanks. A senior AI engineer will reply to you.
u
Ask UnthinkableClarity first, then the right team
Your conversation

An AI agent. This prototype uses prepared answers and sends nothing.