Pricing strategy
Choose the edition that fits the work.
Licensed by usage scope. One purchase. Twelve months of updates and support. Continued use of every version released during that term.
What is being purchased
Not more pieces. A resolved product baseline.
The value is the reduction in interface drift across hierarchy, density, state behavior, navigation, and documentation.
Why one-time pricing fits
Closer to an edition than a SaaS seat.
Installed once. Kept after purchase. A defined update term fits how teams buy a durable interface standard.
Expansion path
Start with one edition. Expand with clear rights.
Independent covers one buyer. Team fits internal product groups. Studio covers client delivery.
Editions
Pricing, with the default choice made clear.
Team is the standard one-time purchase for internal product software. Independent is sized for one contributor. Studio covers broader client delivery.
Solo designer, engineer, or founder
Independent
A single-seat edition for independent product work. Clear scope for one contributor and one shipped product.
Set low enough for independent purchase, but high enough to reflect finished product work rather than commodity UI.
Move to Team when the work expands beyond one contributor or one product.
Internal product teams shipping 1 to 3 products
Team
The default commercial edition for internal teams. Built for product software that needs a more resolved baseline from the start.
Priced to sit well below the cost of internal interface drift, repeated refinement, and design-system rework.
Move to Studio for client delivery.
Agencies and studios delivering premium client work
Studio
Built for repeated client delivery. Licensing stays explicit when the system becomes part of paid project work.
Structured to protect margin on a single engagement while remaining less costly than rebuilding the same interface decisions project after project.
This is the upper fixed edition for broader client delivery.
Economic anchor
Price against replacement cost.
The relevant comparison is not a cheaper kit. It is the time a team would otherwise spend resolving the same interface decisions internally.
Independent
A modest reduction in design and frontend cleanup can justify a serious independent purchase.
Team
A short stretch of avoided interface churn makes the default edition easier to justify than continued internal iteration.
Studio
One cleaner client delivery cycle can cover the license and preserve margin for the next engagement.
Scope definitions
Clear boundaries make the purchase legible.
| Scope | Independent | Team | Studio |
|---|---|---|---|
| Products included | 1 | Up to 3 | Up to 8 |
| Active contributors | 1 | Up to 8 | Up to 15 |
| Client delivery rights | No | No | Yes |
| Update term | 12 months | 12 months | 12 months |
| Support term | 12 months | 12 months | 12 months |
| Perpetual use after term | Yes | Yes | Yes |
Definitions
Terms should read clearly before purchase.
Product
One production application, website, or software property with a distinct brand and end-user purpose.
Contributor
A person actively working with the system in design, code, or implementation during the active license term.
Updates
New releases, fixes, additions, and improvements published during the active update term.
Support
Direct help with installation, usage questions, and implementation guidance during the active term. It does not include custom feature development.
Renewal policy
Renew only for continued releases.
Perpetual use continues
You can keep using every version released during the active term. Renewal extends access to new releases and support. It does not gate continued use.
Renewal is optional
Renew only if continued releases and support remain useful. A renewal reactivates both for the next term.
Lapsed customers can return
A customer can renew later under the policy in effect at that time. The model stays clear even after the update term has lapsed.
Support follows the active term
Support follows the same term as updates. Help remains active during that window alongside the releases published within it.
Upgrade rules
Simple rules for growing scope.
FAQ
Pricing decisions, stated clearly.
Why is this one-time instead of monthly?
Because the value behaves like a licensed product edition, not a metered software seat. You buy a durable baseline, then renew only if continued releases and support remain useful.
Why does this cost more than cheaper kits?
Lower-priced kits usually optimize for breadth or volume. This edition is priced against resolved product-facing work: hierarchy, density, state behavior, navigation, documentation, and less internal churn.
Can I keep using it after 12 months?
Yes. You keep the versions released during your active term. What expires is access to new updates and support, not the right to keep shipping what you already licensed.
What counts as a product?
A product is one production application, website, or software property with a distinct brand and end-user purpose. Staging and development environments for that same product do not count separately.
Which tier fits an agency or client project?
Use Studio when the system is part of client delivery. Team is for internal product teams only.