Churn scores tell you who's leaving. Uplift modelling tells you who's worth saving. Here's how FinTech teams can combine both to retain the right customers.
Knowing a customer is about to leave is not the same as knowing what to do about it. Most FinTech retention programmes stop at the first problem — they build a churn propensity model, hand it to CRM, and watch response rates disappoint everyone in the quarterly review.
The sharper approach combines pre-churn scoring with uplift modelling: identify who is at risk, then layer in who will actually respond to a retention intervention. Towards Data Science contributor Aleksei Terentev laid out the mechanics of this two-stage framework in detail — and for data teams building retention stacks in Southeast Asia’s digital banking market, the implications are significant.
Why Your Churn Model Is Only Half the Answer
A standard churn propensity model ranks customers by their probability of leaving within a defined window — say, 30 or 60 days. It is useful. It is also incomplete. The model cannot distinguish between four meaningfully different customer types: those who will churn regardless of what you do, those who were never going to churn, those who will churn but won’t respond to outreach, and — the only group that actually matters for ROI — those who are at risk and can be saved by intervention.
Spending retention budget on the first three groups is not just inefficient; it actively skews your model’s apparent performance. A campaign with a 12% save rate sounds reasonable until you realise half those customers were never leaving anyway, and another third churned despite receiving the offer. The signal you think you’re optimising is largely noise.
Terentev’s framework addresses this by treating the retention decision as a causal inference problem, not a classification one. The goal shifts from predicting churn probability to estimating the incremental effect of a specific intervention on a specific individual.
Uplift Modelling: The Mechanics That Matter
Uplift modelling — sometimes called incrementality modelling or treatment effect estimation — estimates the difference in outcome between a treated and untreated customer with similar characteristics. In retention terms: what is the probability this customer stays if I contact them, minus the probability they stay if I don’t?
The practical implementation requires historical data that includes a holdout or control group — customers who were eligible for a retention intervention but did not receive one. Without that control group, you cannot estimate the counterfactual. This is the part most FinTech data teams skip because it feels uncomfortable to deliberately withhold an intervention. But without it, you are flying on churn scores alone.
Terentev outlines a two-model approach as one accessible entry point: train a separate model on the treatment group and the control group, then score each customer with both and calculate the difference. More sophisticated implementations use meta-learners (T-learner, S-learner, X-learner) that handle the problem more elegantly, particularly when treatment and control groups are imbalanced — common in real-world retention campaigns where holdouts are small.
For Southeast Asian digital banks and super-apps operating on platforms like GoPay, SeaMoney, or Maya, the feature set feeding these models should extend beyond transactional recency-frequency-value signals. Login cadence, feature adoption depth (has the customer ever used a fixed deposit product? set up recurring transfers?), and even app navigation path data are strong behavioural predictors of genuine engagement versus passive account holding.
Building the Data Infrastructure That Makes This Possible
The modelling framework is only as good as the unified customer profile sitting underneath it. Pre-churn scoring and uplift modelling both require clean, stitched-together behavioural, transactional, and declared data — which is exactly where most retention initiatives hit the wall before they start.
In practice, this means three things need to be true before a team can run this kind of analysis reliably. First, event-level behavioural data needs to be captured and retained with enough granularity to construct meaningful engagement trajectories — not just aggregate monthly active user flags. Second, identity resolution has to work across touchpoints: the customer who browses via mobile web, transacts via app, and contacts support via LINE needs to resolve to a single profile, not three. Third, the modelling pipeline needs to be operationalised, not just run as a quarterly analysis — churn risk changes weekly, and retention windows are short.
For teams not yet at this infrastructure maturity level, a simpler but still meaningful starting point is to segment your existing churn-risk cohort by historical campaign responsiveness. Customers who have engaged with previous outreach — opened an email, tapped a push notification, redeemed a loyalty offer — are a reasonable proxy for the “persuadable” segment until you have the control group data to run a proper uplift model. It is imprecise, but it is better than treating every at-risk customer identically.
From Model Output to Activation That Actually Moves
A retention model that lives in a notebook is a strategy document, not a retention programme. The gap between model and activation is where most of the value leaks out.
Connecting uplift scores to a CRM or campaign orchestration layer requires agreement on a few operational details that are easy to underestimate. Refresh cadence: how often are scores updated, and does the campaign tool consume them in real-time or batch? Suppression logic: are customers in active service escalations excluded from retention outreach? Offer personalisation: is the intervention differentiated by uplift segment, or does everyone get the same cashback offer regardless of their predicted sensitivity to it?
This last point matters more than teams typically acknowledge. Terentev’s framework implies that the type of intervention, not just the targeting of it, should vary by customer segment. A customer showing early disengagement signals may respond to a feature discovery nudge. A customer with a recent negative transaction experience may need a service recovery gesture first. Treating these as identical cases and sending both the same “we miss you” push notification is a model output wasted.
For teams using GPT-5.6 or similar LLM tooling in their content stack, this is also where generative personalisation at scale becomes genuinely useful — not for writing the retention strategy, but for varying message framing across uplift-defined micro-segments without manual copywriting overhead for each variant.
Key Takeaways
- Churn propensity scoring identifies who is at risk; uplift modelling identifies who is worth targeting — running only the former wastes significant retention budget on unpersuadable customers.
- Operationalising this framework requires event-level behavioural data, reliable cross-touchpoint identity resolution, and a live connection between model scores and campaign activation — not a one-time analytical exercise.
- In the absence of a proper holdout group, historical campaign responsiveness is a workable proxy for persuadability while you build toward a full incremental measurement capability.
The real question Southeast Asian FinTechs should be sitting with is not whether to adopt uplift modelling — the ROI case is clear enough — but whether their current data infrastructure can support the causal inference logic it requires. Because a sophisticated model trained on a poorly resolved customer profile is still a sophisticated way to make the wrong call. Where does your unified customer profile actually stand?
At grzzly, we work with digital banks and FinTech growth teams across Southeast Asia to architect the customer data foundations that make models like this operational — not just theoretically sound. If your retention programme is running on churn scores alone and you suspect there’s more signal waiting in your data, we’d enjoy that conversation. Let’s talk
Sources
Written by
Velvet GrizzlyArchitecting the unified customer profile — stitching together behavioural, transactional, and declared data into platforms that actually earn their licence fee.