Book a call

Work / CARS24

CARS24CARS24

LEGO for internal tools: one system, 30+ tools

How CARS24 audited 20+ data-heavy tools, built tokens and Storybook with engineers new to design systems, and set up a contribution model, in about four months.

30+
internal tools on one system
20+
tools audited, screen by screen
93
component sets in Figma
1205
variants, every state drawn
Role
Design Systems Lead, CARS24
Users
Employees, dealers and partners
Platform
Web, desktop-first
Timeline
2025, 3–4 months to beta
The CARS24 internal tools design system: a lead dashboard, a column filter, a brand token and buttons, on mint

01 the brief:

30+ tools. No shared language.

CARS24 runs on internal tools: for loans, inspections, dealers, sales and operations. Each one had been built its own way.

30+
internal tools, across every vertical
100+
designers and engineers building them
None
shared tokens, components or docs
3–4
months to a beta for leadership

Every tool team drew its own tables, filters and navigation

One library that every tool builds from

Engineers rebuilt the same data table in every tool

Build the table once, reuse it everywhere

Engineers who had never worked with a design system

Tokens and Storybook, taught from day one

Tools used by employees, dealers and partners looked unrelated

One look and feel, inside and outside the company

Internal tools are where much of CARS24 actually runs. Dealers manage their cars in them, loan teams work through lead queues, inspectors log reports and operations track every deal. Some are used only by employees; others are used by dealers and partners outside the company.

Each tool had been built by a different team, at a different time, with no shared language between design and engineering. The same table, filter bar and side navigation existed in dozens of versions. Every new tool started from a blank file.

The ask from leadership was simple: make every internal tool look and feel good, and make sure the next ones cost less to build. Better quality, fewer engineering hours, and tools that feel like one company.

How might we give 100+ people who had never used a design system one they would rely on?

02 the audit:

20+ tools, opened one by one

Before drawing anything, every screen of 20+ live tools was taken apart and sorted into components and patterns.

  1. 01

    Get access

    Logins to 20+ tools across verticals

  2. 02

    Map the screens

    Every page, dialog and state, tool by tool

  3. 03

    Cut it apart

    Each element on each screen, grouped by what it does

  4. 04

    Find the patterns

    Tables, filters, navigation and forms that repeat

  5. 05

    Rank

    By how many tools use it and how painful it was

  6. 06

    Shortlist

    What to build first, agreed with engineering

In nearly every tool8
  • Data table
  • Filters
  • Search
  • Side navigation
  • Top bar
  • Pagination
  • Status badge
  • Button
In most tools8
  • Text input
  • Dropdown
  • Date picker
  • Modal
  • Toast
  • Tabs
  • Checkbox
  • Breadcrumbs
In some tools8
  • File upload
  • Stepper
  • Slider
  • Carousel
  • Avatar
  • Time picker
  • Accordion
  • Segment control

Grouping summarised from the audit. These are dense, enterprise-style tools: the hard parts were never buttons, they were tables with tens of thousands of rows.

03 foundations first:

Tokens before a single component

The token file came first: colour, type, spacing, radius, border width, opacity, icon sizes and breakpoints.

50100200300400500600700800900950
slate
gray
zinc
neutral
stone
red
orange
amber
yellow
lime
green

11 primitive ramps of 11 steps. They follow the Tailwind scale, which most of the engineers already knew, so the first conversation was about meaning, not hex values. Hover a swatch.

Semantic surfaces: pick a role and a state

Role

State

Continue
  1. Semanticcolor-surface-brand-default
  2. Primitivedenim-600
  3. Value#5546FF

Six of the nine surface roles, each with six states. Engineers pick a role and a state; the primitive underneath can change without touching a screen.

Spacing · 16 steps

space-3xs2
space-2xs4
space-xs6
space-sm8
space-md12
space-lg14
space-xl16
space-2xl20
space-3xl24
space-4xl28
space-5xl32
space-6xl40
space-7xl44
space-8xl48
space-9xl56
space-10xl64

Radius

radius-2xs2
radius-xs4
radius-sm8
radius-md12
radius-lg16
radius-2xl24
radius-full9999

Breakpoints · 8

