Trusted Carpool Network

Trusted Carpool Network is a verification-first commuter platform designed to connect professionals travelling along similar routes while prioritising safety, trust, and reliability. Rather than simply matching drivers and passengers, the platform establishes trust before every journey through identity verification and structured commuter matching. The idea emerged from observing a recurring challenge faced by early-morning commuters in Lagos, where finding transportation often meant choosing between convenience and personal safety. Understanding that challenge became the foundation for every product decision that followed.

During repeated early-morning journeys along the Mowe–Ibafo–Berger corridor in Lagos, I observed professionals standing by the roadside between 5:00 a.m. and 6:00 a.m., relying on private vehicles for transportation. For many commuters, accepting a ride from an unfamiliar driver had become a routine part of getting to work. While transportation was available, trust was not. Every journey required commuters to make a rapid decision with very little information about the driver or the vehicle. The choice often came down to balancing punctuality against personal safety. These observations revealed that the real problem was not the lack of transportation, but the absence of a trusted way for verified commuters to connect with one another. That insight became the foundation for the product vision

The vision was to create a trusted commuter network where professionals could confidently connect with verified drivers and passengers travelling along similar routes. Instead of leaving trust to chance, the platform would establish it before every journey through identity verification, structured matching, and a community built around accountability. Rather than becoming another ride-hailing service, the goal was to build a verification-first platform that enabled safer daily commuting while strengthening trust among commuters. This vision guided every product decision that followed.

The user journey was designed to reduce uncertainty at every stage of the commuter experience. Rather than focusing only on booking a ride, the journey prioritised trust before, during, and after every trip.

The MVP was intentionally scoped to validate the core hypothesis: verified commuters would be willing to use a trusted platform to find and share trips with people travelling along similar routes. Features were prioritised based on their ability to establish trust, enable successful matching, and collect feedback for future iterations.

• ✓Validate demand for a verification-first commuter network.
• ✓Enable verified drivers and passengers to create and join trips.
• ✓Match commuters travelling along similar routes.
• ✓Build trust through identity verification and post-trip feedback.
• ✓Capture user feedback to inform future product iterations.

The Product Requirements Document (PRD) translated the product vision and MVP into a structured implementation plan. It aligned product goals with engineering execution by defining the scope, functional requirements, user flows, assumptions, constraints, and success criteria for the first release.

• •Product goals and success metrics
• •MVP scope and feature prioritisation
• •Functional requirements
• •User flows and key scenarios
• •Assumptions and constraints
• •Acceptance criteria

Acceptance criteria transformed user stories into testable outcomes, ensuring every feature had clear conditions for completion before development began.

• •Clear success conditions for every user story
• •Functional behaviour defined before development
• •Support for developer implementation
• •Support for QA validation
• •Reduced ambiguity across the team

The roadmap organised product delivery into clear phases, ensuring the team validated the core problem before investing in more advanced capabilities. Each phase built on the learning from the previous one.

Wireframes translated product requirements into visual user flows, allowing key interactions to be validated before investing in detailed UI design or development.

The database design transformed product concepts into a structured data model, ensuring users, routes, bookings, and verification records accurately reflected real-world commuter interactions while supporting scalability and maintainability.

The REST API translated product capabilities into clear, predictable contracts between the frontend and backend. Each endpoint represented a user action, ensuring the system remained modular, testable, and easy to evolve.

The Trusted Carpool Network is organised into a layered architecture where each layer has a clear responsibility. This separation makes the platform easier to understand, maintain, test, and evolve as new features are introduced.