Enterprise · Transportation
Corporate Mobility
A corporate ride-booking app connected to a car service’s existing dispatch workflow. Delivered through Dicty.
The Vision
Let employees request and manage rides directly through the app, without coordinating with administrators or exchanging WhatsApp messages to arrange each trip.
My contribution
Through Dicty, I contributed the frontend, backend, system architecture, cloud infrastructure, and integration with the car service’s existing dispatch system.
- Status
- Delivered through Dicty
- Year
- 2026
- Role
- Developer
The problem
Manual ride coordination created friction as a car service took on a major multinational with many employees in Argentina.
The app had to let people book rides directly while integrating safely with the service’s existing booking system and preserving separation between corporate accounts.
The product
Employees can request a trip on demand or schedule one in advance, for themselves or for a guest. Company supervisors manage permissions and monitor usage across their teams.
The responsive web app behaves like an installable mobile application while remaining connected to the client’s existing dispatch workflow.
Decisions that matter
An intuitive experience, with distinct roles
Employees get a straightforward way to book and manage rides, while each company’s administrators can configure their own booking rules. Separate roles let administrators set parameters such as minimum booking lead time and the time windows in which a ride request must notify a supervisor, without adding complexity to the employee experience.
Multi-tenancy at the database layer
PostgreSQL row-level security separates each company’s trips and data at the database layer, alongside application permissions. Employees and administrators work within their own corporate account, so isolation does not depend on API filtering alone. Database roles and policies reinforce that boundary across booking and management workflows.
Fit the existing dispatch workflow
The app gives employees a new booking experience while keeping the car service’s existing dispatch system in place. A typed FastAPI backend connects ride requests, confirmation codes, modifications, and cancellations to that operation. Trip updates and acknowledgements flow back to the app, keeping both sides connected throughout the journey.
The integration
From the employee’s request to the dispatch system — and back.
A confirmed booking, in one exchange.
The dispatch API returns a confirmation code. The trip is scheduled in the existing system and shown as confirmed in Corporate Mobility.
The API also supports trip modifications and cancellations.
Delivery & validation
What’s built
Delivered an installable web app where employees can request, schedule, modify, and cancel rides, while company administrators manage permissions and booking rules. The app integrates with the car service’s existing dispatch system to create bookings, receive confirmation codes, and exchange trip updates and acknowledgements, keeping the employee experience connected to the operation without a separate manual coordination flow.
What to measure next
Confirm rollout and adoption with the client. The next useful measures are completed bookings, dispatch exceptions, and the effort needed to coordinate each trip.
Under the hood
My scope
- Frontend
- Backend
- System architecture
- Existing dispatch integration
- Database architecture
- Manual testing
- Cloud infrastructure
Technology
- React 18
- FastAPI
- PostgreSQL 16
- AWS
- Terraform
- PWA
- Claude Code & Codex
Explore the workflows
Trip changes and operational controlsModify or cancel a trip
Follow how an employee changes or cancels a booking through the connected travel workflow.
Manage corporate travel
Explore the supervisor’s view of corporate trips and operational controls.