bp-xs320
bp-sm480
bp-md768
bp-lg1024
bp-xl1280
bp-2xl1440
bp-3xl1600
bp-4xl1920

Type · font-size tokens, 4 weights

--font-size-90068/68

Leads

--font-size-80060/66

Leads

--font-size-70048/53

Leads

--font-size-60040/52

Leads

--font-size-50032/45

Leads

--font-size-40024/34

Leads

--font-size-35020/28

Leads

Each size has a matching line-height and letter-spacing token. Weights 400, 500, 600 and 700.

04 into code:

Same names in Figma and in Storybook

Engineers were new to tokens and Storybook, so both were set up together with them, one component at a time. Try the controls.

storybook · LEGO internalCanvasDocs

      
variant
size
state
label

A recreation of the Storybook setup, rebuilt in code with the button's real values from Figma: four variants, two sizes, five states.

Tokens

One source, two outputs

Design tokens exported for Figma and for code, so a change to denim-600 reaches both.

Storybook

A story per component

Every variant and state, with controls that use the same prop names as Figma.

Handoff

No redlines

Engineers read token and prop names off the component instead of measuring screens.

05 the library:

93 component sets, 1,205 variants

Every sheet carries its states, sizes and usage, and a version number.

Surface tokens: nine roles, six states each
Surface tokens: nine roles, six states each
Button v2.0: four variants, five states, two sizes
Button v2.0: four variants, five states, two sizes
Primitive colour tokens
Primitive colour tokens
The system's own cover artwork
The system's own cover artwork
93component sets in Figma, built from private base parts
Actions4
  • Button
  • Icon button
  • Button group
  • Link
Inputs11
  • Text input
  • Text area
  • Verification code
  • Dropdown
  • Multi select
  • Search
  • File upload
  • Slider
  • Date picker
  • Range calendar
  • Time picker
Selection9
  • Checkbox
  • Radio
  • Switch
  • Checkbox card
  • Radio card
  • Switch card
  • Choice chips
  • Chip
  • Segment control
Feedback7
  • Alert banner
  • Toast and notification
  • Tooltip
  • Loader
  • Progress bar
  • Status modal
  • Modal dialogue
Navigation10
  • Sidebar navigation
  • Header
  • Tabs
  • Tab group
  • Breadcrumbs
  • Pagination
  • Stepper
  • Timeline stepper
  • Menu
  • Drawer
Data display11
  • Table header
  • Table cell
  • Table row
  • Badge
  • Avatar
  • Card
  • Carousel
  • Accordion
  • Divider
  • Kbd
  • Grid count

06 the hardest part:

The table carried the whole system

In a data-heavy tool, the table is the product. It got the most time: cells, headers, filters, density and pagination.

Loan leads
Application IDPhone numberCompanyLead sourceCityStatus
123456742+91 98450 31254Guaranteed₹120,000CC IntentJaipurInterest
456767688+91 99018 77383Partner₹85,000RA LeadDelhiAll Docs
3456767801+91 98338 27728Guaranteed₹240,000SA InspectNoidaInterest
456788655+91 91057 37860Partner₹60,000CC IntentGurgaonAll Docs
4567889712+91 97290 82910Guaranteed₹150,000RA LeadJaipurApproved
2345678774+91 96062 89487Guaranteed₹120,700RA LeadDelhiInterest
6789054630+91 98724 30099Partner₹45,000SA InspectNoidaRejected
876543795+91 98026 34591Guaranteed₹320,000RA LeadGurgaonApproved
9876543701+91 98687 49716Guaranteed₹92,000SA InspectDelhiAll Docs
4356789668+91 92520 31349Partner₹120,000RA LeadJaipurInterest
10 of 10 leads123…10

Rebuilt in code with the system's table columns. Sort the scores, filter by city, change the row height. Data is made up.

From the Figma file

A dense lead table from the system: search, sort, show column, per-column filters, bulk select and pagination 1234 567
  1. Search across every column
  2. Sort by any column
  3. Show and hide columns
  4. Filters that combine
  5. Bulk select, for actions on many rows
  6. A filter on one column, with its own search
  7. Pagination for tens of thousands of rows
