Churnor
A practical workflow for SaaS churn monitoring
Churn monitoring starts with the signals your product already records. Bring customer activity and billing changes together, review the evidence, and use it to prioritize a human follow-up.
1. Pick a stable customer identity
Choose an external customer ID and use it consistently in product events, customer imports, and billing data. Email addresses can change and are not used by Churnor to merge customer records.
2. Connect product activity and billing context
Send product activity through the authenticated Events API, upload an existing customer list with CSV, and connect supported subscription or payment events through a billing provider. Product activity and billing events are separate signals: a payment event does not show that someone used the product.
Plan and send customer events · Explore the available integrations
3. Review the observed changes
Churnor calculates a deterministic risk score from recorded activity recency, changes in activity frequency, subscription events, and use of core features. The score is a prioritization signal, not a probability that a customer will cancel. Its usefulness depends on the data available for each customer.
Review the evidence and recorded history with the score. History contains saved assessments and does not reconstruct scores for periods without records.
4. Make follow-up a team decision
Use the customer view to decide which account needs review and what to investigate. Churnor provides recommended actions based on the saved assessment; it does not automatically send customer outreach, Slack alerts, or CRM tasks.
Incoming events and imports recalculate assessments. Authorized dashboard reads refresh missing or older assessments; Churnor does not run a background inactivity scan while the application is unused.
Continue with product setup
Review Churnor features, open the developer documentation, or compare workspace plans.