Vehicle access managed through a manual key handover process that breaks down the moment two bookings overlap or a vehicle runs late?
Fleet utilisation and damage reporting tracked in spreadsheets because the booking tool has no reporting layer?
Mobility Platform Development
Custom mobility software for car-sharing operators, vehicle subscription services, chauffeur dispatch companies, and corporate mobility programmes -- booking management, vehicle access control, and fleet utilisation analytics in one platform.
Built for mobility operators who have outgrown a manual booking process or a generic booking tool and need a platform designed for the specific workflows of their vehicle access model.
Booking management with real-time vehicle availability and conflict detection
Keyless vehicle access integration with hardware partners for app-based unlock and return
Driver verification and licence check at onboarding with ongoing compliance monitoring
Fleet utilisation and revenue reporting across all vehicles and locations
RaftLabs builds custom mobility platforms for car-sharing operators, vehicle subscription services, chauffeur dispatch companies, and corporate mobility programmes. Key capabilities include real-time booking and vehicle availability management, keyless vehicle access integration, driver licence verification and compliance monitoring, dynamic pricing and subscription billing, multi-depot fleet management, and utilisation and revenue analytics. Most mobility platform projects deliver in 12-20 weeks at a fixed cost.
Generic booking tools are built around appointment slots and calendar availability. Mobility operations require something different. A car-sharing platform needs to know whether a vehicle is physically available at the right location, whether the person requesting it has a valid licence and clean compliance record, and whether the keyless access hardware will unlock correctly at the time of the booking. A subscription programme needs recurring billing tied to a vehicle assignment, damage reporting at each handback, and utilisation data by vehicle class to decide where to add or remove stock.
The practical failure point for most mobility operators is the junction between booking confirmation and vehicle access. A generic booking tool confirms the reservation. It does not unlock the car. It does not check whether a different booking ran over and the vehicle has not been returned. It does not record fuel level or damage at handback. Those gaps are closed with manual processes -- phone calls, paper forms, key lockboxes -- that break under any volume and create liability exposure when something goes wrong.
A custom mobility platform is built around the specific access model of the operation: the booking logic, the vehicle access method, the driver compliance requirements, and the utilisation data that determines whether the fleet is sized and priced correctly.
What we build
Booking and availability management
Real-time vehicle availability engine that accounts for active bookings, vehicle preparation time between returns and new starts, and location-specific stock. Conflict detection that prevents double-booking at the point of reservation, not after confirmation. Booking extension handling that checks downstream conflicts before approving an extension request. Multi-depot booking logic that surfaces only vehicles available at the relevant location or within a configurable pickup radius. Cancellation and no-show workflows with configurable fee rules applied automatically. The booking layer that makes vehicle access predictable rather than dependent on a coordinator resolving conflicts by phone.
Keyless vehicle access
Integration with connected vehicle hardware to deliver app-based lock and unlock without a physical key exchange. PIN entry and RFID card options for operators who need a fallback access method independent of a smartphone. Access token generation tied to the booking window so the vehicle cannot be accessed outside the confirmed reservation time. Hardware partner integrations built around the specific devices in your fleet -- whether that is Gemalto, Invers, Vulog, or a proprietary telematics provider already installed. Return confirmation triggered by vehicle lock at the end of the booking, with location and fuel level recorded at that moment. The access layer that removes the manual key handover from every transaction.
Driver onboarding and compliance
Licence verification via DVLA check or state DMV API at the point of onboarding, with the verification result stored against the driver profile. Background check integration for operators who require criminal or driving history screening before a driver is approved. Ongoing licence status monitoring that flags changes -- endorsements, suspensions, or expiry -- between the initial check and each subsequent booking. Document expiry alerts for additional compliance materials such as insurance certificates for commercial drivers or operator-specific permits. Disqualification logic that prevents a driver with a failed or expired compliance status from completing a booking without manual override from an administrator. The compliance layer that reduces liability exposure without adding manual screening to every reservation.
Pricing and payments
Dynamic pricing engine that applies rates by vehicle class, time of day, demand level, and booking duration -- with the ability to configure promotional rates for specific periods or member segments. Deposit collection at booking with configurable hold amounts by vehicle class, released automatically on clean return or applied to damage charges. Damage charge recovery workflow that records condition at return, generates a charge against the payment method on file, and notifies the driver. Subscription billing for monthly vehicle access programmes with mid-cycle vehicle change handling and automated renewal. Invoicing and payment history per driver for both consumer and corporate account holders. The payments layer that captures the right charge at the right time without a manual step.
Fleet and location management
Multi-depot vehicle allocation showing which vehicles are assigned to which location, with stock transfer requests and approval workflow between sites. Vehicle status tracking through every stage: available, booked, in use, in preparation, out of service, and transferred. GPS position recorded at vehicle return so the next driver sees the exact parking location rather than a general zone. Fuel and charge level recording at handback with low fuel alerts that prevent a vehicle being returned below the minimum level without a charge being raised. Vehicle condition recording at each handback with photo attachment, flagging damage for review before the vehicle is made available for the next booking. The fleet layer that keeps vehicle status accurate across every location in real time.
Utilisation and revenue analytics
Vehicle utilisation rate per vehicle and per location showing booked hours as a percentage of available hours, with trends by day of week and time of day to identify demand patterns. Revenue per vehicle per day calculated from completed bookings, factoring in any damage charges or late return fees recovered. Damage incident rate per vehicle and per driver segment to identify high-risk assets or profiles for targeted action. Booking lead time distribution showing how far in advance reservations are made -- relevant for subscription and corporate programmes evaluating demand predictability. Fleet ROI by vehicle class combining utilisation, revenue, maintenance cost, and depreciation inputs to support stock replacement and acquisition decisions. The reporting layer that turns operational data into decisions about fleet size, pricing, and driver policy.
Frequently asked questions
We build platforms for car-sharing operators running peer-to-peer or fleet-owned models, vehicle subscription services offering monthly access programmes, chauffeur and executive transport companies managing driver dispatch and corporate account billing, ride-hailing and on-demand vehicle services, and corporate mobility programmes managing employee vehicle access. The common thread across these models is that booking confirmation and physical vehicle access need to be connected by software rather than a manual handover process. The specific workflow, access method, compliance requirements, and billing model differ by operation type, and we scope each platform around those specifics rather than applying a generic template.
We have built integrations with Invers, Gemalto Cinterion, Vulog, and Geotab Connected Vehicle hardware, as well as custom OBD-II and CAN bus telematics devices from Teltonika and Queclink. Hardware integration method depends on what connectivity the device provides: most modern connected vehicle hardware uses MQTT or REST APIs for command and telemetry, while older or more proprietary devices may require a gateway layer. If you already have hardware installed in your fleet, we integrate with it. If you are selecting hardware for a new fleet, we advise on devices that support the access and telemetry features your platform requires. Hardware availability and API documentation are confirmed during discovery before development scope is finalised.
Licence verification is implemented against the relevant authority API for the market. In the UK, that is the DVLA enquiry service, which returns licence status, endorsement data, and category entitlements. In the US, we integrate with state DMV APIs where available or with a third-party MVR provider that aggregates state records. In other markets, we scope the available verification method during discovery -- some markets have no programmatic verification API, in which case we build a document upload and manual review workflow with document expiry tracking. Ongoing monitoring frequency is configurable: daily, weekly, or triggered by a booking request. Drivers who fail a check are flagged in the platform and blocked from new bookings until the issue is resolved or an administrator overrides the block with a documented reason.
A core mobility platform covering booking management, basic vehicle availability, payment collection, and driver profiles typically delivers in 12-14 weeks. A full platform adding keyless vehicle access hardware integration, DVLA or DMV licence verification, dynamic pricing, multi-depot management, damage charge recovery, and utilisation analytics typically runs 16-20 weeks. Timeline and cost depend on the number of hardware integrations, the markets requiring licence verification API connections, and the depth of analytics and reporting required. We scope every project before confirming the timeline and give you a fixed cost before development starts.
Tell us the vehicle access model you operate, the markets you serve, and where manual booking or key handover is creating friction. We will scope the right platform and give you a fixed cost.