How to Build Black Car Dispatch Software

Most dispatch software is built for taxis and rideshare. Black car and limo operations work differently. They run on reservations booked hours or days in advance, not on real-time matching. They price by zone, not by meter. Their biggest revenue driver is the airport pickup, and the airport pickup only works well if the software knows when the plane lands. Building dispatch software for a black car, limo, hotel shuttle, or NEMT operation means building a different product from the ground up.

According to IBISWorld's 2024 Limousine and Town Car Services Industry Report, the US black car and limo industry generates approximately $7.2 billion in annual revenue. Airport corporate transfers account for over 55% of that revenue, making flight tracking not a nice-to-have but the core feature of the category.

What this software does

Black car dispatch software manages the full trip lifecycle for a chauffeur fleet. A trip begins when a customer or corporate booker makes a reservation. It ends when the passenger is dropped off, the driver logs the completion, and an invoice or receipt is generated.

Between those two points, the software coordinates three parties: the passenger who needs to know where their driver is, the driver who needs clear instructions and navigation, and the dispatcher who needs to see the entire fleet at a glance and catch problems before they become complaints.

For airport pickups, the software also monitors the passenger's inbound flight in real-time and adjusts the driver's dispatch time automatically when flights run late.

For NEMT (Non-Emergency Medical Transport) operators, the software also handles Medicaid broker integrations, HIPAA-compliant patient records, and documentation required for Medicaid billing. HIPAA here means secure record storage with audit logs, not just encrypted transit.

Core features: MVP vs. full product

MVP: 14-18 weeks, $130K-$220K

The MVP covers the core commercial workflow: advance reservation booking, dispatcher assignment, driver mobile app, flight tracking, passenger SMS notifications, and zone-based flat-rate billing.

Trip lifecycle, nine stages:

1. Booking: customer or corporate booker creates a reservation with pickup address, dropoff address, date, time, flight number (if applicable), and any special notes.
2. Dispatch: dispatcher reviews upcoming trips and assigns each to a driver. Or the system auto-assigns based on proximity and availability rules you define.
3. Driver assigned: passenger receives an SMS with the driver's name, vehicle description, license plate, and ETA. This SMS alone cuts inbound "where is my driver" calls by 60-70%.
4. Driver en route to pickup: driver's GPS location is tracked. Passenger can see live ETA.
5. Driver arrived: passenger receives SMS notification. Driver starts a wait-time clock.
6. Passenger onboard: driver marks trip as in-progress.
7. Trip in progress: GPS tracking continues. ETA to dropoff is recalculated live.
8. Trip completed: driver marks dropoff. Receipt is generated and emailed to the passenger and the booking account.
9. Billing: for corporate accounts, the charge is attributed to the monthly invoice. For direct consumers, Stripe charges the card on file.

Flight tracking is part of the MVP, not a nice-to-have. See the architecture section for how it works.

Full product: 22-28 weeks, $260K-$400K

Phase 2 adds: NEMT Medicaid broker integrations (MTM, Veyo, Access2Care), corporate self-service booking portal, on-demand dispatch (for NEMT), fleet analytics dashboard, and driver performance ratings at scale.

The architecture

Flight tracking

Integrate FlightAware or FlightStats via their commercial API. At booking, capture the passenger's inbound flight number and scheduled arrival time. The system begins polling flight status 4 hours before scheduled arrival, checking every 10-15 minutes.

When the flight delays, the system calculates the new pickup time (scheduled arrival + average deplaning and baggage claim time, typically 25-35 minutes depending on the airport) and updates the driver's dispatch time automatically. The driver receives a push notification: "Pickup for John Davis moved from 3:00 PM to 4:45 PM. Flight AA447 now landing at 4:15 PM."

When the flight diverts, the system immediately flags the trip to the dispatcher with a manual intervention alert. Diversions require human judgment, not automated rescheduling.

This single feature eliminates the primary complaint in airport transportation: a driver sitting at the terminal for 2 hours because a flight was delayed and nobody updated the pickup time.

Dispatch board

The dispatch board is a real-time map view for the dispatcher. Every driver is a map pin. Pin color indicates status: green (available), blue (assigned), orange (in-trip), gray (off-duty). Active trips are drawn as lines from pickup to dropoff.

The dispatcher can see all upcoming trips in a sidebar, drag-and-drop to reassign trips between drivers, and send in-app messages to specific drivers. When a cascade conflict exists (see the hardest problem section below), the affected trips are highlighted in red.

Driver mobile app (React Native)

The driver app shows upcoming trips in time order. Each trip displays: passenger name, pickup address, dropoff address, scheduled time, flight information if applicable, and any special notes the dispatcher added.

For navigation, the app opens Google Maps (or Waze) via deep link with the destination pre-filled. Drivers prefer their native map app over an in-app map. This saves six months of routing engineering.

GPS tracking rules vary by employment type. Hourly drivers are tracked continuously while clocked in. Per-trip contractors are tracked only during active trips. This distinction matters for labor compliance.

Pricing model

Black car pricing uses zone-based flat rates, not dynamic pricing. Example rate table: LAX to Beverly Hills = $85, LAX to Pasadena = $95, LAX to Santa Monica = $75. Zone pairs are defined in the admin dashboard and applied automatically at booking based on pickup and dropoff addresses.

