Tessellate
Documentation as the product
Brand and product design for a design-systems platform, on the argument that its documentation was the thing customers were actually buying.
- Client
- Tessellate
- Year
- 2025
- Sector
- Software
- Status
- Delivered
- Scope
- Identity system
- Product interface
- Documentation architecture
- Technical illustration standard
- Collaborators
- Engineering: PLACEHOLDER
Tessellate sells tooling that keeps design systems consistent across large engineering organisations. Its own product was inconsistent — three visual languages across marketing, application and documentation, which is a difficult position from which to sell consistency.
The documentation was the demo
Prospective customers were spending most of their evaluation inside the docs, not the marketing site. So the documentation was rebuilt first and everything else was derived from it: the same grid, the same type scale, the same illustration standard, the same code-sample treatment.
Technical illustration was standardised to a single stroke weight at a single isometric angle, with no fills and no colour beyond the single accent used to mark the element under discussion. Roughly two hundred existing diagrams were redrawn to that standard, which was tedious and was the most valuable thing we did.
Identity from the grid
The identity is built from the product’s own layout primitives — a four-unit module, a fixed rule weight, and one tonal step. There is no metaphor in it. The mark is the module repeated, and it is drawn in the same weight as the rules used throughout the interface, so brand and product are made of literally the same parts.
Result
Time-to-first-successful-integration, which is the number the company runs on, fell by a little under half. None of that came from the identity. It came from the documentation, which is the correct order of importance and which the identity now reflects.