One record for every booking, car, and chauffeur.

Limousine management software runs a chauffeur or black-car company from one record per trip. The booking, the price, the car, the chauffeur, the flight, and the invoice all read from that record. It covers online booking, pricing rules, a dispatch board, a driver app, flight tracking for airport pickups, payments, and corporate billing. It is different from generic fleet software, which tracks vehicles, and from transport management software, which moves freight.

Taxi work is reactive: a rider requests a car now. Limousine work is scheduled: bookings are made days ahead, trips have several stops, cars are reserved by the hour, regular passengers have preferences, and some passengers only ride with a particular chauffeur. A system built for on-demand rides treats every rider the same and cannot hold hourly bookings, corporate accounts, preferred chauffeurs, or event orders with several cars. That mismatch is why operators end up back on spreadsheets beside the taxi system.

The flight number sits on the booking. The system follows the actual arrival, not the scheduled one, so a delayed flight moves the pickup without phone calls, and an early flight pulls the chauffeur forward. The driver sees the terminal and gate information on the job, and the passenger sees the chauffeur once assigned. The wait clock and its rules are agreed in advance, so a delay caused by the airline is not billed as if the passenger kept the car waiting.

Wait time starts from a rule you set, such as a fixed grace period after the flight lands, and the driver app records when the wait starts and ends. Extra stops, added hours, tolls, and parking are recorded on the trip itself, not on a separate note. The invoice is raised from the trip record, so the passenger is charged for what actually happened, and the office does not reconstruct the trip at month end.

One set of pricing rules covers every trip. A zone price applies to a fixed area pair, an hourly price applies to as-directed work with a minimum booking length, and a flat rate applies to airport and point-to-point runs. Surcharges for nights, holidays, extra stops, or larger vehicles apply from the same rules. Every booking, quote, and invoice uses those rules, so two dispatchers never price the same trip differently.

Each company account holds its own rates, billing contact, and payment terms, including Net-30 where agreed. Trips for that company are grouped into one monthly invoice with trip-level detail: date, passenger, route, vehicle, and price. Deposits and card payments sit on the same record as the invoice, so the office can see what was charged, what is owed, and what is overdue without rebuilding the month from separate tools.

The job arrives on the chauffeur's phone with the pickup, route, passenger notes, flight information, and price details the driver needs. The driver accepts or declines, navigates from the job, and taps through each status, so dispatch sees progress without calling. If a job goes unaccepted, it is re-offered under rules you set and flagged to dispatch before it becomes a missed pickup. The dispatcher always sees every active trip, driver, and vehicle on one board.

Cars and chauffeurs each have one availability record. A booking that overlaps an existing trip for the same car or chauffeur is refused at entry, including multi-day work, event orders with several cars, and hourly bookings that run long. The check happens against the same record dispatch uses, so the office, the driver app, and the passenger view can never disagree about who is where.

Yes. The booking page and apps carry your company name, and the customer records stay in your account. A ride marketplace puts its own brand in front of your passenger, takes a cut of every fare, and holds the customer relationship, so a repeat passenger books through the marketplace next time, not through you. Owning the booking channel is what keeps repeat corporate and regular passengers yours.

Switching starts with a move-over plan, not a cutover date. Bookings, customers, company accounts, rates, driver records, and trip history are mapped from the old system, whether that is Limo Anywhere, Moovs, spreadsheets, or paper, and checked record by record before anything goes live. The old system keeps running beside the new one until the new record matches it, so no booking is lost in the move.

Ask for the all-in monthly figure in writing. Operators commonly find the advertised plan price is only part of it: per-booking fees, driver seat charges, and a higher support tier can sit on top of the base plan, and the real total only appears once the invoice arrives. Any quote worth signing names the base plan, every per-trip and per-driver charge, payment processing terms, and what support tier is included, before you commit.

Yes. An event order holds several cars and several pickups under one confirmation, with each car and chauffeur checked against the same availability record. Hourly work reserves one car and chauffeur for a block of time, with the clock starting and stopping on the trip record and extra time billed in the increments you set. Multi-stop days, roadshows, and nights out run as one trip with stops, not as separate bookings that have to be reconciled later.

When a trip is outside your area, you send it to a partner operator in that city from the same dispatch board. The partner sees only their trip: pickup, passenger notes, and price details for that job. The customer relationship, the booking record, and the invoice stay with you, and what you owe the partner is tracked against the trip, so settlement at month end does not depend on remembering who drove what.

Ask for the quote to name everyone who will use the system, including your own team. Every platform has two products: what passengers see, and what your people use all day: the dispatch board, driver management, billing, and a record of who did what. When that second product is quoted as an 'admin panel' on a single line, it becomes the overrun. Our quotes treat your team's screens as their own scope, with their own users. Then the phase names the workflow, what 'done' looks like, the price, and the exclusions, all before paid work starts. You review working software at agreed checkpoints, and when new information changes the scope, you hear the effect on price and timing before anything is approved.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces don't fit. A software company earns its fee when the work needs coordination across screens, rules, data, and connections: one accountable party, one phase price, and checkpoints against the whole workflow. If your need is one screen or one fix, hire the freelancer.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.