Cars&Co
OWN PROJECT / 2026


SCOPE
ux/ui design
information architecture
design system
ai workflow
SCOPE
ux/ui design
information architecture
design system
ai workflow
INDUSTRIES
fleet management
HIGHLIGHT
135 screens designed in an AI workflow, now in development
PREVIEW
01
/ 05

ABOUT
Cars&Co is a fleet management system for company cars, a web app for desktop and mobile. It replaces a spreadsheet with up to 47 columns per car, where nothing showed what was overdue or who was handling it. Version one covers 12 cars and is planned to scale to around 200. It is my own project: I work in fleet operations, so the requirements came from the job, not from a brief. The whole thing was made in an AI workflow. I made the design decisions, Claude Code ran file audits and bulk changes in Figma through a custom plugin. The result is 135 screens and a token based design system. The project is now in development.
ABOUT
Cars&Co is a fleet management system for company cars, a web app for desktop and mobile. It replaces a spreadsheet with up to 47 columns per car, where nothing showed what was overdue or who was handling it. Version one covers 12 cars and is planned to scale to around 200. It is my own project: I work in fleet operations, so the requirements came from the job, not from a brief. The whole thing was made in an AI workflow. I made the design decisions, Claude Code ran file audits and bulk changes in Figma through a custom plugin. The result is 135 screens and a token based design system. The project is now in development.
CHALLENGES
The first version of the start screen tried to do everything: alerts, tasks and a Gantt chart of the whole fleet. I split it. Start answers one question, what needs a reaction today. The timeline got its own page, Forecast, where each car is a row and overlapping tasks stack in lanes. Color follows one rule across both: it appears only where it means something. Event types have their own colors, red means overdue and nothing else, lime is reserved for the primary action. Even the today line is neutral.
The wireframes looked finished before they were. An audit of the file showed that none of the six user flows ran end to end on consistent data, and no desktop screen was built on auto layout. I fixed that before any visual work: one car carries every flow, every action has a state after it, all 135 screens sit on auto layout and a 4 px grid. A second check before hi-fi caught color pairs below WCAG AA and statuses with no token assigned. There is no user testing yet. That is the next step, alongside development.
CHALLENGES
The first version of the start screen tried to do everything: alerts, tasks and a Gantt chart of the whole fleet. I split it. Start answers one question, what needs a reaction today. The timeline got its own page, Forecast, where each car is a row and overlapping tasks stack in lanes. Color follows one rule across both: it appears only where it means something. Event types have their own colors, red means overdue and nothing else, lime is reserved for the primary action. Even the today line is neutral.
The wireframes looked finished before they were. An audit of the file showed that none of the six user flows ran end to end on consistent data, and no desktop screen was built on auto layout. I fixed that before any visual work: one car carries every flow, every action has a state after it, all 135 screens sit on auto layout and a 4 px grid. A second check before hi-fi caught color pairs below WCAG AA and statuses with no token assigned. There is no user testing yet. That is the next step, alongside development.

view map, FigJam

wireframe to hi‑fi, vehicle card

file audits, before and after

forecast, week view

tasks, details panel

design system in use

mobile flow, editing a deadline

view map, FigJam

wireframe to hi‑fi, vehicle card

file audits, before and after

forecast, week view

tasks, details panel

design system in use

mobile flow, editing a deadline