Driver monthly plan
Fixed fee unlocks ride access for verified drivers.
Monthly-fee driver marketplace
Ride-hailing where drivers pay access, not commission.
A practical MVP for cars and motorbikes: riders book trips, drivers keep fares, and the platform earns from transparent monthly driver subscriptions.
Driver income
Fare retained by driver
Platform income
Monthly access fee
Vehicle types
Cars and motorbikes
Control layer
Verification and trace
Business model
Replace per-ride commission with subscription access.
Driver pays monthly. Platform does not tax every trip.
No ride commission
Driver keeps fare revenue after direct rider payment.
Hybrid option
Part-time drivers can use low daily pass or pay-per-active-day.
Governed locks
Expired subscription blocks new ride acceptance, not historical records.
MVP surfaces
Build three apps first: rider, driver, admin.
Rider app
- Register with phone or email
- Set pickup and drop-off
- Choose car or motorbike
- See fare estimate and driver distance
- Track ride and rate driver
Driver app
- Upload license, ID, vehicle, and insurance
- Pay monthly subscription
- Accept or reject ride requests
- See active plan and renewal date
- View ride history and rider ratings
Admin console
- Approve driver applications
- Monitor subscription status
- Handle disputes and safety incidents
- Suspend drivers with traceable reason
- Export evidence only with authority
Technical architecture
Start with boring, scalable parts.
The MVP does not need exotic AI. It needs accurate location, reliable matching, subscription enforcement, driver verification, and traceable admin decisions.
Mobile apps
React Native or Flutter for rider and driver apps.
Backend API
Node.js or Django API for auth, ride matching, plans, and notifications.
Database
PostgreSQL for users, rides, subscriptions, audit logs, and payments.
Maps
Google Maps or Mapbox for geocoding, live tracking, and distance pricing.
Payments
Stripe Billing, PayPal, or local provider for driver subscriptions.
Notifications
Firebase Cloud Messaging for trip requests, renewal reminders, and alerts.
Launch plan
Controlled rollout before public scale.
1
Pilot city
Pick one city, define legal requirements, and recruit a controlled driver cohort.
2
Driver economics
Validate fixed monthly fee, daily pass, and low-commission fallback.
3
MVP build
Ship rider request flow, driver acceptance, subscription status, and admin review.
4
Closed beta
Run limited trips with support, incident logging, and manual dispute handling.
5
Public launch
Scale only after payment, safety, and driver verification controls pass.
PMS4U control layer
Cheap commission is not enough. The platform needs governed execution.
Driver approval
KYC, license, insurance, vehicle status, and operating region must pass.
Subscription access
Only active or grace-period drivers can accept new ride requests.
Incident handling
Suspension, refund, payout hold, or evidence export needs an accountable operator.
Data export
No rider, driver, or trip evidence export without trace ID and authority reason.
Matching
Nearest eligible driver receives the trip first.
Safety
Every user, driver, dispute, and admin action has an owner.
Motorbike mode
Two-wheel rides use separate pricing, radius, and safety rules.