A dashboard built from the system: sidebar navigation, summary cards, toolbar and the table
A dashboard built from the system: sidebar navigation, summary cards, toolbar and the table

07 written for engineers:

Docs that answer the next question

Every component page says what it is, when to use it, its specs, and what not to do.

ToastFeedback
Variants
error · warning · success · info · neutral
Styles
filled · lighter · stroke
Sizes
32px · 40px (default) · 132px with description
Spacing
16px gap · 10px sides · radius 8px / 12px
Behaviour
One or two at a time · dismiss after 5–7s

Don't use a toast for anything the user must acknowledge.

Alert bannerFeedback
Statuses
error · warning · success · info · neutral
Type
title 14 medium · body 14 regular · link 14
Padding
14px × 12px · 12px between alerts
Instead
toast for transient news · modal to interrupt

Don't stack several banners on one dashboard.

StepperNavigation
States
default · error · ongoing · success · disabled
Use when
a process has several steps the user must track
Labels
"Enter details", never "Step 1"
Mobile
switch to the vertical stepper

Don't lock navigation in a non-linear process.

All designs are tokenisedNo hard-coded colour, spacing or type. Ever.
Components are used as providedA custom version needs the maintainers' approval.
Names match FigmaSame component, prop and token names in design and code.
QA before releaseViewports, token use and accessibility, checked and written down.

Specs quoted from the component documentation in the Figma file. Help lived in one Slack channel, #design-system-help.

08 who builds what:

Teams build it. Two maintainers guard it.

The system team couldn't build everything. So the engineers who needed a component built it into the system.

Squad

8 engineers

Building internal tools across verticals. When a feature needed a component, they built it into the system.

Maintainers

2 engineers

Reviewed every contribution against the tokens, the props and the docs before it shipped.

Design

A system designer and a lead

One designer full time on the system; Aniket on direction, quality and the roadmap.

  1. 01

    Need

    A tool's roadmap needs a component

  2. 02

    Check

    Is it in the library already?

  3. 03

    Design

    Drawn on the tokens, every state

  4. 04

    Build

    The squad engineer builds it, with a story

  5. 05

    Review

    Maintainers check tokens, props, docs

  6. 06

    Release

    Published, announced in Slack

  1. Requested
  2. In design
  3. In build
  4. In review
  5. Released

09 the runway:

Three to four months to a beta

Leadership set the deadline. The order was fixed: understand, then foundations, then components, then process.

  1. Audit

    Access to 20+ tools, every screen taken apart, the shortlist agreed with engineering.

    20+ tools
  2. Foundations

    Primitive and semantic tokens, type, spacing, radius, breakpoints. Exported for Figma and code.

    100+ tokens
  3. Storybook

    Set up with the squad. How tokens work, how a story works, how props map to Figma.

    With 8 engineers
  4. Components

    Table, filters and navigation first, then forms and feedback. Each with docs and QA.

    93 sets
  5. Contribution model

    Two maintainers, a review checklist, a Slack channel and a request process.

    Running
  6. Beta to leadership

    The library, the docs and the first tools rebuilt on it, presented as a beta.

    Shipped

Approximate months.

10 what changed:

One system behind every new tool

Library
93 component sets

1,205 variants and 100+ tokens, in beta, with a roadmap for complex patterns.

Teams
Built with, not for

A squad of 8 engineers contributed; 2 maintainers kept the bar.

Reach
CARS24's global teams

Teams building internal tools across the company were asked to start from it.

Leadership
A clear yes

Well received by the engineering teams and by leadership at the beta review.

01

In data-heavy tools, start with the table. Everything else hangs off it.

02

Teach tokens before you ship components. Engineers who understand the chain stop hard-coding.

03

Let the teams who need a component build it, and give two people the right to say no.

11 for your team:

The same playbook, as a studio engagement

Each step of this case study maps to how we work with clients now.

Aniket Pandey led this as Design Systems Lead at CARS24 (2025), with a system designer, a squad of eight engineers and two engineering maintainers. This is employee work, not Layer One client work. Screens and component sheets belong to CARS24 and are shown for portfolio purposes. The Storybook panel, the table and the token tools are recreated in code from the Figma values; the table data is made up and the timeline is approximate.

Next case studies