A feature set is a named bundle of platform capabilities that you can grant as a unit. They sit between the granular permissions inside security groups and the marketing-friendly subscription packages.
Why They Exist
- Trying to enable 30 individual features on every customer who upgrades is error-prone.
- Subscription packages are the marketing language (“Pro plan”). Feature sets are the technical language. Mapping packages to feature sets gives a clean separation.
- When you launch a new feature, you decide which feature sets get it; existing customers automatically inherit based on their tier.
A Typical Hierarchy
- Starter set: Basic browse, simple forms, single user.
- Pro set: Adds 10 users, custom reports, API.
- Business set: Adds 50 users, audit log, advanced permissions, white-label.
- Enterprise set: Unlimited users, SSO, dedicated support, custom integrations.
Cumulative vs Discrete
- Cumulative: Pro includes everything in Starter plus its own additions. Most SaaS works this way.
- Discrete: Each tier is a distinct bundle, possibly missing features other tiers have. Useful when you sell to specialised audiences (e.g. “Educator plan” has features “Business plan” doesn't).
Worked Examples
- SaaS launch: Three feature sets (Free, Pro, Business) mapped to three subscription packages.
- Add-on architecture: Base sets plus optional add-on sets (e.g. “Analytics add-on”, “API add-on”) that can be enabled separately.
- Educational discount: An “Education” feature set that's a subset of Business — designed for schools at a different price point.