Vehicle-for-hire operations platform
Priv8Car is a family-owned vehicle-for-hire operator. The licence and the service have been live since 2006. The software is the modernization: one stack for drivers, clinics doing NEMT, and riders, instead of a live fleet running on whatever was pieced together over two decades.
A live service, an unfinished product
The company already moves people. What it did not have is a single operations platform: drivers on a mobile app, clinics booking non-emergency medical transport on the web, and clients using a VFH app — with dispatch and payments in the same system.
This is still in progress. The claim is not that a national consumer app is finished. The claim is that a licensed operator is replacing ad-hoc process with software it owns, without stopping the service that already exists.
- The VFH operation is live. New software cannot assume a greenfield market or a freeze on trips.
- Three surfaces, one domain: driver mobile, clinic NEMT web, client VFH app.
- Dispatch and payments are in scope. Matching a rider or a clinic trip to a driver is not a UI flourish; it is the business.
- I am the engineer on the product. Family ownership is context, not a different quality bar.
Rider, clinic, driver, pay
rider ⇄ driver
clinic → dispatch
↓
payments
Django holds the domain: users, trips, dispatch, and payment state. The web surfaces for clinics and clients sit on that API. Drivers get a mobile app against the same records. Vercel hosts the web delivery. The interesting split is not “mobile vs web.” It is NEMT clinic bookings and street VFH sharing a dispatch and pay path without pretending they are the same product.
Full stack: data model, APIs, clinic and client web, driver mobile work, dispatch, and payments. There is not a separate platform team. Decisions about what ships next are product decisions and engineering decisions at the same time.
Django · Vercel · driver mobile · clinic NEMT web · client VFH app · dispatch · payments
The operator still runs. The software is the program to put drivers, clinics, and clients on one stack. I do not publish trip counts or GMV. Status is in progress, on purpose.
- A live VFH licence is the asset. Software has to walk up to it, not the other way around.
- NEMT and street hail share dispatch and money, not UX. One database, two products, is the honest split.
- Solo full-stack on an operations domain means sequencing: payments and dispatch before polish on all three apps at once.
Modernizing a live operations domain?
I build the software a licensed VFH company actually runs on — drivers, clinics, clients, dispatch, payments. Open to remote technical-lead conversations.