Choose the measures that matter
Agree which product activities indicate value for your customers. Compare meaningful usage over time, not simply the number of logins.
Notice changes in product use, bring in the support context and find a helpful next step. Start with the customer’s experience, not an assumption about churn.
Try the exampleFernbank’s active seats have fallen from 68 to 52 across four weeks. A setup question is still open with support.
Check whether the setup issue explains the change. Offer a rollout session before assuming churn or pitching an upgrade.
Illustrative example. No live connections or actions.
Agree which product activities indicate value for your customers. Compare meaningful usage over time, not simply the number of logins.
Bring open support questions and account conversations into the picture. A dip could mean a setup problem, seasonality or something else entirely.
Surface a practical next step for the owner, such as a setup session or a check-in. Review the response and record what changed.
Configured around your product and available data. Agree the comparison period, thresholds and follow-up ownership before a workflow goes live.
An agreed product-usage source and a definition of meaningful activity.
Support tickets, onboarding history, account notes and email.
Connections, access and available actions are scoped during setup.
No. This example highlights an observable change and supporting context. Lower use alone does not establish that a customer will leave.
Yes. The measures and milestones should reflect how customers get value from your product. We scope these with your team.
A usage-based workflow needs a suitable source. Other account or support checks may still be useful, but they should not be presented as measured adoption.
We’ll work through the sources, rules and first useful workflow with you.
Arrange a demoOpens an email to luke@zarco.uk. No calendar slot is reserved.