Time to Value (Expansion Features)

Definition

Time to Value (Expansion Features) measures the average time it takes for users or accounts to adopt and gain value from premium or advanced features after their initial onboarding or activation. It helps assess expansion readiness and product maturity velocity.

Business Context

Time to Value (Expansion Features) is a key indicator of upsell readiness, feature adoption, and advanced engagement, reflecting how quickly users move from core features to monetizable, premium functionality.

The relevance and interpretation of this metric shift depending on the model or product:

• In SaaS, it highlights time to integrations, automation, or analytics
• In Freemium, it reflects usage of gated, trial-only, or upgrade-worthy features
• In Enterprise, it surfaces admin adoption or cross-department expansion

A shorter time signals strong product education and in-product discovery, while delays may point to poor visibility, unclear ROI, or lack of onboarding.

By segmenting by user type, feature path, or tier, you can spot which users are ready to expand and where guidance is needed.

Time to Value (Expansion Features) informs:

• Strategic decisions, like pricing tier design and roadmap investments
• Tactical actions, such as feature spotlighting and targeted upsell triggers
• Operational improvements, including in-product cues and CS enablement
• Cross-functional alignment, helping CS, product, PMM, and RevOps drive faster expansion cycles and NRR growth

Key Drivers

These are the main factors that directly impact the metric. Understanding these lets you know what levers you can pull to improve the outcome

• Upgrade Flow and Feature Onboarding: Expansion features need onboarding too — not just access.
• Customer Maturity and Use Case Match: Expansion value shows up faster in mature, high-usage accounts.
• Visibility and Education: Users can’t find what they don’t know exists.

Improvement Tactics & Quick Wins

Actionable ideas to optimize this KPI, from fast, low-effort wins to strategic initiatives that drive measurable impact.

• If expansion TTV is slow, launch expansion-focused walkthroughs and success templates.
• Add usage nudges (“You’ve mastered A — now try B”).
• Run campaigns for existing users showcasing ROI of underused features.
• Refine CS touchpoints with “next stage” success plans.
• Partner with product to sequence features based on typical maturity curves.

Related Activities

Activities commonly tied to improving or operationalizing this KPI.

Activity	Description
Expansion Strategy	Expansion Strategy is a strategic process focused on identifying, prioritizing, and executing opportunities to increase revenue and market share within existing customer accounts. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include QBR Engagement Rate and Time to Value (Expansion Features).
Onboarding Design	Onboarding Design are guided smoothly through the early stages of product adoption. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Engagement Depth (First 3 Sessions) and Onboarding Satisfaction Score (OSS).
Feature Monetization	Feature Monetization is the strategic process of identifying, packaging, pricing, and launching specific product features as standalone or upgradeable offerings to generate additional revenue. It helps teams translate strategy into repeatable execution. Relevant KPIs include Time to Value (Expansion Features).
QBR Planning	QBR Planning involves methodical preparation for high-impact, periodic reviews between internal stakeholders and customer organizations. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Time to Value (Expansion Features).
Engagement Triggers	Engagement Triggers focuses on Identifying, tracking, and responding to specific customer behaviors or milestones—now termed Customer Activation Signals—plays a crucial role in modern go-to-market strategies. It coordinates execution across touchpoints so teams can move users or accounts toward the target outcome. Relevant KPIs include Time to Value (Expansion Features).

Required Datapoints

• Activation Timestamp (or onboarding completion)
• Timestamp of First Expansion Feature Use or Milestone Value Moment
• Definition of “Expansion Feature” and related value signal

Example

80 accounts activated in Q2

45 of them used expansion features

Avg. time between activation and first expansion use = 10.3 days

Formula

$$\mathrm{Time\ to\ Value\ (Expansion\ Features)} = \mathrm{Avg.}\left( \mathrm{First\ Expansion\ Feature\ Use\ Timestamp} - \mathrm{Activation\ Timestamp} \right)$$

Positive & Negative Influences

Negative Influences

• Complexity of Upgrade Flow: A complex upgrade flow can delay the adoption of expansion features, increasing the Time to Value.
• Lack of Feature Onboarding: Without proper onboarding for expansion features, users take longer to realize their value, extending the Time to Value.
• Low Customer Maturity: Accounts with lower maturity levels may struggle to adopt advanced features quickly, leading to a longer Time to Value.
• Poor Use Case Alignment: If expansion features do not align well with the customer’s use case, it can delay their adoption and increase the Time to Value.
• Insufficient Visibility and Education: When users are unaware of expansion features due to poor visibility and education, it prolongs the Time to Value.

Positive Influences

• Streamlined Upgrade Flow: A simplified upgrade process facilitates quicker adoption of expansion features, reducing the Time to Value.
• Effective Feature Onboarding: Comprehensive onboarding for expansion features helps users understand and adopt them faster, decreasing the Time to Value.
• High Customer Maturity: Mature accounts with high usage are more likely to quickly adopt and benefit from expansion features, shortening the Time to Value.
• Strong Use Case Match: When expansion features align well with customer needs, they are adopted faster, reducing the Time to Value.
• Enhanced Visibility and Education: Increased awareness and understanding of expansion features through visibility and education accelerates their adoption, lowering the Time to Value.

