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
DealerFlow
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
What was built
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.
Result
Beta pilot with working mobile workflows for buyer matching, seller inventory management, and real-time notification delivery
How the system was structured
This section shows the operational logic behind the build, not just the user-facing surface.
Key system pieces
Worker pipeline computes match scores and notification fan-out.
Vehicle lifecycle rules keep buyer and seller state transitions safe.
Mobile-first flows make the software operational instead of dashboard-only.
Core constraint
State consistency: vehicle lifecycle transitions must keep buyer/seller state safe across concurrent offer and inventory workflows
Stack
NestJSBullMQPostgreSQLPrismaExpo React NativeRedis
Supporting proof
The strongest proof is the mobile workflow itself paired with the notification and inventory lifecycle model behind it.
Mobile screenshotNotification pipelineInventory lifecycle model