Required Datapoints
- Target Feature(s) to Track
- Total Number of Accounts or Users
- Usage Frequency Over Time (e.g., daily/weekly/monthly)
Expansion Feature Usage Frequency measures how often a specific upsell-eligible feature is used by existing accounts. It helps assess product stickiness, value realization, and readiness for expansion.
Expansion Feature Usage Frequency is a key indicator of product stickiness and upsell readiness, reflecting how often users engage with premium features or value-adding modules post-purchase.
The relevance and interpretation of this metric shift depending on the model or product:
A rising trend signals habit formation and increased value extraction, while a drop can point to UX complexity or feature misalignment.
By segmenting by account type, industry, or lifecycle stage, you unlock insights for expansion forecasting, feature education, and upgrade sequencing.
Expansion Feature Usage Frequency informs:
These are the main factors that directly impact the metric. Understanding these lets you know what levers you can pull to improve the outcome
Actionable ideas to optimize this KPI, from fast, low-effort wins to strategic initiatives that drive measurable impact.
Activities commonly tied to improving or operationalizing this KPI.
| Activity | Description |
|---|---|
| Expansion Enablement | Expansion Enablement focuses on Customer Growth Activation encompasses systematic processes and strategies designed to empower teams to identify, nurture, and realize revenue expansion opportunities within existing customer accounts. It coordinates execution across touchpoints so teams can move users or accounts toward the target outcome. Relevant KPIs include Expansion Feature Usage Frequency. |
| Product Analytics | Product Analytics focuses on systematically gathering, measuring, and interpreting data on product usage, user behavior, and feature adoption to guide strategic decision-making. It turns signals into decisions, interventions, and measurable follow-up. Relevant KPIs include Expansion Feature Usage Frequency and Feature Adoption / Usage. |
| Post-Sale Strategy | Post-Sale Strategy is a structured approach focused on engaging, supporting, and growing customer accounts after the initial sale. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Expansion Feature Usage Frequency. |
| Usage Coaching | Usage Coaching involves providing proactive guidance and ongoing support to customers to ensure they fully understand, utilize, and extract maximum value from a product. It helps teams translate strategy into repeatable execution. Relevant KPIs include Expansion Feature Usage Frequency. |
This KPI is associated with the following stages in the AAARRR (Pirate Metrics) funnel:
This KPI is classified as a lagging Indicator. It reflects the results of past actions or behaviors and is used to validate performance or assess the impact of previous strategies.
This role is directly accountable for the KPI and is expected to drive progress and decisions around it.
These roles contribute directly to performance and typically partner on execution, reporting, or optimization.
These leading indicators influence this KPI and act as early signals that forecast future changes in this KPI.
These lagging indicators confirm, quantify, or amplify this KPI and help explain the broader business impact on this KPI after the fact.
How this KPI is structured in Cube.js, including its key measures, dimensions, and calculation logic for consistent reporting.
cube('FeatureUsage', { sql: `SELECT * FROM feature_usage`,
joins: { Accounts: { relationship: 'belongsTo', sql: `${CUBE}.account_id = ${Accounts}.id` } },
measures: { usageFrequency: { sql: `usage_count`, type: 'sum', title: 'Usage Frequency', description: 'Total usage count of the target feature by accounts.' }, totalAccounts: { sql: `account_id`, type: 'countDistinct', title: 'Total Number of Accounts', description: 'Total number of unique accounts using the feature.' } },
dimensions: { id: { sql: `id`, type: 'string', primaryKey: true }, featureName: { sql: `feature_name`, type: 'string', title: 'Feature Name', description: 'Name of the target feature being tracked.' }, usageDate: { sql: `usage_date`, type: 'time', title: 'Usage Date', description: 'Date when the feature was used.' } }})Note: This is a reference implementation and should be used as a starting point. You’ll need to adapt it to match your own data model and schema