DealershipCRMInventory

Case Study

Dealership Management System

A vehicle dealership running its sales operation across spreadsheets and messaging apps was losing leads it never knew it had. DeckPro built a purpose-designed management system that gave the entire team one place to work from.

Inventory, buyer enquiries, test drive bookings, follow-up tasks, and management reporting — all disconnected, all manual, all costing the business deals. The new platform unified every part of the sales workflow into a single operational system built around how a dealership actually runs.

---

Project Overview

| | | |---|---| | **Industry** | Vehicle Retail / Automotive | | **Timeline** | 8 weeks | | **Services** | Product Strategy, System Architecture, UX Design, Custom Software Development, Dashboard & Reporting | | **Tech Stack** | Next.js, Supabase, PostgreSQL, Tailwind CSS, Role-based Access Control | | **Project Goals** | Replace fragmented tools with a single dealership platform covering inventory management, lead tracking, test drive scheduling, follow-up automation, and live management reporting |

---

Problem / Challenge

### What was broken

The dealership's sales operation ran across a spreadsheet for inventory, a shared WhatsApp group for leads, individual staff notes for follow-ups, and a paper diary for test drives. Nothing was connected. Information existed in multiple versions simultaneously — different staff members holding different facts about the same vehicle or the same buyer.

### Why staff struggled

When a buyer called about a specific vehicle, the salesperson had to stop the conversation, check a spreadsheet, cross-reference with a colleague, or physically check the floor to confirm availability, specification, and price. That lag is unprofessional in front of a buyer and slow enough to cost the deal entirely.

Follow-ups relied entirely on individual memory and goodwill. There was no system that reminded anyone about a buyer who needed a callback, a test drive that needed confirming, or a deal that had gone quiet. If the salesperson forgot, the lead was gone — and the business would never know it had been lost.

### Business impact

In vehicle retail, the follow-up window is short. A buyer who enquires and does not hear back within hours is already moving to the next dealership. The business was losing deals not because of price or stock, but because its operational tools were not built to run at the pace a sales floor demands. Management had no real-time view of what was happening across the team — reporting was done manually at the end of the week, by which point nothing could be corrected.

---

Strategy & Planning

### UX thinking

The system needed to be fast to use in a high-activity environment. Salespeople on a busy floor cannot navigate complex interfaces between customer interactions. The design priority was: the most important action on every screen must be reachable in one or two clicks. Lead updates, inventory checks, and task completions needed to be immediate operations, not multi-step processes.

Role-based access was planned from the start. Salespeople see their own leads, their assigned vehicles, and their tasks. Managers see everything across the team. The information each user sees is relevant to their role and does not create noise.

### Conversion strategy

The platform was designed to eliminate the two largest sources of lost deals: slow response to new enquiries and missed follow-ups. Both were solved structurally — new leads enter a defined queue with timestamp visibility, and follow-up reminders trigger automatically based on lead stage and elapsed time, not salesperson memory.

### Research

The workflow was mapped in detail before any design work began. How does a new enquiry come in? Who sees it? What information is needed immediately? What happens after first contact? What does management need to see, and when? The system architecture was built from those answers, not from a generic CRM template applied to a dealership context.

---

Design Showcase

### Inventory module

A clean, searchable vehicle list showing make, model, year, specification, condition, price, and availability status. Each vehicle has a full detail page with attached images, specification notes, pricing history, and a record of which buyers have expressed interest. Updated in one place, reflected everywhere instantly.

### Lead pipeline

Leads move through defined stages on a visual pipeline: New Enquiry → Contacted → Qualified → Test Drive → Negotiation → Closed / Lost. Each lead card shows the buyer's name, vehicle of interest, assigned salesperson, last activity date, and current stage. Moving a lead forward is a deliberate action that creates a timestamped record.

### Lead detail view

Each lead has a full profile: buyer contact details, vehicle interest, conversation notes, activity history, attached documents, test drive record, and follow-up task list. Every interaction is logged in one place, visible to any authorised team member.

### Test drive scheduler

Test drives are booked directly from the lead record, linked to a specific vehicle, assigned to a staff member, and shown in a team calendar view. Conflicts are visible before they happen. Post-drive follow-up tasks are created automatically.

### Management dashboard

A live overview of the entire operation: leads by stage, staff workload, overdue follow-ups, test drives this week, vehicles moved this month, and pipeline value. Current at all times — no end-of-week manual reporting required.

### Mobile experience

The platform is fully responsive. Salespeople on the floor can pull up a lead, check vehicle availability, log a note, or set a follow-up from their phone without returning to a desk.

---

Development Details

### Framework and architecture

Built on Next.js with a Supabase backend (PostgreSQL). Real-time updates across the platform mean that when inventory or lead status changes, every user sees the change immediately without refreshing.

### Role-based access control

Three access levels: Salesperson (own leads and tasks), Manager (full team view and reporting), Administrator (platform configuration and user management). Permissions are enforced at the database level, not just the UI.

### Performance optimisation

Server-side rendering for all data-heavy views. Optimistic UI updates for common actions (stage changes, note saves, task completions) so the interface feels immediate even on slower connections. Database queries are indexed on the fields most commonly filtered — vehicle availability, lead stage, assigned staff.

### Notifications and reminders

Follow-up reminders are triggered by a background job that evaluates lead stage and elapsed time. Overdue follow-ups surface in the salesperson's task list and in the manager's dashboard view. No manual reminder setting required.

### Responsive system

Mobile-first layout with a responsive sidebar navigation that collapses on small screens. All data tables reformat to card views on mobile without losing essential information.

---

Results / Impact

  • **Lead visibility** — every enquiry now has an owner, a stage, and a timestamp. Nothing enters the system without being tracked and nothing falls through without a trigger
  • **Follow-up discipline** — automatic reminders by stage and elapsed time replaced memory-dependent follow-up, removing the primary cause of lost deals
  • **Inventory access** — any staff member can answer a buyer's question about availability, specification, and price in real time without leaving the conversation
  • **Management visibility** — live pipeline and team performance data available at any time, replacing end-of-week manual reports with current operational information
  • **Test drive coordination** — scheduling conflicts eliminated, post-drive follow-up automated, test drive history attached to every relevant lead record

---

Start Your Project

DeckPro builds operational systems for businesses that have outgrown spreadsheets and messaging apps as management tools.

If your team is working harder than it should to keep track of the basics, a purpose-built system is the fix — not a better spreadsheet.

**[Get in touch →](/contact)**

Need a system shaped around your own workflow?

Start with the operational problem and DeckPro can help define the right build.