Car rental websites and the software that runs them.

A rental catalogue is not a product grid. Rates move with duration, delivery is a real option with a real cost, a deposit or pre-authorisation sits between the booking and the handover, and a large share of renters will leave for WhatsApp before any of it. So the price has to resolve for the dates in front of the renter, rather than showing a daily rate and settling the rest by message.

This is also where mobile speed stops being a score in a report and becomes revenue. Rental searches happen on a phone, on mobile data, with two competitor tabs already open. A catalogue that takes three seconds to filter has lost the comparison before it showed its best car.

This is the part international rental products skip, because it is not a problem in the markets they were designed for. Salik charges arrive against the vehicle, not the renter, so attributing one means matching its timestamp to the contract that was live at that moment, and then to the customer on it. Fines are the same matching problem with a much longer tail — one can surface weeks after the deposit was returned and the car has gone out four more times.

Around that sit Emirates ID, licence and passport records captured at handover with expiry awareness; deposits that are held, partly released and drawn against for damage or charges; and invoicing that has to produce a compliant tax document. None of it is hard in isolation. All of it is hard to keep in agreement for years, and keeping it in agreement is the thing actually being bought.

One modelling decision decides whether any of it works: an extension recorded as a fresh contract severs the toll and fine continuity that attribution depends on. It takes five minutes to get right at the start and is expensive to correct once a year of records has been written against it.

Almost nobody should commission both halves at once. The usual order is a catalogue and a structured enquiry flow first, because that is what fills the calendar; then online booking, payments and deposits once volume justifies them; then the back office, once the process it is meant to encode has stopped changing every month. A system built around a workflow that is still moving is a system you pay for twice.

A custom management platform is also not always the right answer, and we would rather say so early. Under about thirty to fifty vehicles, a disciplined spreadsheet is usually still enough, and configuring an off-the-shelf product costs less than anything we would quote. Custom earns its place when the compliance automation is the entire point, when you run several branches with permissions that no product models, or when per-vehicle licensing across a large fleet over several years passes the cost of building. Ask us and we will tell you which of those you are in.