Context and challenge
Vehicle rental is both a customer product and an operations system. Behind a booking sits a fleet with changing availability, vehicle information, payment steps, and a team that needs a reliable view of what is happening now.
Allo Driver needed backend services and an administrative console that reflected those day-to-day constraints. The core challenge was not simply displaying vehicles; it was connecting fleet data, booking workflows, and operational visibility in one coherent product.
My role and scope
I contributed across backend and product engineering, with a focus on the services and internal tools that support the rental workflow.
The work included:
- fleet and vehicle management;
- booking lifecycle implementation;
- operational dashboard capabilities;
- data access with PostgreSQL and Prisma;
- Mobile Money integration points;
- a web console built with Next.js and TypeScript.
Engineering approach
The system was shaped around the business workflow. Fleet records form the operational source of truth, while bookings describe how a vehicle moves from available to requested, confirmed, and handled by the team.
Keeping those responsibilities distinct makes the model easier to understand and reduces accidental coupling. The administrative interface can then present the right operational view without embedding business rules inside UI components.
The console was designed as a working tool rather than a passive reporting screen. Information hierarchy, status visibility, and direct access to common actions were important because the value of the interface depends on how quickly the team can understand and act on the current situation.
Key decisions
- Model the workflow explicitly. Booking states communicate what has happened and which actions are valid next.
- Separate domain rules from the interface. Backend services own business behavior; the console consumes predictable contracts.
- Use one operational source of truth. Fleet and booking information should not drift between customer-facing and administrative experiences.
- Make dashboards actionable. The console prioritizes current operations and decisions over decorative metrics.
Outcome and next steps
The result connects the customer-facing rental experience with the internal workflows required to operate it. The team can manage vehicles, follow bookings, and work from a consolidated operational view, while the underlying services support the product’s payment and data needs.
Future evolution should continue around auditability, fine-grained permissions, and operational notifications. These capabilities become increasingly valuable as the fleet, booking volume, and number of internal users grow.
