RTO Tricycle Business Admin Platform Design
Jolaoluwa Olatunji
Like this project
Posted Jan 22, 2026
Designed a scalable admin platform for a Ride-to-Own tricycle business.
Product Description
A role-based admin platform powering a Ride-to-Own (RTO) tricycle business, designed to manage riders, fleet operations, contracts, payments, and compliance at scale. The system translates complex, offline-heavy workflows into a centralised, auditable product built for operational efficiency and revenue control.
My Role
Lead Product Designer & Systems Strategist
Owned end-to-end admin experience across the web
Defined information architecture, role-based access control, and system states
Translated business rules into scalable product flows
Worked closely with engineering, operations, and finance to reduce ambiguity and speed up delivery
Authentication
What I Designed
Admin login with role-aware access control
Session handling tied to permission scope
Immediate access revocation on suspension
Why It Matters
Prevents unauthorised access to sensitive financial and rider data
Establishes trust and accountability from the first interaction
Supports compliance and audit requirements
Dashboard
What I Designed
Status-driven overview (riders, fleet, payments, exceptions)
Real-time notifications for actions requiring attention
Activity logs for traceability and audits
Why It Matters
Helps ops teams act quickly without digging through modules
Shifts the dashboard from “analytics” to operational command centre
Reduces missed follow-ups and manual tracking
Riders
What I Designed - Full rider lifecycle management:
Onboarding & KYC
Contract state (applied, active, defaulted, completed)
Payment history and ownership progress
Clear state indicators and next-action guidance
Why It Matters
Centralises rider data previously spread across paper and spreadsheets
Reduces ambiguity around rider status
Enables predictable weekly revenue tracking
Fleet
What I Designed
Fleet inventory with real-world identifiers (plate number, model, status)
Assignment to riders and contracts
Maintenance history and availability tracking
Why It Matters
Prevents asset misuse and data loss
Improves fleet utilization
Creates a clean link between physical assets and digital contracts
Settings
What I Designed
Granular role-based access control (RBAC)
Permission matrix mapped to navs and actions:
No access / View only / Edit
Role creation, editing, suspension, and audit logging
Immediate permission updates without logout
Why It Matters
Enables safe delegation across operations, finance, and maintenance
Reduces risk of human error and fraud
Scales the business without centralising power in one admin
Conclusions
Designing for RTO at scale is less about screens and more about state, permissions, and enforcement.
The biggest leverage came from treating the admin platform as a business control system, not an internal tool.
Clear role boundaries and auditable actions unlocked faster operations without increasing risk.
Grounding the system in real-world entities (riders, tricycles, workshops, contracts) reduced operational errors and instances of trust breakdown.
Key Learnings
State-driven design beats feature-driven design in operational products; most complexity lives between statuses, not screens.
Permissions are a product feature, not an afterthought; getting them right early prevents costly rework.
Admin UX should optimise for speed, clarity, and prevention, not exploration.
Early alignment with ops and finance dramatically improves both product confidence and engineering velocity.