Operations system for a mobile car-wash fleet

The challenge

A Gulf company washes cars at the customer's location from a fleet of equipped buses. It had no single place that showed where each bus goes and when, what each wash earned, what each bus spent, or who is owed a loyalty reward.

What I built

• Scheduling: the office plans each bus's day on a daily and weekly schedule, with drag to reschedule, undo, and a search for the first free bus.
• Orders: customer, car and package, prices by car type, and before and after photos.
• Crew app: each bus crew runs its day from a phone, from today's timeline and the current wash to new orders and expenses with receipt photos.
• Invoices and expenses: PDF invoices with VAT, expenses including recurring ones, and monthly targets per bus with crew bonuses.
• Reports: revenue, expenses and profit per bus and per period, exported to PDF and Excel.
• Loyalty cards: a card designer, plus Apple Wallet and Google Wallet passes.
• WhatsApp messages: customer messages sent through a paced queue that respects opt-out requests.

Tech

I built it with Next.js and TypeScript on PostgreSQL, with background jobs on Redis. The interface is Arabic first, with full English. The crew app is an installable web app (PWA) that keeps working on a weak connection. There are four roles and an audit log of every change, and it runs in Docker with automated deploys and nightly off-site backups.

Outcome

I built it alone and delivered it in phases, and every note from the client went into the spec. The client's name is withheld, and the screenshots use demo data.