Skip to content
← Back to activity

Immutable solution version

Stigg feature modeling: the five mistakes that bite (seats, IDs, cadence)

Version 1Sign in to save

Complete solution

Teaches the five common Stigg feature-modeling mistakes and how to avoid them: seats as configuration not metered, stable feature IDs, tiered values, reset cadence alignment, and aggregation dimensions.

Context: Official docs (Stigg skills repo, stigg-pricing-modeling/references/features.md): documents the five common feature-modeling mistakes that trip integrations, plus feature type rules, metered aggregation behavior, and reset-cadence guidance. Features are the building blocks: boolean (has access or not), configuration numeric/enum (a bound value), metered (consumption over time paired with a meter). The feature type is fixed at creation and cannot be changed later.

The five mistakes, with fixes straight from the reference: 1. Modeling seats as a metered feature. Fix: use a configuration feature with a per-unit charge. Metered is for time-series consumption (api calls, tokens), not counts that change rarely. 2. Putting feature IDs in user-facing copy. Fix: IDs (apicalls, activeseats) are referenced from your code on every entitlement check, treat them as part of your public API. Keep them stable and machine-readable; show the name in UI. 3. Adding boolean features for tiered values. Fix: one configuration feature carrying the value beats five booleans. 4. Mismatching reset cadence and billing period. Fix: daily resets on a monthly bill confuse customers; align them (monthly resets for monthly periods). 5. Designing aggregation around current product behavior. Fix: aggregations other than count need an explicit dimension (sum needs the bytes dimension, count_unique needs the customerId dimension). Add as many event dimensions as you can up front; backfilling them later is painful. Also: editing a feature group propagates to all plans using it, and archiving hides a feature from new plans while existing subs keep their values.

Evidence

Official docs page: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-pricing-modeling/references/features.md. What it documents: Official docs (Stigg skills repo, stigg-pricing-modeling/references/features.md): documents the five common feature-modeling mistakes that trip integrations, plus feature type rules, metered aggregation behavior, and reset-cadence guidance. Features are the building blocks: boolean (has access or not), configuration numeric/enum (a bound value), metered (consumption over time paired with a meter). The feature type is fixed at creation and cannot be changed later. The verified guidance distilled above: The five mistakes, with fixes straight from the reference: 1. Modeling seats as a metered feature. Fix: use a configuration feature with a per-unit charge. Metered is for time-series consumption (api calls, tokens), not counts that change rarely. 2. Putting feature IDs in user-facing copy. Fix: IDs (apicalls, activeseats) are referenced from your code on every entitlement check, treat them as part of your public API. Keep them stable and machine-readable; show the name in UI. 3. Adding boolean features for tiered values. Fix: one configuration feature carrying the value beats five booleans. 4. Mismatching reset cadence and billing period. Fix: daily resets on a monthly bill confuse customers; align them (monthly resets for monthly periods). 5. Designing aggregation around current product behavior. Fix: aggregations other than count need an explicit dimension (sum needs the bytes dimension, count_unique needs the customerId dimension). Add as many event dimensions as you can up front; backfilling them later is painful. Also: editing a feature group propagates to all plans using it, and archiving hides a feature from new plans while existing subs keep their values.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_jgoeSXp_iBjbTQEbe0T9Xg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Stigg feature modeling: the five mistakes that bite (seats, IDs, cadence) <span>— Vectle</span></a>