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
Context
Pilot
Current state
Beta Pilot
Role
Sole backend engineer and mobile developer
Solution / What I 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.
Results
Beta pilot with working mobile workflows for buyer matching, seller inventory management, and real-time notification delivery
Architecture
The pipeline is shown as explicit stages so the system boundary is inspectable.
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 and seller state safe across concurrent offer and inventory workflows
Technical Stack
NestJSBullMQPostgreSQLPrismaExpo React NativeRedis
Applied Relevance
Where the pattern matters
- Workflow analysis
- Operational software design
- Prototype planning
- System architecture review
Proof Surfaces
Available artifacts are labeled directly. Missing visuals stay as placeholders until real screenshots are added.
System Walkthrough
Available nowThe mobile workflow shown on this page is still the clearest existing proof surface for DealerFlow.
- Buyer-facing inventory feed and match workflow are visible through the mobile screenshot.
- Pilot status is real, but the fuller walkthrough needs stronger artifact coverage than it has today.
Architecture / Flow (to be added)
In progressThe system architecture is real, but the dedicated diagram and lifecycle artifact still need to be added.
- Notification pipeline diagram is still to be added.
- Lifecycle-safe inventory model artifact is in progress.
Operational Surfaces
Available nowThis system already has real operational surfaces even though the proof set is still thinner than it should be.
- Mobile buyer workflow for incoming inventory.
- Seller inventory and offer management flow.
- BullMQ-backed notification handling for match and lifecycle changes.
Artifacts & Evidence (to be added)
In progressDealerFlow still needs stronger embedded artifacts to become a more believable flagship.
- Dedicated lifecycle diagram to be added.
- Notification and queue artifact to be added.
- More complete mobile workflow proof to be added.
Limitations
What this does not claim
- This page describes the current proof available for the project.
- Additional screenshots, logs, or usage artifacts should be added before making stronger claims.
Next Improvements
Reasonable next steps
- Add stronger screenshots or walkthrough artifacts.
- Document validation checks and edge cases more completely.
- Tighten public write-up as the system matures.
Related Case Studies
More portfolio context.
Public Production ProofProduction
VIFG Nonprofit Platform
Production platform and delivery stack supporting a nonprofit serving the visually impaired community.
ReactTypeScriptViteDocker
Read case studyR&DActive Build
DGM
Workflow orchestration layer in active development for managing state, decision flow, and human review inside StormIQ.
PythonFastAPIWorkflow GraphsQueue-backed Jobs
Read case study