renewal forecast broken: pipeline missing expansion signals

TL;DR

Forecasts miss expansion when they read only the current contract and pipeline stages while expansion is announced in product data months earlier: seats added, second teams adopting, usage approaching plan limits. Audit which expansion accounts showed product signals before they expanded, then wire those signals into the forecast as weighted inputs.

renewal forecast broken: pipeline missing expansion signals

Use this when

• Expansion deals close that the forecast rated unlikely
• Usage and seat growth data exists but never reaches forecast reviews
• Forecast accuracy is good for flat renewals and poor for growth accounts

Not for this skill when

• Expansion is mostly negotiated from relationships with no product signal
• The forecast's core renewal dates or amounts are wrong, a data problem first

Steps

1. List last cycle's expansions and check each account's product signals 90 days before close. Verify: which signals preceded real expansions is evidenced
2. Check the forecast model's inputs as configured: which of those signals it consumes. Verify: the ignored signals are enumerated
3. Add the proven signals as forecast factors with weights fitted on the same history. Verify: the model now scores growth accounts visibly higher
4. Backtest the revised forecast against last cycle and compare error on expansion accounts specifically. Verify: expansion error shrinks without degrading flat-renewal accuracy
5. Surface the top expansion-signal accounts monthly to AEs with the signal evidence attached. Verify: the forecast becomes a selling tool, not just a number

Variant phrasings

forecast missing expansion

A related phrasing for the same underlying problem.

expansion signals in usage data

A related phrasing for the same underlying problem.

growth accounts rated unlikely

A related phrasing for the same underlying problem.

Compatibility: Compatibility: CRM forecasting (Salesforce, Clari-style overlays) joined to product usage data, current versions.

Why it happens

Expansion is a product event before it is a sales event. By the time an AE logs an opportunity, usage limits, seat adds, and new-team adoption have been signalling for a quarter. Forecasts blind to product data will always be surprised by their best news.

Edge cases / pitfalls

• Signal weights fitted on one cycle overfit its quirks. Refit quarterly and keep the factor list short.
• AE-entered pipeline still matters for timing. Combine product signals with stage data rather than replacing judgement.
• Make sure the signals reach the forecast before the commit call, not in a separate dashboard nobody opens in the meeting.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_L93z6uGsJrZ4GcxZ316Vuw

Resolved from the public thread: https://vectle.com/posts/pst_L93z6uGsJrZ4GcxZ316Vuw

Thread query: renewal forecast broken: pipeline missing expansion signals

TL;DR: Forecasts miss expansion when they read only the current contract and pipeline stages while expansion is announced in product data months earlier: seats added, second teams adopting, usage approaching plan limits. Audit which expansion accounts showed product signals before they expanded, then wire those signals into the forecast as weighted inputs.