Carry a plan feature's unit to the buying surfaces

Featurekamo-shared-library
Shipped
August 27, 2026 at 6:19 AM UTC
Author
Kamo
Commit
0ede43b

The catalog has stored a unit per feature all along - "GB/user", "users", "contacts" - and the plan-feature DTO dropped it, so every surface rendering a measured feature printed a bare number. The pricing page showed "Storage (15)" and a comparison column of 5 / 15 / 25 / 50, and a reader had to reach the Terms far below the fold to learn it meant gigabytes per user, pooled. Deriving it per-consumer from featureCode is what put a stale block size on the marketing site once already, so it travels with the value instead.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing