A custom platform for car-rental operations.

Context

Vehicle rental looks like booking software and behaves like asset operations. Every vehicle is a physical asset with a location, a condition, a maintenance history, a utilisation rate and a cost. Every rental is a commitment against that asset, subject to late returns, damage, swaps, extensions and transfers between locations.

This engagement designed and built a custom platform supporting those workflows.

Why a generic product often falls short

• Fleet state is the core model. The central question is not “is this bookable” but “where is this vehicle, what condition is it in, and what is it committed to”. Systems built around a calendar struggle with that.
• Exceptions are the business. Extensions, early returns, damage, upgrades and one-way movements are routine, and each has commercial consequences that need to be recorded, not worked around.
• Operational and commercial views must reconcile. Utilisation, pricing and availability are the same data viewed by different teams. When they diverge, the business over- or under-commits its fleet.
• Local process is real. How a specific operator handles deposits, checks, documentation and handover is often the part that a standard product cannot accommodate.

The general lesson

Asset-based operations - rental, logistics, equipment, field service - share this shape. The workflow is specific enough that forcing it into a generic product creates manual reconciliation, and that reconciliation grows with volume.