, Case study · Rental operations
Mobilio.
A rental management platform we designed and built end to end. Fleet, bookings, contracts, invoices and customers in one system, for operators who were running all of it from a spreadsheet and a phone.
- Started
- 2024
- Our role
- Design and build
- Stack
- React · TypeScript · Supabase
- Built on it
- Fleet Nest
, The brief
A rental desk that ran on memory.
The same car, booked twice
Bookings lived in a spreadsheet and a WhatsApp thread. Nothing stopped two people promising the same vehicle for the same weekend.
Damage nobody could prove
Pickup and return were a quick look and a handshake. When a car came back scratched, there was no record of how it left.
Dates kept in someone’s head
Insurance renewals, services and licence expiries were remembered, until they were not.
, What we built
Nine parts, one system.
Fleet & vehicles
A profile per vehicle: status, mileage, insurance expiry alerts and service reminders.
Bookings
The full booking lifecycle, with overlaps blocked at the database, pickup and return checks, damage photos and PDF contracts.
Fleet calendar
Monthly and weekly views, colour-coded by status, so a clash is visible before it is a phone call.
Customers
Customer profiles, driving licence details, booking history and corporate accounts.
Enquiries
A public enquiry form, an alert to the desk and a reference number for every request.
Invoices & payments
Pro forma and final invoices, automatic numbering, payment tracking, PDF and CSV exports.
Expenses
Costs logged per vehicle and by category, so the expensive cars stand out.
Dashboards
Revenue over time, fleet utilisation, profit per vehicle and the best customers.
Documents
Contracts stored against their booking, with a record of who did what.
, Decisions
The calls that shaped it.
Double bookings stopped by the database
01Not by a warning someone can click past. If two bookings overlap, the second one cannot be saved.
One platform, many businesses
02Each operator sees only its own data, enforced row by row in the database rather than trusted to the screen.
Built for the phone first
03The desk is often a car park. Every screen works one-handed, and the whole team sees changes live.
Paper becomes a PDF
04Contracts, pro formas and invoices are generated from the booking, so nobody types the same details twice.
, For your build
What carries over to your project.
The parts that are hard to get right in any operations system are already solved here: a booking engine that cannot double-book, documents generated from records, data separated per business, and dashboards fed by the same data. Fleet Nest’s customer site and operations dashboard were built on this base.
See Fleet Nest in our workYour business runs on a spreadsheet
and a phone too?
Tell us how the day works now. We will tell you what a system for it would involve.
Book a free 30-minute call