Comment by bbg2401

Pricing per seat makes little sense for a component library. It forces every party involved in building an application to acquire a license, not just a designer who might otherwise have been hired once to provide the assets. Seat-based pricing suits tools people daily drive (Figma, Slack), whereas asset libraries are better priced by what you ship with them.

A more natural unit for pricing would be per domain, application, environment, or similar.

That said, I'm aware several UI frameworks have moved toward seat-based licensing recently, so it must be working for them in some sense.