QUICKHAUL
Quikhaul is a roadside assistance app that connects stranded drivers with service providers. Customers request help and track arrival live, and providers manage jobs and earnings in one place.
Role
Product Designer
Duration
2 months
Category
Client Project
Tools
Figma, Claude

The business ran on phone calls and manual work, and neither could keep pace with the jobs.
Customers called to request a service, and a busy line meant missed customers. Providers were lined up by hand, records were manual and slow, and every update needed another call.
The Problem
The Solution
A dedicated request flow, a job queue with live status, and a provider dashboard that replace the phone calls and notes.

60% faster booking
From about 4 to 5 minutes by phone to about 2, roughly 50 to 60% faster



~0 Calls for Updates
From about 4 to 5 minutes by phone to about 2, roughly 50 to 60% faster

No Busy lines &
Organised records
Providers see active jobs, completed jobs, income, and records in one dashboard.

Understanding the client
Calls got missed, details got lost, and jobs went untracked.
A client debrief surfaced his main concerns: missed requests, unclear information, and no job tracking. A journey map of his phone process then showed where each one began.

Solution Ideation
Ideas and functionalities to include in my design
Progressive disclosure
Customer Information
Availability
Payment
Confirmation
Tracking
Comunication
Records
User FLows
Two connected flows, one for customers and one for providers.
Customer flow : Request a service on the web, join the queue, follow the job’s status, and see it through to completion.
Service provider flow : Log in with a phone number and OTP, and switch status on or off from the homepage. When online, a new job request comes in. The provider accepts it, or it auto declines. Then comes pickup, drop off, and job completed.

User FLows
A First Draft from Claude Is a Question, Not an Answer
After mapping the customer and provider flows, I used Claude to generate the first version of the screens from the flows. It gave me a fast starting point for every step, so I could spend my time reviewing and improving the design.

Design iterations
Buttons to Sliders
A review session with a senior designer changed how the product feels, one small decision at a time.
What went right
The design answered the real problems directly.
The arrival time on the live map ended the repeated “how long?” calls, and the service cards made a request quick to start.
What Improved
A Senior designer pointed out that a button can be tapped by accident, and a wrong tap on a job has real consequences. A slider takes a deliberate gesture, so every confirmation is intentional.

Adding badges to the Job's Info card instead of a new tab
The current job is front and center with a live status and a map. The next job waits below as “Up Next” with just the essentials, so the provider stays focused on one job at a time.



Information Architecture

Final Designs
The Finished Product
The final designs bring the customer and provider sides together. Customers request a service and follow their job on a live map. Providers go online, take jobs, and manage their work from one dashboard.


Learnings
Looking Back, Moving Forward
This project taught me that good design starts with listening. The client’s concerns and the map of his phone process shaped every decision after.
Designing a two sided platform taught me to think beyond individual screens. Every decision I made for the driver side had a direct consequence on the customer side. That systems thinking, understanding how two different users interact within one connected experience, is now central to how I approach any product problem.
For more enquiries or to grab a coffee, email me at mokshithmnagaraj@gmail.com


