Skip to content
All work
On-demand professional driver booking

ProDriva

ProDriva books a vetted professional driver for a car the customer already owns. The product turns an arrangement normally made through personal referrals and phone calls into a scheduled booking with a named driver, an agreed fare and a record of the trip.

Visit prodriva.ng
prodriva.ng
ProDriva booking page showing pickup location, destination, date and time fields, and an estimated fare.
The booking flow: pickup, destination and schedule, with the fare estimated before the trip is confirmed.

Problem

  • Hiring a driver usually depends on personal referrals, with no verification behind the recommendation.
  • Bookings are arranged over calls and messages, so there is no record of what was agreed or when.
  • Price is negotiated per trip, and neither side is certain of the cost until it is over.

Approach

  • Make vetting part of the product rather than a claim on a page — the customer books against a driver who has been through a defined process.
  • Quote the fare before the booking is confirmed, so the commercial terms are agreed rather than discovered.
  • Model a booking as a scheduled commitment with a defined lifecycle, so both sides know its current state.
  • Keep payment and its paperwork inside the product, so a trip leaves a record rather than a transfer receipt in someone's phone.
  • Answer the questions that decide whether someone books at all — safety, payment and what happens if a trip runs over — inside the product itself.

Solution

  • Booking flow taking pickup, destination, date and time, with geolocation to fill in the current location.
  • Two service lines from one flow: a driver for the customer's own vehicle, or a vehicle and driver together across saloon, SUV, minivan and bus classes.
  • Fare estimation shown before a booking is confirmed, with additional time settled at the end of the trip.
  • A stored-value wallet alongside online gateway payment, with the method chosen at booking confirmation.
  • Invoices and receipts issued against trips and kept in the customer's account.
  • A customer dashboard covering the active journey, trip history and notifications.
  • Safety, payments and FAQ content built into the product to address the objections that block a first booking.

Technology

  • .NET
  • C#
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • PostgreSQL
  • Docker

Results

[CONTENT NEEDED]

Results are published only once measured figures have been verified and approved for release.

Screens

Customer dashboard
ProDriva customer dashboard showing booking options, wallet balance, active journey, recent bookings, invoices and receipts.
Services, wallet balance, active journey, trip history and payment documents in one place.

Have something worth building?

Tell us what you're building, what isn't working, or what you want to improve.