growth-model-vs-actuals-tracking

Tracking actual revenue performance against a growth model baseline involves comparing CRM and CS-platform actuals to your Unit of Growth baseline across new logo ARR, expansion NRR, and retention GRR vectors to measure period-level attainment and detect drift.

Growth drift detection in unit economics reporting identifies when actual performance deviates from your UoG baseline beyond configured thresholds, such as new logo drift exceeding 15%, NRR dropping over 5pp, or GRR falling beyond 3pp.

Generating a variance memo for NRR and GRR threshold breaches requires running variance analysis on actuals against your UoG baseline, which automatically fires a memo with vector-level deltas when expansion or retention metrics cross their configured drift thresholds.

You can run RevOps variance analysis without a configured UoG baseline by switching to reporting mode, which surfaces actuals only from your CRM and CS-platform data while explicitly disclosing the limitation that no baseline comparison is available.

Growth drift should trigger mid-year replan routing when any vector crosses its configured drift threshold, routing threshold breaches to replan triggering while keeping CS-owned expansion and retention metrics aligned to CS leadership accountability.

Labeling data-as-of dates when pulling CRM actuals for growth tracking requires applying G-code guardrails to timestamp your source data, ensuring period-level attainment calculations reflect accurate point-in-time snapshots for variance analysis.