Skip to content
David BraunAI Systems & Platform Engineer

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

DealerFlow mobile feed showing newly published wholesale inventory.

Problem

Wholesale vehicle buyers and sellers lose time when fresh inventory, offer status, and lifecycle changes are spread across slow manual workflows.

Core Constraint

State consistency: vehicle lifecycle transitions must keep buyer and seller state safe across concurrent offer and inventory workflows

Solution / What I Built

I built a mobile system with a NestJS API, BullMQ-backed worker processing, persisted notifications, and inventory lifecycle rules. 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.

Technical Stack

NestJSBullMQPostgreSQLPrismaExpo React NativeRedis

Applied Relevance

Where the pattern matters

  • Wholesale inventory discovery and buyer matching.
  • Mobile inventory, offer, and inquiry workflows.
  • Background notification processing tied to inventory changes.

Implementation and evidence

Implementation details and the artifacts available for review.

Mobile inventory feed

Linked artifacts

The captured mobile feed shows how newly published wholesale inventory appears to a buyer.

  • The screenshot is an existing application capture.
  • Buyer matching, seller inventory, and offers are the pilot workflows described in this case study.
Open the mobile feed screenshot

Implementation scope

Implementation notes

I built the NestJS backend and Expo mobile client around inventory changes and the notifications they produce.

  • PostgreSQL and Prisma store application state.
  • BullMQ and Redis handle background notification work.
  • Inventory and offer transitions are the central state-consistency constraint.

Scope and limitations

Interpreting this work

  • The system remains a beta pilot; broad adoption, production scale, and long-term reliability are not established by this case study.
  • The public screenshot shows the inventory feed. It does not independently demonstrate every lifecycle transition or queue failure mode.

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 study
R&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
Back to all work