Concept · discovery

Hamraah / shared commute

A better commute, shared with confidence.

A recurring carpooling concept for riders and drivers, paired with an employer commute programme. From the first match to the last-mile update, every handoff has a clear next step.

For India and the Middle East · initial corridor and service model under validation

Hamraah concept experience with illustrative synthetic data. A rider commute app is shown alongside an employer commute programme dashboard.
Concept experience · illustrative synthetic data Concept preview

The buyer problem

Coordination is the real journey.

Sharing a car is only one moment. The service has to coordinate expectations before pickup, respond when reality changes, and give programme owners a responsible way to learn.

01

The commute starts before the car arrives

Recurring schedules, route fit, pickup points and preferences live across separate conversations. Hamraah is being designed to bring those decisions into one clear plan.

02

A delay should not become a mystery

When a driver is late or a pickup changes, riders need a timely update and a practical alternative—not another thread to monitor.

03

Employers need a programme, not a group chat

Transport and workplace teams need a way to understand demand, seat use, punctuality and safety exceptions without exposing every personal journey detail.

Proposed capabilities

One routine. Every handoff considered.

The concept connects the rider, driver and employer experience without treating them as the same user or giving them the same information.

Recurring commute plans

Set home and work anchors, arrival windows, weekly days and return journeys as one repeatable routine.

Context-aware matching

Explore matches by route, timing, available seat and stated preferences, including women-only options where supported.

Coordinated pickups

Keep the agreed meeting point, vehicle details, live trip status and driver-rider messages in one place.

Exceptions with a next step

A late-driver scenario can trigger an update, revised arrival estimate and an alternative offer for the rider to review.

Employer programme view

A separate operational view for demand, seat utilisation, punctuality and safety exceptions—with programme measures still under validation.

The operating flow

From a weekly plan to a programme that learns.

Six connected moments make the service legible to the person travelling and the team responsible for the programme.

  1. 01

    Plan

    Choose recurring days, route anchors, arrival window and preferences.

  2. 02

    Match

    Review a proposed shared journey with route, time and seat context.

  3. 03

    Coordinate

    Confirm the pickup and keep both sides aligned as the trip approaches.

  4. 04

    Respond

    See a delay, receive the update and choose any offered alternative.

  5. 05

    Arrive

    Complete the trip, review the illustrative cost split and leave feedback.

  6. 06

    Improve

    Let authorised employer teams review programme-level patterns and exceptions.

Safety & trust

Trust needs an operating model.

These are product requirements being explored, not claims about a live safety service. Market-specific processes and response ownership remain discovery work.

Identity before introductions

Verified identity is a core product requirement. The verification method and eligibility rules remain subject to market validation.

A journey someone can follow

Trip sharing, visible vehicle and driver details, and clear pickup records are part of the proposed experience.

Help that is easy to find

SOS and in-trip support are designed into the journey, not buried in settings. Response ownership must be proven before launch.

Preferences with respect

Matching can account for stated preferences, including women-only journeys, while preserving clear user choice and control.

A view for each role

Shared journey. Different responsibilities.

Rider

A suitable recurring match, a clear pickup, timely exception updates and accessible support.

Driver

A planned route and schedule, understood pickup details, clear rider coordination and trip review.

Employer

A programme-level operating view with access, privacy and useful measures defined through discovery.

What we are validating

Evidence before availability.

No public launch, service coverage or performance outcome is being claimed. The roadmap begins with a bounded question and earns each next step.

01Now

Concept and discovery

Testing the proposition with commuters, drivers and employer teams; mapping real commute routines, trust requirements and exception ownership.

Problem interviews · corridor selection · service blueprint
02Next

A bounded service pilot

One employer or commute corridor, with manual operational support where needed and success measures agreed before a pilot begins.

Match quality · pickup reliability · support workload · participant trust
03Before launch

Operational and market readiness

Validate transport, cost-sharing, insurance, payment, privacy and safety obligations for the chosen jurisdiction with appropriate professional review.

Reviewed operating procedures · validated economics · go / no-go decision

Questions, answered honestly

Before you share the road.

The concept is a starting point for discovery, not a promise of a finished service.

Is Hamraah available to use today?

No. Hamraah is a Concept · discovery product. The experience on this site illustrates the proposed service; it is not a live booking or matching service.

Is Hamraah a general ride-hailing app?

The concept focuses on recurring shared commutes and employer commute programmes. It is not positioned as an on-demand taxi service. The initial operating model is intentionally narrow so route fit, reliability and support can be studied in context.

What would an employer commute programme include?

The concept includes programme-level views of demand, seat utilisation, punctuality and safety exceptions. Exact measures, access controls and employee privacy boundaries are discovery questions, not committed capabilities.

How would safety and support work?

Verified identity, trip sharing, SOS, in-trip support and clear exception handling are design requirements. Verification partners, support staffing, escalation paths and jurisdiction-specific obligations still need to be validated before any service launch.

How can I contribute to discovery?

We welcome conversations with employers, commuters, drivers and mobility practitioners in India and the Middle East. Bring one concrete commute problem, its constraints and the outcome you would want to measure.

Explore the proposed service

Bring us one commute that needs to work better.

See the rider, driver and employer concept, or help shape the questions a real-world pilot would need to answer.