Hourly billing applies to events and full-day hires: a base rate per hour with a minimum (typically 3 hours), plus any tolls, parking, or gratuity.

Corporate accounts bypass per-trip payment. The account carries a credit limit or cost-center code. Trips are attributed monthly and billed via invoice.

The hardest technical challenge

Flight delay cascades.

"The operators who built their own dispatch tools did it because of cascades. Every commercial product we evaluated showed you the conflict after it was already too late to fix it gracefully." -- Operations director at a national corporate ground transportation company, speaking at the 2023 National Limousine Association annual conference.

A single delayed flight often affects one booking. But that booking belongs to a driver who has three more trips that afternoon. If the delayed airport pickup now ends at 4:45 PM instead of 3:00 PM, and the driver's next trip starts at 4:00 PM, you have a conflict.

Naive systems show you the conflict only after it becomes a crisis. You need a cascade checker that runs the moment any trip's ETA changes by more than 30 minutes.

The algorithm treats each driver's day as a sequence of time-constrained tasks. When trip N is updated, the system checks whether the new end time of trip N overlaps with the start time of trip N+1. If it does, it checks trip N+1 against trip N+2, and so on. Any conflict is surfaced to the dispatcher immediately, with the affected trips highlighted and a suggested resolution (reassign trip N+1 to the nearest available driver).

This requires a data model where each driver's assignments are stored as an ordered sequence, not a flat list. The cascade check runs as a background job triggered by any trip status or ETA change.

Getting this right separates operational software from a scheduling spreadsheet with a map.

Build timeline and cost

MVP (advance booking, dispatch board, driver app, flight tracking, zone pricing, SMS notifications): 14-18 weeks, $130K-$220K.

Full product (adds NEMT broker integrations, corporate self-service portal, on-demand dispatch, fleet analytics, driver ratings, multi-city operations): 22-28 weeks, $260K-$400K.

Cost drivers: the Medicaid broker integrations for NEMT are the largest variable. MTM, Veyo, and Access2Care each have different electronic data interchange formats, and each state Medicaid program has its own billing codes and authorization formats. If NEMT billing is in scope, budget the higher end of the range.

Build vs. buy

LimoAnywhere costs $200-$500/month and is the most widely used tool in limo and black car. It has flight tracking, reservations, and a driver app. Moovs costs $200-$400/month with a more modern UI suited to operators who find LimoAnywhere dated. MedRoutes at $200-$400/month is NEMT-focused with broker integrations. TaxiCaller at $150-$300/month supports on-demand dispatch for taxi and black car fleets.

Buy these products first:

• LimoAnywhere: $200-$500/month. Most widely used in limo and black car. Has flight tracking, reservations, and driver app.

• Moovs: $200-$400/month. Modern UI, good for operators who find LimoAnywhere dated.

• MedRoutes: $200-$400/month. NEMT-focused, includes broker integrations.

• TaxiCaller: $150-$300/month. Works for taxi and black car, supports on-demand dispatch.

Build when:

You operate 100 or more vehicles, where monthly SaaS fees and per-trip charges compound to exceed what custom software costs over 3 years.

You are building a multi-city NEMT network that requires Medicaid broker integrations in multiple states, and no existing software handles your specific combination of states and waiver programs well.

You are building a hotel-branded or travel-brand transportation product where the guest experience (booking flow, driver communication, receipts) needs to match the host brand's visual and UX standards. White-label SaaS tools cannot achieve this.

Tech stack

Driver app: React Native. Single codebase covers iOS and Android. Expo simplifies builds and over-the-air updates for driver devices.

Customer booking: React (web) or React Native (mobile app), depending on whether your customers book primarily via browser or app.

Dispatch web dashboard: React. The dispatcher lives in a browser all day. The map uses Google Maps JavaScript API or Mapbox, depending on your customization needs.

Backend: Node.js with PostgreSQL. Trip data has relational structure (driver, vehicle, passenger, booking, trip segments). PostgreSQL handles this well and supports PostGIS for geospatial queries if you need radius-based driver availability searches.

Flight tracking: FlightAware AeroAPI or FlightStats API. Both offer commercial plans. FlightAware has broader global coverage. FlightStats is strong on delay predictions.

Mapping and navigation: Google Maps Platform (Maps JavaScript API for the dispatch board, Directions API for ETA calculations, Places API for address autocomplete).

Payments: Stripe for consumer card payments and corporate invoicing. Stripe Invoicing handles monthly invoice generation and PDF export.

SMS: Twilio. Three automated messages per trip (driver assigned, driver arrived, trip complete receipt). Twilio's programmable SMS API handles this with a webhook trigger on each trip status change.

Storage: AWS S3 for trip receipts, scanned documents, and driver records.

If you are adding NEMT billing, you will also need an EDI library or a third-party clearinghouse that translates your trip data into state Medicaid billing formats. This is custom integration work, not a standard library.

Build the flight tracking cascade checker early. It touches the trip assignment model, the driver schedule model, and the dispatcher notification system. Retrofitting it after launch is far harder than designing for it from the start. RaftLabs has shipped fleet and dispatch products for transportation operators, and the cascade conflict checker is the one component that cannot be bolted on after go-live without a significant refactor.