Problem
Wholesale vehicle buyers and sellers lose time when fresh inventory, offer status, and lifecycle changes are spread across slow manual workflows.
Pilot case study
Pilot platform that automates inventory alerts, buyer matching, and seller workflows for wholesale vehicle activity.
At a glance
Delivery stage
Pilot
Current state
Beta Pilot
My role
Sole backend engineer and mobile developer

Wholesale vehicle buyers and sellers lose time when fresh inventory, offer status, and lifecycle changes are spread across slow manual workflows.
Built as a production-lean mobile system with a NestJS API, BullMQ-backed worker processing, persisted notifications, and lifecycle-safe inventory transitions. Buyers get scored matches and alerts, while sellers manage inventory, offers, and inbound inquiries from a mobile workflow.
Beta pilot with working mobile workflows for buyer matching, seller inventory management, and real-time notification delivery
This section shows the operational logic behind the build, not just the user-facing surface.
Core constraint
State consistency: vehicle lifecycle transitions must keep buyer and seller state safe across concurrent offer and inventory workflows
This page separates what is already visible from what is still being prepared, so the proof layer can grow without pretending unfinished artifacts already exist.
Real artifacts stay visible. Missing artifacts are labeled directly so this page stays honest and ready for stronger proof later.
The mobile workflow shown on this page is still the clearest existing proof surface for DealerFlow.
The system architecture is real, but the dedicated diagram and lifecycle artifact still need to be added.
This system already has real operational surfaces even though the proof set is still thinner than it should be.
DealerFlow still needs stronger embedded artifacts to become a more believable flagship.