Pleo
pleo.io
Scanned September 7, 2026
This score measures Pleo's observable frontend consistency — patterns observable in publicly accessible frontend code and rendered pages, primarily pleo.io's shipped CSS. It is not a complete measure of Pleo's design-system maturity, internal tooling, design process, or team structure, which this benchmark has no visibility into. CSS-in-JS, Tailwind-style utility classes, hashed class names, JavaScript-rendered states, and authenticated product surfaces can all reduce how much is actually observable here. See the full methodology for what is and isn't measured.
Evidence & confidence
- Analysis date
- September 7, 2026
- Surface analyzed
- pleo.io homepage (1 of 1 linked stylesheets)
- Observable data coverage
- 2,215 CSS declarations analyzed
- Confidence level
- High confidence in the observable CSS sample
This confidence level describes the completeness of the observable CSS sample, not the maturity of the organisation's full design system.
A substantial, largely complete set of the site's shipped CSS was gathered and analyzed.
Category scores
Token adoption
38.8/40Color discipline
25/25Typography discipline
19.5/20Spacing discipline
14.7/15What we found
The highest-leverage issues, ranked by impact.
Solid foundation — focus on documentation
Your token adoption, color palette, and type scale all look healthy. Consider documenting your system in a shared library (Figma / Storybook) to keep it that way as the team grows.
Benchmark v1.1
Own or manage Pleo?
Being listed here isn't a submission, endorsement, or verified participation — Pleo has not necessarily reviewed or confirmed this result.