Founding members · not open yet
We are starting an operator community from scratch
There is no room to walk into yet — no workspace, no channels, nobody inside. This is the founding-members list for a community for taxi, limo and ride-hailing operators, and the people who join now decide what it becomes. Add your email and the 8-page buyer's guide arrives today; the invitation follows when it opens.
Not open yet
This page is the list, not the door
8 pages
The buyer's guide, sent when you join
Founding
Whoever joins first decides what it becomes
No plan needed
You do not have to be a customer
Where this actually stands
The straight answer, before you give us an email
Most community pages describe a room full of people. This one cannot, so here is exactly what exists, what arrives in your inbox today, and what arrives later.
There is no room to walk into
No workspace, no channels, no threads, no archive to scroll back through. If you add your email today you are on a list, not in a chat. Anything further down this page describing rooms or topics is what we intend to build, not something already running.
What you get today
The 2026 Dispatch Software Buyer's Guide — a real 8-page PDF, emailed to you and shown on screen the moment you submit, so you are not waiting on an inbox. It is a vendor-neutral buying document: a requirements worksheet, a weighted scorecard, migration paths and a red-flags list.
What you get when it opens
One email with an invitation, and a say in how the thing is set up — where it lives, what the first rooms are, and what the rules are. That is the whole offer. We are not going to dress the list up as something busier than it is.
Join the list
Take the guide. Keep the invitation for later.
One form, two outcomes: a document you can use this week, and a place on the list for a community that does not exist yet. We would rather be clear about which is which.
The 2026 Taxi & Limo Dispatch Software Buyer’s Guide
8 pages · PDF · yours immediately
A requirements worksheet, a weighted vendor scorecard, the pricing models decoded, migration paths and a red-flags list. Vendor-neutral, including about us.
Submitting sends you the guide. We keep your address so we can send the invitation when it opens. There is nothing to enter today beyond that — the invitation email is the next time you hear from us about the community. If you only want the document, the direct download link under the button skips the list entirely.
The starting agenda
What we want it to be about
None of this exists yet: there are no rooms, no threads and no archive behind these headings. This is the agenda we would put in front of the first members — and it is theirs to rewrite.
The dispatch floor
The part of the job that no manual covers. We want a place where the people actually working the board can compare how they handle the hours that go wrong, rather than how the software is supposed to behave in a demo.
- How you staff a Friday night, a match day, or an airport in fog
- What you actually do in the first minutes when a driver stops responding
- The habits and shortcuts experienced controllers never write down
Switching platforms
Changing dispatch systems is the decision operators are most afraid of and have the least honest information about. We publish our own switching method openly; the intent is a place where the messy parts get discussed rather than sold.
- What dual-running really costs in staff hours and patience
- Which data you must get out in an open format before you sign anything
- Where cutovers go wrong, written down so the next operator sees it coming
The money side
Fares, settlements and invoices are where small mistakes compound quietly. This is the topic we most want operators arguing about in the open, because a badly-set surcharge or a slow-paying account is rarely a software problem.
- Zones, surcharges and what to do when a price is provably wrong
- Driver settlements, commission plans and what drivers accept
- Corporate accounts, purchase orders and actually getting invoices paid
Regulation, city by city
Licensing rules change locally and unevenly, and the practical reading of a new rule usually arrives months after the rule does. Which cities end up covered depends entirely on who joins — we are not going to pretend to a map we do not have.
- New licensing and compliance requirements as operators hit them
- What a rule change means in practice for a fleet your size
- Local paperwork, inspections and the timelines they really take
What we should build next
We build TaxiDex, so the most useful thing we can offer a room of operators is a short path to the people writing the code. The intent is that requests are argued in the open, in front of other operators, instead of disappearing into a form.
- Feature requests discussed with the people who would build them
- Honest answers about what is not going to be built, and why
- Early looks at work in progress before it reaches the changelog
Work that outlives the thread
Chat is a bad archive. Anything genuinely useful should end up as a published guide, calculator or checklist that any operator can read without joining anything — the same way the four guides and five calculators on this site already work.
- Useful threads written up and published, credited if you want it
- New calculators and checklists aimed at gaps members point out
- Everything free to read, with no login and no wall
How it will run
The rules we are committing to now
Written down before there is anyone to hold us to them, which is the only time writing them down means much.
Our bias, stated
We are a vendor, and that changes how you should read this
A community started by a software company is not neutral. Rather than pretend otherwise, here is what we build and where the conflict of interest sits.
What TaxiDex is, so you can weigh the source
TaxiDex is dispatch software for taxi, limo and ride-hailing fleets: a dispatch console and live operations map, an auto-dispatch rules engine, a drag-and-drop board, a fare engine, finance and settlements, corporate accounts, flight tracking and an audit trail, plus a driver app and a passenger app. The passenger app and web booker carry the operator’s brand; the driver app is always TaxiDex-branded.
That is the conflict of interest, in plain terms: we would like operators to buy our software, and we are the ones starting this list. The counterweight we can offer is that everything on this page is either something you can verify today or something clearly marked as intent. The guide is written to help you evaluate any platform, and the migration protocol we publish assumes your existing system stays licensed as a rollback while both run side by side.
Available right now
Useful things that need no invitation
The community is not open. Everything below is, today, free and without a form standing in front of it.
Four guides, written for the decision you are actually making
Each is a short PDF you can read in a break, not a lead-gen brochure padded to length. The dispatch software buyer’s guide is the one this page sends you. There is also an Autocab migration checklist, a dead-mileage playbook, and a ride-hailing startup roadmap for anyone building an operation from nothing.
A switching method published in full
The migration protocol sets out a 14-day switching process day by day: both systems run in parallel, your existing platform stays licensed so it remains a genuine rollback, and the cutover happens shift by shift rather than in one weekend. It is published so you can hold any vendor — including us — to a written method instead of a verbal reassurance.
Calculators that run on your numbers, not ours
Five of them, all free: the dead-mileage calculator, the dispatcher cost calculator, the driver earnings calculator, the ROI calculator and the surge pricing simulator. Put your own fleet size, shift patterns and rates in and see what falls out.
Comparisons, pricing and the blog
The comparison pages set TaxiDex against the platforms operators usually shortlist, feature by feature. Pricing is published in full rather than gated behind a call. The blog is where longer write-ups land — and where anything genuinely useful from the community would end up, free to read whether you joined or not.
FAQ
The questions a sceptical operator asks first
Including the uncomfortable ones about what exists, who is behind it, and why you should give an email to a list.
Is there a Slack or forum I can join right now?
No. There is no workspace, no channels, no members and no archive of past discussion. If you add your email today you are joining a founding-members list, not entering a room. This page previously described a private Slack with live channels; that description was inaccurate and has been removed.
What actually happens when I submit the form?
The 2026 Dispatch Software Buyer's Guide is emailed to you, and the download link appears on screen straight away so you never have to wait on an inbox. Your address is recorded on the founding-members list so we can send you an invitation when the community opens. If you would rather not give an email at all, the form has a direct download link underneath it — take the guide and skip the list.
When will it open?
We are not going to invent a date. It opens when enough operators are on the list that a first conversation is worth someone's time — a handful of people talking to themselves helps nobody. You will get one email when that happens. If it becomes clear operators do not want this, we will tell you that instead of quietly keeping the list warm.
Do I have to be a TaxiDex customer?
No. Being on the list costs nothing and requires no plan, no trial and no purchase. If you do want to look at the product, the per-driver rates and the monthly minimum are published on the pricing page and you can book a demo — but neither is a condition of joining, and nobody will be sorted by whether they bought anything.
Which platform will it run on — Slack, Discord, something else?
Deliberately undecided. It is one of the first questions for the people who join, along with whether it should be one room or several and how heavily it should be moderated. Committing to a platform before knowing who is in it is how communities end up shaped by a tool instead of by their members.
TaxiDex sells dispatch software. Is this just a lead magnet?
We build and sell TaxiDex, and you should read this page with that in mind. The guide you receive is written to be vendor-neutral — the scorecard rates any platform on the same criteria, including ours. The honest position is that a community run as a sales channel would not be worth joining and would not last, so the rules above apply to us before they apply to anyone else.
How do I get off the list?
Reply to either email — the one with the guide or the invitation — and say so. You come off the list, with no confirmation loop and no retention offer.
Get the guide today. Get the invitation when there is one.
No membership to claim, no room to oversell. Add your email, take an 8-page document you can use this week, and be among the operators who decide what this becomes.