Start a project Start
Case studies Case template · Dealer Workspace
Dealer WorkspaceAutomotive · Digital product
Motorcycle page for a 2025 Rush Mamba, stock number MV2457: photos, price, site status and its own views, enquiries and phone taps for the last 30 days
One motorcycle

Services

  • Product design
  • UX/UI design
  • Frontend development

Tools

  • Competitor analysis
  • Market research
  • UX audit
  • Information architecture
  • User stories
  • User flows

Technology stack

  • React
  • TypeScript
  • Vite
  • React Router
  • React Aria Components
  • CSS variables
  • IndexedDB

Dealer Workspace

A workspace for motorcycle dealers to answer customers, arrange visits and move sales forward. Email, SMS and website conversations come together in one place, with clear customer responsibility and the motorcycle and next step close at hand.

Two sides of the dealership

The website helps buyers find a motorcycle and make an inquiry. The workspace is designed to carry that context into the dealership’s daily work. These demos run separately; their connection is not live.

Why this product

A buyer may email about a motorcycle, continue by text and then ask to visit. The dealer needs to keep that conversation together, know which manager looks after the customer and turn their interest into a clear next step. We set out to make replying, arranging a visit and following up part of one continuous workflow.

Our product decisions

We put the customer conversation at the center. Messages keep their channel visible, and staff can choose how to reply from the same place. We linked conversations to the customer record, where the assigned manager and motorcycles of interest stay clear.

We connected the conversation to the visit: staff offer showroom times, and the buyer chooses online. Deals and tasks carry the next action forward. Each motorcycle has its own stock record, and a separate publishing step gives the dealer control over what buyers see on the website.

Our contribution

We shaped the product direction, mapped the relationships and workflows, reviewed the first version section by section, and designed and built the responsive frontend. The work covers both the interface people see and the rules that make its sections work together.

Carlos Mendez’s conversation about a Dragster RR SCS, MV2485: an initial website inquiry followed by SMS messages, with Email, SMS and Site chat reply controls
Carlos’s website and SMS messages in one conversation

Answer the buyer from one place.

A customer can start on the website and continue by text. Staff need the earlier exchange in view when they reply, whichever channel the buyer uses.

We brought website inquiries, email and SMS into the same chat interface, with the channel shown on each message. In this sample, Carlos moves from the website to SMS; staff can reply beside the conversation history, with the relevant motorcycle above it.

Customer list with an Assigned to column: Ben Carter is assigned to Ethan Cole and Carlos Mendez to Mia Chen; an employee filter and each customer’s next step are visible
Customer responsibility and the next action, visible to the team

Keep each customer with their manager.

A shared dealership contact needs clear responsibility behind it. The team can assign a manager to a customer and see who is handling the relationship, alongside the next action.

We attached that responsibility to the customer record. When contact details identify an existing customer, a new inquiry links back to that record and keeps the assigned manager. Conversations and follow-up work stay connected to the same person.

Chat with Ben Carter about a Brutale 800: he asks to come on Thursday after work, and a panel suggests three times with Send these times and Adjust buttons
Suggested times beside Ben’s request
Buyer preview of an email to Ben Carter about a Brutale 800, with a button for each of three visit times
Buyer preview: choose a time to create the appointment
Buyer preview confirms Ben’s 30-minute viewing of the 2026 Brutale 800 on Thursday, November 5 at 5:00 PM America/Los Angeles, with an Add to calendar action
Ben confirms his visit online; the booked time also appears in the dealer’s chat

Turn a message into a booked visit.

A request such as “Thursday after work” should lead to a visit the buyer can confirm online. We put suggested showroom times inside the conversation, so staff can arrange the visit while the request is in front of them.

The buyer chooses a time, and that choice becomes an appointment linked to the conversation. In this demo, the email preview lets you try the buyer’s part of the flow.

Deals board with open deals in four columns, New, Qualified, Proposal and Negotiation: each card has a client and a motorcycle, and shows its value, next step and owner or says they are missing
The board shows the next step—or that one is missing
Task details for Confirm Daniel's Rush test ride: assigned to Sophia Reed, due November 5 at 11:00 AM, linked to the client, the deal and the conversation, with Daniel's source message
One task links the buyer, deal and original message

Keep the sale moving after the reply.

After a reply or a booked visit, the team still needs to know what happens next. Each deal keeps the buyer, the exact motorcycle and the next action together.

We made the next step a task shared by the deal and the task list, with an owner and a due date. The buyer’s original message can stay attached, so the person following up can see what was agreed. The board highlights overdue steps and deals that still need one.

Inventory list of 34 motorcycles: each row has a photo, model year, stock number, price, availability, site status, views, enquiries and days listed
Each motorcycle has its own stock number and listing data
Analytics: bikes flagged for many views and no enquiries or a long time on the site, above a table of listings with views, visitors, enquiries, enquiry rate, phone taps and days listed
Sample listing data highlights motorcycles worth reviewing

Know which motorcycles need a closer look.

Two motorcycles of the same model can have different prices, availability and time on the site. Combining them would hide the details a dealer needs to make a decision.

We made the individual stock unit the basis of inventory and reporting. Each bike keeps its own views and inquiries. The analytics view brings patterns such as many views with no inquiries to the dealer’s attention, ready for a closer look.

Editing a 2024 Rush Mamba, MV2464: the On the site panel lists a new price and Reserved as not on the site yet, with Save draft and Publish changes buttons
A price and status change awaiting publication. The website is not connected to this demo.

Review changes before buyers see them.

A new price or a Reserved status changes what the dealership is offering. Staff need a chance to check those edits together.

We separated Save draft from Publish changes. Pending changes stay visible field by field, and publication is a deliberate next action. News and CSV imports follow the same rule.

A working dealer workspace.

A working app across desktop, tablet and phone, connecting customer conversations, responsibility, visit booking and sales follow-up with inventory and website management. Explore the workflows with sample data; your changes stay in your browser. The demo is not connected to the dealer website, email or SMS services.

Other cases

EN