At Inspo we design and build software products — and the intelligence inside them — shipped end to end by one team.
Every studio has seen it: a beautiful design system in Figma, and a product that drifted away from it within two sprints. The system was a picture, not a contract. Pictures do not survive contact with engineering.
Tokens are the treaty
Colour, spacing, radius, type scale — if it is not a named token that exists identically in the design file and the codebase, it is an opinion. Opinions drift. Our systems ship as tokens first: a small set of values both sides import, neither side may improvise.
Components earn their place
A component enters the system when it appears a third time — not before.
Every component ships with its states: hover, focus, loading, empty, error.
If a screen needs explaining, the component is not finished.
The system serves the product
A design system is not a museum. When the product needs something the system lacks, the system grows — deliberately, with a name and a rule. The measure of success is boring: months later, new screens still look like the same product, and nobody had to argue about it.
Let’s keep in touch.
More notes from the studio on X and Instagram — product, design and AI, from the people shipping it.
