Robotaxi fleet management software: what to look for

General fleet software was built for vans and trucks with drivers: routes, fuel cards, driver behavior and hours. A robotaxi fleet has none of those, and a different set of problems: the car runs itself, so the work moves to the depot, and every hour a car isn’t earning comes straight out of a thin margin. Here is what robotaxi fleet management software needs to do, and the questions to ask before you choose one.

1. Show you which car stopped earning

The most important screen is not a map of every car. It is a short list of the cars that need you: offline, low battery, a defect from the morning inspection, service coming due. Look for one inbox that pulls those together and sorts them by severity, with a daily digest so nothing slips overnight. Our guide Robotaxi uptime explains why this matters so much.

2. Run the depot, not just the cars

• Service programs by miles or days per model, and work orders with vendors, costs and photos.
• A daily inspection checklist on a phone, with photos and clear rules for what is critical.
• A task board for cleaning, charging and moving cars, with a field app the crew can use one-handed.

The robotaxi maintenance checklist shows the routine the software should support.

3. Automate the routine decisions

A fleet that runs at night needs rules that act without a person: when an inspection finds a critical defect, take the car out of service and open a work order; when a car goes offline, alert the person on call. Ask to see the rule builder and a log of what each rule did.

4. Track charging per car

Energy is one of the biggest running costs. The software should record every charging session per car and show cost per paid mile, not just a monthly bill. More in How to charge a robotaxi fleet.

5. Show profit per car

A bank balance won’t tell you which cars carry the fleet. Look for imported platform payouts, a ledger that can’t be quietly edited, a monthly close, and a P&L per car you can compare with the estimate you bought the car on. See How much does a Tesla robotaxi earn? for what that P&L contains.

6. Handle owners, if you manage cars for others

Fleet managers need agreements with fees or revenue splits per owner, monthly statements tied to each transaction, and a read-only portal where owners can check their cars.

7. Connect to the car and keep your data separate

• A connection to the vehicle maker’s API for battery, odometer and status, with your permission.
• CSV import for vehicles and payouts, and CSV export of your numbers.
• Each fleet’s data isolated from every other customer’s.

8. Work with the AI you already use

More owners now ask ChatGPT or Claude about their business. Fleet software should let them: an MCP server and API keys, so an assistant can read the fleet and prepare work, with permissions, a log and approval for anything it changes. Fleetsly’s MCP server and API are coming in the beta; see AI agents and API and How to connect ChatGPT or Claude to your fleet data.

Questions to ask before you choose

• Can I see the inbox with a demo fleet, not a slide?
• What happens at 3 am when a car reports a critical defect?
• How do payouts get from the platform into the P&L?
• Can my depot crew use it on their own phones?
• Can I export everything if I leave?
• Can my AI assistant or my own scripts use it, and what can they change?

We built Fleetsly around this list, starting with Tesla. For the day-to-day routine behind it, read How to manage a robotaxi fleet.