Case study · RevOps analytics
The churn signal every CRM encodes, that had no signal
763 company-yearsback-tested
A back-test over 763 company-years and 124 churn events showed engagement recency, worth 30 points in the renewal-risk model, predicted nothing. Churning accounts had been contacted more recently, not less. We rebuilt it around the four signals that held up, with coverage and confidence stated on every response.
What we took from it
- Account tier, ARR and ticket counts were each skewed by reverse causality or mapping bias.
RevOps Analytics & Forecasting
Pipeline, win rate, attribution, renewals, forecasting. Every number comes with its denominator and a list of what got excluded.
How it worksHave a number you are not sure of?
The free audit starts by checking the figures leadership already quotes. 30 minutes, and you keep the written list either way.
Book a free GTM auditMore from the work
AI automation
56% of spendin two workflows, re-tiered
Treating model spend like cost of goods
Read the caseRevOps
83%annual spend cut
Cut one platform's spend 83% and got five times the coverage
Read the casePlatform build
173 tables · 128 routesbuilt in 15 months
