Illustrative scenario / synthetic data

When expansion revenue drifts, find the decision behind the number.

A worked example for Northstar Cloud, a fictional B2B SaaS company. The interface demonstrates reasoning and control—not a customer result.

What it means
What it meansactivation depth

A cluster of product, billing, CRM and support changes appeared before the next renewal window.

Inspect this section
Demonstrates
  • How one decision can stay inspectable
  • How uncertainty can remain visible
  • How a human-controlled action can be reviewed
Does not prove
  • A real customer result
  • Causality or model accuracy
  • A production integration
Quick answer

The essential answer stays immediate; every next section adds inspectable depth.

01Signal

Expansion forecast moved below plan.

A cluster of product, billing, CRM and support changes appeared before the next renewal window.

02Evidence

Multi-user adoption is the strongest shared movement.

The evidence supports an onboarding-friction hypothesis, but does not establish causality.

03Decision

Test adoption support before changing commercial terms.

The recommended next move is a reversible 14-day intervention with a named owner and review date.

Inspect the evidence

Sources, constraints, roles and review criteria—without marketing shortcuts.

04Metric definition

“Activation depth” needs an exact denominator.

In this synthetic scenario it means the share of active accounts completing the shared multi-user setup sequence before the renewal window.

05Named evidence

Four source categories contribute different kinds of evidence.

Product events show behavior, CRM shows commercial context, billing shows plan movement and support shows qualitative friction.

06Alternatives

Three reversible paths are compared before action.

Guided activation, enablement outreach and commercial intervention are considered; discounting is not the default.

07Approval

The proposed test needs a named decision and owner.

VP Revenue approves; Customer Success owns the 14-day intervention; Product and Data validate the measurement.

08Outcome review

Day 14 compares the observed signal with the original assumption.

The record closes as go, adapt or stop and preserves what changed, what did not and what remains unknown.

Continue the decision journey

Explore this use case