Car-Fluent.
A B2B dashboard that replaced spreadsheets for automotive teams without retraining them.
(Overview)
- Industry
- Automotive SaaS
- Role
- Product Designer
- Timeline
- 2021 — 2022
- Team
- Solo designer · 5 engineers · Founder/PM
- Tools
- Figma, FigJam, Metabase, Jira
As product designer I owned the dashboard, reporting and core operational workflows. I restructured the information architecture around how shops actually run their day and worked directly with the founding team and engineers on every release.
(01) — The Problem
Customers were migrating from spreadsheets they had used for years, and the platform initially mirrored that chaos: dashboards displayed data without answering questions, key workflows took dozens of clicks, and reporting meant manually exporting and rebuilding tables. Owners, managers and service staff shared one interface despite needing completely different views of the business.
(02) — The Process
I shadowed real operations — vehicle intake, service tracking, end-of-month reporting — and mapped the decisions each role actually makes. The IA was rebuilt around daily operations rather than database entities. Dashboards were redesigned as answers: what needs attention today, what's overdue, what's profitable. Reports became reusable templates instead of one-off exports.
(03) — The Solution
The operations dashboard leads with exceptions — overdue services, idle vehicles, pending approvals — instead of raw totals. Core workflows were compressed into guided flows with sensible defaults per role. The report builder turns the month-end ritual into picking a template and a date range.
(Outcome)
Daily task time dropped roughly 30% across pilot accounts, and month-end reporting went from hours to minutes. Weekly active usage grew steadily after the IA rework, and pilot-to-paid conversion improved enough to anchor the company's next funding conversation.
