Map the service from visit to completed job
← All workService marketplace
Case / C
OnTheGo
Designing the full operating system behind a mobile car-wash booking.
ClientOnTheGo
ContextService marketplace
TimelineOne month, 2026
PlatformsCustomer website, admin portal, staff mobile app
Confirmed scopeProduct design · Service design · Prototype build · Booking UX
Project gallery
The work,
in context.
Selected product screens, flows, and presentation views from the published case study.
01Overview
The customer website, designed for booking from home
02Customer website
Homepage and side-by-side package comparison
03Customer website
Mobile homepage and service menu
04Customer website
Mobile booking starts with the service address
05Booking
Service details, booking, and package comparison on mobile
06Booking
Step 1 of 8 with the live order summary
07Staff app
Assigned jobs, today's shift, and the service checklist
08Staff app
Work schedule and a new job awaiting acceptance
09Staff app
Designed for use on site beside the vehicle
10Before and after
The earlier WordPress site beside the new service product
The problem
Start with what
needed to change.
The existing WordPress site could sell wash packages, but it did not reflect how a mobile service actually operates. Each job depends on a location, vehicle, time window, travel, equipment, staff acceptance, and on-site quality control—most of which was coordinated manually.
Role in the workWorking directly with the owner, Ali mapped the service, designed the customer website, eight-step booking flow, admin portal, and staff app, then built the working prototype for first tests with customers and staff.
The process
Design customer, staff, and admin journeys
Build a working prototype in one month
Prepare user research and first operational tests
Inside the product
Decisions that connect
the whole experience.
Customer website
The site answers what the service is, what it costs, how it works, and whether it covers the visitor's area. It includes four packages, add-ons, a service-zone check, and an email-verified customer portal.
Booking in eight steps
One question per screen keeps mobile booking focused. A persistent summary shows package, travel and equipment fee, estimated tax, duration, buffer time, and total before the customer commits.
Staff and admin tools
Field staff see their shift, accept or decline jobs, navigate to customers, follow a required checklist, upload before-and-after photos, and report issues. Admins manage the same jobs from an operational portal.
Prototype before scale
The earlier WordPress site worked as a brochure. This prototype turns the business into a service product and creates something concrete enough to test before committing to a full operational launch.
The solution
What the work
made possible.
Three connected interfaces share one job state: transparent customer booking, an on-site staff app with acceptance and quality controls, and an admin portal for orders, services, staff, payments, and job status.
Verified outcomeA working prototype was completed in one month for research and first tests. It has not run live operations, so no customer, conversion, or revenue results are claimed.
Working prototype designed and built in one month
Verified in Ali's published case study.
Booking divided into eight short steps with a live total
Verified in Ali's published case study.
Connected customer, staff, and admin portals
Verified in Ali's published case study.
Built to support user research before launch investment
Verified in Ali's published case study.