A unit lands, sits in prep for three weeks, gets quoted at two different prices by two salespeople, and sells on a payment schedule the dealership manages itself. Firelinkx builds dealership software that holds that whole history against the vehicle, with cost and margin visible only to the people entitled to see them.
Dealer principals, sales managers, administrators, and accounts staff who need to answer where a unit is, what it truly cost, who is chasing it, and what the customer still owes, without reconstructing it from a WhatsApp thread and three spreadsheets.
Purchase price, freight, duty, port charges, and preparation live in different places, so the true cost of a specific unit is worked out at the moment someone is negotiating on it, which is the worst possible time.
Without one current price per unit, with a record of who changed it and why, the dealership finds out about the discrepancy from the customer who was quoted the higher one.
An enquiry arrives on a salesperson's WhatsApp and stays there. When they are off, on leave, or gone, the dealership cannot say who was interested in what or what was promised.
Dealer-managed payment schedules run for months after delivery. Deposits, receipts, allocations, and overdue follow-up need to hang off the same sale record, or arrears become an exercise in cross-checking receipt books.
The vehicle is the spine. Every cost, conversation, approval, and payment attaches to a unit, so the history can be read off one screen instead of assembled from four.
Open the unit record with its identifying details, where it came from, what was paid, and the milestones expected before it can be sold.
Shipment, arrival, customs, and each approved cost component post against the unit as they happen, so landed cost is a number the system already knows.
Preparation work is assigned and its results recorded. A unit does not enter saleable stock until the completion rule is met, which stops half-prepared vehicles being sold on a Saturday.
Location, status, days in stock, and the current price with its version history. Cost and margin sit behind a permission so sales staff can quote without seeing what the dealership paid.
Source, vehicle of interest, assigned salesperson, what was discussed, and the next action with a date on it. A lead with no next action shows up as one.
The offer records what was agreed, any price exception and who authorised it, and the trade-in appraisal that supported the number.
The agreement, the deposit, the receipts, and the dealer-managed payment schedule, with overdue items assigned to a person for follow-up.
Required documents are confirmed present, handover conditions reviewed, the vehicle released, and the delivery evidence retained against the unit.
One unit record carries the whole history, so a question about a car in 2024 is still answerable in 2027.
Salespeople manage their own pipeline while managers can see ownership and progress without asking for a verbal update.
Each of these records a named approver and a reason, because these are the decisions that get questioned months later.
Built from the same records the floor is already keeping, so a report costs a click and nobody prepares it.
The system runs the dealership's vehicles, customers, staff, sales, and collections. Publishing stock to a website and connecting outside services come after the internal record is trustworthy, because publishing an unreliable stock list is worse than publishing nothing.
A dealership system is a full custom application with restricted data and its own approval rules, so the number follows how much of the operation is in the first release.
From US$199
A Tech Roadmap Audit covering what to build, what to buy, and what to leave alone, with cost ranges and a sequence. Credited toward the project if you build with Firelinkx.
$4,500 - $6,500
Usually stock and pricing with cost held behind a permission, or the lead pipeline through to offer. One area, running on real units, before the next is added.
Paid discovery first
Restricted margin data, dealer-managed collections, and approval authority put this in the platform lane, where the build quote follows discovery. Local platform builds usually start from $4,000 to $8,500 after discovery, with corporate work higher.
Every proposal separates the one-time build from the monthly operations that follow it. See full pricing for how both are structured.
Review representative records, current tools, staff responsibilities, handoffs, delays, and exceptions.
Specify records, states, permissions, approvals, integrations, reports, and acceptance checks.
Deliver working stages that staff can test against representative scenarios before the scope expands.
Plan data migration, training, deployment, support responsibilities, and the operational cutover.
Bring a representative job, record, exception, or report. Firelinkx will help define the users, controls, integrations, and first useful release.