All work
WebiOSAndroidSaaS
AutoMexa
Dispatch, driver, and customer in one platform.
Portfolio: Internal platformYear: 2025Status: Public site + private ops · v1.0.0Timeline: Platform architecture + three surfaces in ~14 weeks.
Inspectable proof
Open the shipped product.
Every public surface we can share is linked here. Some admin dashboards are private; the client-facing product is inspectable where available.
Real app screens
View on App Store See the public build.
The problem
Small-to-mid service operators typically run on SMS, Google Sheets, and three disconnected tools. They can't see real-time job status, can't quote consistently, and can't scale past one operator's phone.
What we shipped
A single platform with three surfaces: a web control center for the operator, a native customer app for bookings and tracking, and a native driver app with live job flow. All three share one NestJS backend and a single source of truth.
Surfaces
Web + 2 Apps
Public site
automexa.mx
Stack
Full-stack TS
Outcomes
- Public landing page at automexa.mx, with the operator control center kept private
- Real-time job state synced across all three surfaces
- Role-based access (admin, dispatcher, driver, customer)
- Ready to onboard new fleets without code changes
Stack
Next.jsNestJSExpoPostgres
Services
- · Platform Architecture
- · Web App
- · Mobile Apps
Want a system like this for your operation?
Book a 20-minute call and we'll scope a version for your team with a fixed timeline, fixed scope, agreed before we start.
Next caseFix My Swing