# JollyDrivers

> JollyDrivers (JD) is booking and back-office software for small, hands-off rideshare, chauffeur and transfer operators in Australia and the drivers who work for them. It takes the booking through an AI chat, gives each driver one workspace across every operator they drive for, and raises the operator's invoices directly in the operator's own Xero. JD is a technology platform, not a booking entity: the operator holds the authorisation and is accountable for the booking.

The app itself sits behind a sign-in at https://jollydrivers.com.au/signin. The pages below are the public description of it, written to be read by people and AI assistants.

Key facts:

- Audience: hands-off operators (chauffeur, executive, airport and regional transfer, fleets of about 3 to 15 vehicles, solo driver-operators), their drivers, and riders who return to drivers they trust.
- Booking intake: conversational AI (Anthropic Claude) with Google Maps address and route checks. It handles passenger trips, goods deliveries (including shop-and-deliver) and attendance tasks such as dog walking.
- Architecture: every intake goes through one shared creation path that checks the same rules every time. Every change is recorded as an event, and the rider, driver and operator screens update live from that history.
- Money: invoices, approvals, amendments, voids and payments go directly into the operator's own Xero organisation. JD does not set fares, does not vary them with demand, and works out no share of a fare for itself. Its charge is a flat fee to the operator on each settled booking, never to the passenger, and it never rises with the fare. The FAQ gives the amount. There is no surge or demand pricing; fares come from the operator's own fare book.
- Drivers: one calendar across all operators, with cross-operator schedule-conflict warnings (advisory only; each operator sees only its own bookings), live trip stages, hours and fatigue signalling, compliance documents and training.
- Compliance: JD produces evidence (trip records, hours, documents, training, safety management plans, audit-ready export). The operator and driver stay accountable.
- Deliberately not: a dispatch engine, a ratings platform, a consumer rideshare brand, or a booking entity.
- Not yet live: a marketplace for finding new drivers, and API links to government registers. Peer checking of a driver's compliance documents against a public register is live.
- Getting in touch: hello@jollydrivers.com.au. JollyDrivers is in closed beta; operators and drivers join by invitation.

## Pages

- [JollyDrivers home](https://jollydrivers.com.au/): one-page overview — who JD is for, the life of a booking, what makes it different, and how to get in touch
- [About JollyDrivers](https://jollydrivers.com.au/about): what JD is, what makes it different, and what it deliberately is not
- [How it works](https://jollydrivers.com.au/how-it-works): the life of a booking, and what riders, drivers and operators each get
- [FAQ](https://jollydrivers.com.au/faq): how JD differs from Uber-style apps and dispatch software, who holds the money, and what it charges
- [Releases](https://jollydrivers.com.au/releases): every release in plain language, newest first, with the day it reached production — what JD has actually shipped, rather than what it says it does
- [Blog](https://jollydrivers.com.au/blog): why JollyDrivers is being built, how it works under the bonnet, and what ships next (Atom feed at https://jollydrivers.com.au/blog/feed.xml)

## Connect your AI

An AI assistant that speaks MCP can ask JollyDrivers directly instead of only reading this file.
The public endpoint below needs no account, every tool on it is read-only, and its answers come
from files that shipped with the release, plus JollyDrivers' own published contact address — it
reads no bookings and no personal data. The account endpoint is a different thing: it acts for
one signed-in person, and some of its tools write.

- [Public MCP endpoint](https://jollydrivers.com.au/mcp): what JD is, what an operator, a driver or a rider can each do, and how JD compares with a rideshare app, dispatch software or a spreadsheet
- [Account MCP endpoint](https://jollydrivers.com.au/mcp/account): an operator or driver connects their own account with their usual JollyDrivers login, to ask about their own schedule, bookings and unpaid invoices. Open to a small pilot rather than to everyone

## Optional

- [Privacy policy](https://jollydrivers.com.au/privacy)