Nothing Falls Through Between the Test Drive & the Callback
Bell System puts a dealership’s customers, deals, appraisals, and appointments on one record that the sales floor and the management team read at the same time. A test drive booked on the floor, an appraisal completed, or a proposal sent all write to the same timeline, so a manager sees the state of the pipeline as it forms rather than at the end of the month.
Project: Bell System · Automotive retail
Project Overview
Sector: Automotive retail
Industry context: Dealership sales, trade-in appraisal, & finance
Product: Bell System, a dealership sales platform across mobile & web
Build focus: Deal pipeline with stage tracking, customer & vehicle records, activity timelines, appraisal & finance triggers, manager reporting
Dealership selling is a long sequence of small commitments. A lead arrives, gets contacted, drives a car, trades one in, receives a proposal, negotiates, and either signs or disappears. Bell System was built so that sequence lives in one place, visible to the consultant working it and to the manager responsible for the floor, with the same information in front of both.
Key Features
One Timeline Per Customer
Contact details, vehicle of interest, trade-in, and every logged interaction on a single record, with stage position visible from new lead through to closed. The gain is shared visibility, which removes the double bookings and the missed follow-ups at their source.
Alerts While They Still Matter
Appointments, appraisals, proposals, and finance events notify as they occur rather than appearing in a monthly summary. The gain is response time, which in vehicle retail is most of the difference between a sale and a lead that went quiet.
Two Views of the Same Data
A mobile screen built around a consultant’s day and a browser dashboard built around pipeline state, reading one source. The gain is management that coaches during the month instead of reviewing after it.
Inside the Product
Get It Out of the Notebook
Replacing a diary, a notebook, and nine separate complaints with one shared record is the kind of problem worth structuring properly at the start.
Scoping happens in days. Working software follows in months. A senior engineer owns the architecture from the first conversation through to release.