Bookings limited to office hours
Tourists landing at midnight and residents planning at 10pm found a phone number, not a booking button — and moved to the next tab.
Case StudyAutomotive
A UAE Car Rental Group: From Phone-Call Operations to a Booking Engine
A car rental group operating across the UAE ran a modern fleet on a manual core: availability checked by phone, contracts signed on paper, and utilisation understood only at month-end. We built its booking engine, digital contract flow, and fleet dashboards — making the fleet bookable around the clock and its economics visible daily.
At a Glance
- Client
- Car rental group — UAE-wide
- Industry
- Automotive — rental & fleet
- Engagement
- Booking engine + fleet operations
- Payments
- Cards, Apple Pay, Tabby
- Core target
- Bookable 24/7, utilisation visible
Background
The Context That Made This Worth Building
Car rental is a utilisation business: every day a car sits unbooked, its fixed costs run anyway. The group’s fleet was healthy and demand was real — but the booking process (call, wait, confirm, sign paper at the counter) meant demand outside office hours simply bounced, and management flew the fleet on instinct rather than numbers.
The Challenge
The Pain Points That Started It
Three operational drags, all rooted in the same missing layer of software.
Counter paperwork throttling handovers
Licence copies, contract printing, deposit handling — twenty minutes of counter time per rental, multiplied across every pickup.
Utilisation invisible until month-end
Which categories over-index, which branches starve, when to rebalance the fleet — questions answered by accounting reports weeks too late.
Discovery
Understanding Before Building
We mapped the rental lifecycle end to end — enquiry, verification, contract, handover, return, fines and Salik reconciliation — timing each step and noting where staff re-typed the same data. The counter emerged as the chokepoint, and after-hours demand as the invisible loss: the phone log showed clusters of missed calls at exactly the hours competitors with online booking were converting.
Pricing and deposit rules varied by category, duration, and season in ways that lived in the operations manager’s head. Discovery externalised those rules into a structure an engine could execute — the prerequisite for honest instant quotes online.
The Solution
What We Designed and Built
A booking engine at the front, an operations system at the core, and dashboards on top.
Online booking engine
Live availability by category and branch, instant pricing with seasonal rules, UAE payments including Tabby, and document upload before arrival.
Digital contract & handover flow
Pre-verified documents, digital signatures, and condition photos at pickup and return — the twenty-minute counter visit cut to minutes.
Fleet & utilisation dashboards
Live utilisation by category and branch, upcoming returns, maintenance windows, and fines/Salik reconciliation views.
Scope Delivered
Everything That Shipped
- Booking website with live availability & instant pricing
- UAE payment mix — cards, Apple Pay, Tabby
- Pre-arrival document upload & verification
- Digital contracts with condition photo capture
- Fleet utilisation & branch dashboards
- Maintenance scheduling & alerts
- Fines & Salik reconciliation workflow
- WhatsApp booking assistant for enquiries
Implementation
How the Build Ran
- 1
Lifecycle mappingWeeks 1–2
Every step from enquiry to return documented and timed; pricing and deposit rules externalised from heads into structure.
- 2
Booking engineWeeks 3–6
Availability, pricing, payments, and document flows built and tested against real rate cards and real weekends.
- 3
Counter & fleet opsWeeks 6–9
Digital contracts, handover flows, and fleet dashboards rolled out branch by branch alongside the paper process, then instead of it.
- 4
Assistant & tuningWeeks 9–11
WhatsApp assistant for availability and booking questions; pricing rules and reminders tuned on live behaviour.
Stack
- Next.js
- Node.js
- PostgreSQL
- Stripe
- WhatsApp Business API
Results & ROI
What It Delivered
24/7Fleet bookable, from office hours
~75%Counter time cut at handover
DailyUtilisation visibility, from monthly
~11 wksMapping to full rollout
- After-hours demand converted instead of bounced — the midnight arrival books before the taxi reaches the hotel
- Handover queues dissolved: documents verified before arrival, signatures digital, condition photographed
- Fleet rebalancing decisions made weekly on live utilisation data instead of month-end instinct
- Fines and Salik reconciliation moved from spreadsheet archaeology to a tracked workflow
The group’s fleet didn’t change; its availability did. Making inventory bookable at the hours demand actually occurs, and stripping the friction from handover, converted existing demand the business had been silently declining. The dashboards then turned fleet management from a monthly retrospective into a weekly steering decision.
Takeaways
What This Project Teaches
Utilisation businesses live on after-hours demand
When inventory is perishable by the day, every hour the booking channel sleeps is inventory quietly expiring.
Move the paperwork before the customer arrives
Pre-arrival verification is the highest-leverage minute-saver in any counter operation.
Externalise the rules in heads
Instant online pricing only became possible once seasonal and deposit logic left the operations manager’s memory and entered the system.
Before You Ask
What Readers Usually Want to Know
Our pricing rules are complicated. Can a booking engine really handle them?
Yes — that complexity is precisely what a rules engine is for: seasonal calendars, weekday and weekend rates, duration tiers, category pricing, deposits, and minimum hire periods. The real work is extracting those rules from the people who currently hold them in their heads and writing them down. Once that exists, honest instant pricing online becomes straightforward.
Do we have to replace our existing fleet software?
Not usually. If your current system manages the fleet adequately, we build the booking and handover layer around it and integrate where possible. Replacement is only worth discussing when the existing system actively blocks the thing you are trying to fix — and we will tell you when that is genuinely the case.
What about Salik, fines, and deposits?
They are part of the rental lifecycle, so they belong in the system rather than in a spreadsheet afterwards. Deposits are handled at booking, and post-rental charges like tolls and fines get a tracked reconciliation workflow so they are matched to the right contract and customer instead of being reconstructed at month end.
The Services Behind This Build
Need the Same Capabilities?
Want a Result Like This?
Tell us your pain points — we’ll walk you through how we’d scope it, what it would cost, and what a realistic outcome looks like. Honestly, both ways.