Dashboard & CRM design
The screens behind the login. Designed for the dense state first, because that is the one people actually work in.
- Typically from
- $8,000
- Timeline
- 5–10 weeks
- Next step
- Book a 30-minute call ↗
Why this matters
Demo dashboards are always beautiful. They contain eleven rows, three merchants and one chart with a pleasing upward curve. Then real data arrives — four hundred rows, names that are too long, a metric that goes negative — and the design that photographed so well stops being usable.
We design the crowded state first and let the empty state be the easy one. The question is never whether a screen looks good in a deck. It is whether the person who opens it every morning can answer their question in five seconds.
What you get
Information hierarchy
Working out which four numbers earn the top of the screen, and defending that decision against everything else that wants to be there.
Tables that hold up
Sorting, filtering, pagination, sensible column widths, tabular figures so digits line up. Long values handled deliberately rather than truncated at random.
Charts designed to be compared
Consistent axes, tick density and heights across a screen, so the eye can move between charts without recalibrating. Two charts at different scales side by side is a quiet way of lying.
Every state drawn
Empty, loading, error, permission-denied, one-item, four-hundred-item. The states nobody designs are the states users hit on their worst day.
A component library
Handed over as Figma components with variants, so your engineers build against a defined system and the tenth screen matches the first.
Accessible by default
Contrast that passes, colour never carrying meaning alone, focus states that exist. Enterprise buyers ask about this, and increasingly they audit it.
How it runs
- 01
We watch someone use the current tool, or the spreadsheet it is replacing. What people actually do rarely matches the brief.
- 02
Structure and hierarchy agreed on the two or three screens that matter most.
- 03
Full interface design with a component library and every state defined.
- 04
Handover with your engineers, and we stay reachable through the build.
Questions
Before you ask.
Do you build the dashboard as well as design it?
We design it and hand over a component library your engineers build against. For the front end of a marketing site we build too; for application code we work alongside your team rather than replacing them.
We have no design system. Is that a problem?
No — you get one as part of this. Tokens, components, states and rules, in Figma, yours to keep and extend.
Can you redesign an existing product without breaking what users know?
Yes, and that constraint is usually right. We work out which patterns your users depend on and keep them, and change the parts that are genuinely costing people time.