Bellboy
Delivery booking site and rider onboarding for a delivery company in Australia.
Outcome
A quote-to-booking flow and a rider onboarding flow that collects every required document before review.
- Year
- 2024
- Role
- Front end and admin
- Status
- Client work
- Stack
- Next.js 14, React, MUI, Tailwind, react-query, Formik, Yup, AWS S3
The problem
A delivery quote depends on distance, vehicle, and parcel size.
Rider onboarding needs a verified phone number, a photo, a signature, and documents before anyone can review the application.
What I built
The public site quotes a delivery from distance, vehicle, and parcel size, then hands off to booking.
Rider recruitment pairs a marketing page with an application flow: OTP phone verification, photo and signature capture, document upload.
Admin screens manage rate cards, rider commission, and transport rules.
Surfaces
- Public site
- Rider application
- Admin
- Team API
Decisions
Pricing rules live in admin data rather than hardcoded copy.
The application collects every document before review.
The marketing site and the operations tools stay in separate apps.
Scope
I built the front end and admin tools. Another developer built the backend and payment integration.
Team context
The backend was a NestJS/Prisma service with RabbitMQ, Adyen payments, S3 media, Firebase, and Twilio. I built the front end and admin against its APIs.