Why it matters
Activation was a sum of signals. We just never added them up.
Here's what activation actually looked like at PipelineCRM, even though we never formalized it. There were six signals I watched for in a new account: did they import their data — or did we have to do it for them? Did they add other users to the account? Did they create any new deals? Did they create tasks and events? Did they sync their email? And did they log in five days in a row? Any one of those was a flicker of life. The sum of them was the real activation number — the one we should have been calculating and weren't. A customer who hit most of them was activated and was going to stick. A customer who hit few of them, or none, was trending toward churn, full stop.
That's the definitional lesson, and it's the one most teams get wrong: activation is rarely a single magic click. It's a constellation. Defining it as a sum of value signals — not "logged in once," not "clicked the button" — is what makes the number honest. The single-event definitions are easy to hit and tell you nothing. The sum is harder to build but it actually predicts who stays.
And not tracking it formally cost us real money in churn. Because we weren't computing activation as a number, we couldn't see a new customer stalling in time to do anything about it — we'd notice once they'd already gone dark, which is a month too late. The fix I'd insist on now: intervene earlier in the trial and onboarding, and do it with real humans, not product widgets or automated emails. A person reaching out in week one to a customer who hasn't imported their data saves accounts that a tooltip never will. The metric exists to tell you which customers need that human, and when — which is now, not next month.