21 modules on one data layer, thirteen live integrations, one API. Every row carries an owner stamp and the database — not the code — fences each tenant. Hover the diagram; scroll for what each module does and why it was built that way. The integrations have a page of their own.
A booking made in the widget is the same record the driver taps, the board drags, the invoice posts and the analytics count. Hover a node.
Every screen below is the real console, and it wears the look you are reading in — Midnight Noir after dark, Powder by day. The platform carries the same two, per person: your night dispatcher and your morning office manager sign into the same system and each get the one they want. Flip it and watch the screens follow.
What is bringing the work in, what is moving right now, what needs a decision. Live counts, the next five pickups, the flights that matter this evening, and anything that has gone red.
“Nobody should have to open four screens to know whether today is under control.”
Zone-pair and hourly quoting, class multipliers, seasonal windows, multi-leg and round trips, arrive-by pickups worked backward from the appointment, pre-authorisation at confirmation. The price is re-computed on the server at submit, so a quote cannot be edited in the browser.
“A reservation that was quoted wrong is a margin you never get back.”
Every unit on a live map, with National Weather Service radar, FAA airport status and state road closures scoped to the route being driven — not the county. Chips ring when a trip is under way and pulse red when two trips collide on one car.
“Weather is a dispatch input. It should not be a website you go and check.”
Day, week and month views. Sideways drags reassign the unit and hold the clock; vertical drags move the time. Before you commit a car it answers, in plain language: deadhead from the last drop-off, traffic ETA, already-booked work, and whether it is feasible.
“The question is never “is the car free” — it is “where will the car physically be”.”
A web app under your domain: today's sheet, one-tap status (on the way, arrived, on board, dropped), navigation hand-off, pre-trip inspection, tip capture, and pay visible per trip. Location reports back to the board while a trip is live.
“Drivers churn; the app should not be one more thing to onboard.”
FAA status and AeroDataBox schedules polled per flight, not per page load. Red-eye arrivals are matched to the day the flight actually lands. Delays move the pickup and tell the driver; a cancellation raises a flag on the board instead of a surprise at the kerb.
“The airport run is the trip most likely to go wrong for reasons that have nothing to do with you.”
Pre-auth at booking, capture on completion, bank debit at 0.8% capped at $5 for the accounts that pay that way, tips after the drop, refunds and partials, a passenger wallet, and statements. Card cost is carried to the trip line so margin is real.
“We never take a cut of your volume. That is the whole point.”
Accounts, contacts, aliases, travel-arranger relationships, notes and a message thread per contact. Capture from the booking flow. SMS with quiet-hours guardrails built into the sending layer so nobody gets a text at 2am unless they are being picked up at 2:30.
“The customer list is the business. It should live where the bookings live.”
Zone-pair matrix, hourly and point-to-point, class multipliers, seasonal windows, minimums, service and fee rules, per-partner rate cards that fall back to the house sheet, per-row locks so a promotional rate cannot be accidentally overwritten.
“Every operator's rate sheet is a decade of hard-won exceptions. We keep them.”
Affiliate network integration for sending and receiving work across operators. Built to the GRiDD specification; awaiting certification credentials before it is switched on in production.
“An operator who cannot farm cannot switch. This is why it was built before it was asked for.”
Preventive maintenance programmes, driver inspections with photos, registrations and insurance dates, Azuga telematics, and an odometer that accrues from completed trips instead of waiting to be typed in. Every card says what the car is doing this minute.
““Ready” is a fact about paperwork. The garage wants to know if the car is halfway to the airport.”
Twenty dimensions against twenty measures, drillable to the trip, scheduled to your inbox. Driver pay, tips and card cost are carried through, so “did that job make money” has an answer rather than an opinion.
“A report that stops at revenue is a story. A report that reaches margin is an answer.”
Scheduled runs, seat inventory, tour pages with their own checkout, and the same drivers, vehicles and accounts as the charter side. One garage, one payroll, two kinds of work.
“Mountain operators live on both. Two systems for two lines of business is one too many.”
OAuth connection to QuickBooks Online. Invoices, payments and customers posted as they happen. No CSV round-trip, no month-end reconciliation from memory.
“Your accountant should never learn about a trip from a spreadsheet.”
It reaches every module rather than sitting in a corner of its own: the board, the sheet, the accounts, the cards, the books. It reads live operational data and acts on it — reassign, reschedule, draft the message, propose the quote — behind a confirmation gate, so nothing moves without you saying yes. Scoped to the caller's permissions: a chauffeur's assistant cannot see billing, and the money paths stay locked whoever is asking.
“Useful, and unable to do anything you could not do yourself.”
Accounts, companies, chauffeurs and cars from your current system land first, through a reconciliation gate that compares file counts to platform counts before anything is committed — with an undo. Reservations and money follow. Limo Anywhere first, because half the operators in the region run it.
“This is the part you are dreading. It is the part we do.”
The platform is a WordPress plugin. Your pages, photography, brand and search ranking stay exactly where they are; the booking widget and passenger pages render in your theme. Three in five operators in our region are already on WordPress.
“Nothing moves to somebody else's domain.”
How to read this. Throughout, boxes like this explain the reasoning behind a rule. They are worth reading once, because almost every "that's odd" moment on this platform is a rule doing exactly what it was built to do:
Marketing — The words on the site, and who gets a discount. Four things sit here: promotions, which run on the promo codes you have already set up; the copy desk, where drafts are written with AI help but in the house voice rather than a generic one; the SEO agent; and the living site. The living site works on scheduled beats — at set intervals it proposes changes to the website and waits for someone to approve them. Nothing goes live because a machine decided it was time.
Where the money goes — One page for the whole picture. This is the single page that shows how money arrives, how it goes back, and where the rest of it ends up. Each box on it stands for a part of the system that has its own section further down, so you can start here and follow the one you need. It is the map rather than the detail, and it is meant to be read before anything else.
Refunds and credits — Money goes back from the screen it came in on. A trip is refunded on the trip; a statement is refunded on the statement, so the record of the return sits with the record of the charge. Both panels open with the same three figures: what was collected, what has already gone back, and what is left on each rail. That last figure is the one that decides whether a refund can go through at all, and it is not the fare.
From the platform's own operations guide, version 3.116.0.
Stripe, Twilio, QuickBooks, Azuga, GNet, flight schedules and airport status, weather, roads, maps, sign-in and the Agent — each one a first-class input to the board. They have a page of their own.
Every client gets their own site, domain and branding, all calling one API into one database. Every row carries an owner stamp; the database, not the application code, fences each tenant.
Capability checks on every route, prepared statements, output escaping everywhere, twenty-three deliberately public endpoints and every one of them reviewed. An independent audit's findings closed.
Runs on your own WordPress and your own server by default. If you would rather not run one, we host it: we move the site you have, or build you a fresh one, and the whole thing exports the day you ask.
Thirty minutes, screen share, your own numbers typed into the live system.
