Problem
Wholesale vehicle buyers and sellers lose time when fresh inventory, offer status, and lifecycle changes are spread across slow manual workflows.
Project case study
DealerFlow
Vehicle monitoring and notification platform that aggregates inventory updates and alerts users to relevant deals.
Project facts
Theme
Operational Workflow Software
Current state
Beta Pilot
My role
Sole backend engineer and mobile developer
Core constraint
State consistency: vehicle lifecycle transitions must keep buyer/seller state safe across concurrent offer and inventory workflows
Outcome
Beta pilot with working mobile workflows for buyer matching, seller inventory management, and real-time notification delivery
Approach
A concise problem → system → evidence structure so the engineering story is easier to inspect.
System design
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.
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.
Stack
NestJSBullMQPostgreSQLPrismaExpo React NativeRedis
Evidence
The strongest proof is the mobile workflow itself paired with the notification and inventory lifecycle model behind it.
Mobile screenshotNotification pipelineInventory lifecycle model
Related work
Projects in a similar problem family.
Operational Workflow SoftwarePrototype
NAICS Startup Planning System
Software that guides founders through structured startup planning workflows instead of vague brainstorming.
My Role
Sole architect and full-stack engineer
Outcome
Working planning engine with rules-based role generation, income modeling, and explainability views across NAICS hierarchy
Next.jsPrismaSQLiteZod
Read case study