Funnel Stage & Type

AAARRR Funnel Stage

This KPI is associated with the following stages in the AAARRR (Pirate Metrics) funnel:

• Activation
• Revenue
• Retention

Type

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.

Ownership

Primary Owner

This role is directly accountable for the KPI and is expected to drive progress and decisions around it.

• Customer Success

Secondary Owners

These roles contribute directly to performance and typically partner on execution, reporting, or optimization.

• Finance
• Revenue Operations
• Product Management (PM)

Supporting Leading & Lagging Metrics

Leading

These leading indicators influence this KPI and act as early signals that forecast future changes in this KPI.

• Activation Rate: A higher Activation Rate means more users are reaching meaningful initial engagement milestones, which shortens the average Time to Value (Expansion Features) as these users are primed to explore advanced features more quickly.
• Product Qualified Accounts: An increase in Product Qualified Accounts (PQAs) signals accounts that are highly engaged and ready for expansion, indicating a faster transition to adopting expansion features and thus reducing Time to Value.
• Short Time to Value: Accounts that experience a Short Time to Value in the initial product phase are more likely to progress rapidly towards using expansion features, directly decreasing the overall Time to Value (Expansion Features).
• Deal Velocity: Higher Deal Velocity suggests that sales-qualified opportunities move more quickly through the pipeline, setting the stage for earlier adoption and value realization from expansion features.
• Monthly Active Users: Growth in Monthly Active Users reflects strong product engagement, which increases the pool of accounts likely to adopt expansion features sooner, positively impacting Time to Value (Expansion Features).

Lagging

These lagging indicators confirm, quantify, or amplify this KPI and help explain the broader business impact on this KPI after the fact.

• Expansion Activation Rate: A higher Expansion Activation Rate means a larger proportion of existing accounts are adopting new features, confirming and amplifying improvements in Time to Value (Expansion Features) and supporting expansion success analyses.
• Expansion Readiness Index: This composite metric quantifies how ready accounts are for upsell or cross-sell, providing context and explanatory power for observed changes in Time to Value (Expansion Features) across segments.
• Expansion Feature Usage Frequency: Increased frequency of expansion feature usage confirms effective value delivery post-adoption and helps explain reductions in Time to Value (Expansion Features) on a cohort or feature basis.
• Activation-to-Expansion Rate: This measures the proportion of activated accounts that expand, providing a direct explanatory link to how quickly users progress from core value to expanded value, thus validating shifts in Time to Value (Expansion Features).
• Time to Expansion Signal: Decreases in the Time to Expansion Signal (how quickly readiness for upsell is detected) validate and quantify improvements in the speed of expansion feature adoption, directly relating to Time to Value (Expansion Features).

Data Model Definition

How this KPI is structured in Cube.js, including its key measures, dimensions, and calculation logic for consistent reporting.

cube('UserOnboarding', {
  sql: `SELECT * FROM user_onboarding`,
  measures: {
    count: {
      type: 'count',
      sql: 'id',
      title: 'User Onboarding Count',
      description: 'Counts the number of user onboarding records.'
    }
  },
  dimensions: {
    id: {
      sql: 'id',
      type: 'string',
      primaryKey: true,
      title: 'User Onboarding ID',
      description: 'Unique identifier for each user onboarding record.'
    },
    activationTimestamp: {
      sql: 'activation_timestamp',
      type: 'time',
      title: 'Activation Timestamp',
      description: 'Timestamp when the user completed onboarding.'
    }
  }
})

cube('FeatureUsage', {
  sql: `SELECT * FROM feature_usage`,
  measures: {
    count: {
      type: 'count',
      sql: 'id',
      title: 'Feature Usage Count',
      description: 'Counts the number of feature usage records.'
    }
  },
  dimensions: {
    id: {
      sql: 'id',
      type: 'string',
      primaryKey: true,
      title: 'Feature Usage ID',
      description: 'Unique identifier for each feature usage record.'
    },
    firstExpansionFeatureUse: {
      sql: 'first_expansion_feature_use',
      type: 'time',
      title: 'First Expansion Feature Use',
      description: 'Timestamp of the first use of an expansion feature.'
    },
    expansionFeatureDefinition: {
      sql: 'expansion_feature_definition',
      type: 'string',
      title: 'Expansion Feature Definition',
      description: 'Definition of the expansion feature used.'
    }
  }
})

cube('TimeToValue', {
  sql: `SELECT
    u.id AS user_id,
    TIMESTAMPDIFF(DAY, u.activation_timestamp, f.first_expansion_feature_use) AS time_to_value
  FROM
    user_onboarding u
  JOIN
    feature_usage f ON u.id = f.user_id`,
  measures: {
    averageTimeToValue: {
      type: 'avg',
      sql: 'time_to_value',
      title: 'Average Time to Value',
      description: 'Average number of days it takes for users to adopt expansion features after onboarding.'
    }
  },
  dimensions: {
    userId: {
      sql: 'user_id',
      type: 'string',
      title: 'User ID',
      description: 'Unique identifier for the user.'
    },
    timeToValue: {
      sql: 'time_to_value',
      type: 'number',
      title: 'Time to Value',
      description: 'Number of days from activation to first expansion feature use.'
    }
  }
})

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