The Beta-Geometric model is a probabilistic framework for modeling customer retention in discrete-time contractual settings. It assumes that in each period, a customer has a constant probability θ of churning, which follows a Geometric distribution. To account for heterogeneity across a customer base, the individual churn propensity θ is modeled as a random variable drawn from a Beta distribution, creating a mixture that captures varying loyalty levels.
Glossary
Beta-Geometric Model

What is Beta-Geometric Model?
A probability model for customer retention where the probability of churning in a given period follows a Geometric distribution, and heterogeneity in churn propensity is captured by a Beta distribution.
This model is a foundational component of Buy-Till-You-Die (BTYD) frameworks, often paired with the BG/NBD model for non-contractual purchasing. By applying Bayesian shrinkage, the Beta-Geometric model generates stable retention estimates even for cohorts with sparse data, making it essential for calculating Customer Lifetime Value (CLV) and forecasting long-term churn probability scores in subscription-based businesses.
Key Features of the Beta-Geometric Model
The Beta-Geometric model provides a mathematically rigorous framework for modeling customer retention in contractual settings by combining a Geometric churn process with Beta-distributed heterogeneity.
Geometric Churn Process
At its core, the model assumes that in each discrete time period, a customer has a constant probability θ of churning, independent of tenure. This memoryless property means the probability of surviving to period t and then churning follows a Geometric distribution. The process models the 'die' component of buy-till-you-die frameworks, where churn is an absorbing state from which customers never return.
- Probability mass function: P(T = t) = θ(1-θ)^(t-1)
- Hazard rate remains constant at θ for each period
- Suitable for subscription businesses with regular renewal cycles
Beta Heterogeneity Distribution
Not all customers share the same churn propensity. The model captures this unobserved heterogeneity by assuming individual churn probabilities θ are drawn from a Beta distribution with shape parameters α and β. This flexible distribution, bounded between 0 and 1, can take U-shaped, J-shaped, or bell-shaped forms to represent diverse retention patterns across the customer base.
- Beta(α, β) density: f(θ) ∝ θ^(α-1)(1-θ)^(β-1)
- α > 1, β > 1: unimodal distribution around a central tendency
- α < 1, β < 1: bimodal, capturing both loyalists and defectors
Bayesian Updating of Individual Churn Risk
As renewal or cancellation data accumulates for a specific customer, the model applies Bayes' theorem to update the posterior distribution of that individual's churn probability. The Beta prior conjugacy with the Geometric likelihood yields a Beta posterior, enabling computationally efficient, closed-form updates without Markov Chain Monte Carlo sampling.
- Prior: θ ~ Beta(α, β)
- Likelihood: P(data | θ) based on observed renewals and cancellations
- Posterior: θ | data ~ Beta(α + cancellations, β + renewals)
- Shrinkage effect: sparse data pulls estimates toward the population mean
Survivor and Retention Rate Functions
The model yields analytically tractable expressions for key business metrics. The survivor function S(t) gives the probability a randomly selected customer is still active after t periods, while the retention rate r(t) = S(t)/S(t-1) shows period-over-period stickiness. Unlike raw cohort tables, these functions produce smooth, monotonic decay curves.
- S(t) = B(α, β + t) / B(α, β) where B is the Beta function
- Retention rate increases over time as high-churn customers drop out
- Enables extrapolation beyond observed data for long-term CLV projections
Maximum Likelihood Parameter Estimation
The population-level parameters α and β are typically estimated via maximum likelihood estimation using historical cohort data. The likelihood function aggregates over all customers, accounting for both censored observations (still active) and uncensored observations (churned at a known period). Optimization is performed using numerical methods like the BFGS algorithm.
- Log-likelihood sums contributions from each customer's observed tenure
- Right-censoring handled naturally: active customers contribute S(t) to likelihood
- Standard errors derived from the inverse Hessian matrix at convergence
Contractual vs. Non-Contractual Distinction
The Beta-Geometric model is designed specifically for contractual settings where churn events are directly observable—such as subscription cancellations, membership lapses, or service contract non-renewals. This contrasts with non-contractual models like the BG/NBD, where inactivity must be inferred from a lack of transactions rather than an explicit termination signal.
- Observable churn: event time is known with certainty
- No need to infer a 'dropout' state from transaction gaps
- Pairs with Gamma-Gamma model for monetary value prediction in full CLV estimation
Frequently Asked Questions
Clear, technical answers to the most common questions about the Beta-Geometric model, its mechanics, and its application in customer lifetime value forecasting.
The Beta-Geometric (BG) model is a probabilistic model for customer retention where the probability of a customer churning in a given period follows a Geometric distribution, and the heterogeneity in churn propensity across the population is captured by a Beta distribution. It operates in discrete time, typically modeling contract renewal or periodic subscription contexts. The core mechanism assumes that each customer i has an underlying, constant churn probability θ_i per period. At the population level, these individual probabilities are distributed according to a Beta distribution with shape parameters α and β. The model uses Bayesian updating: as a customer survives more periods, the posterior distribution of their churn probability shifts, reflecting the inference that they are likely a 'low-churn' type. This allows the model to project a retention curve that flattens over time, accurately mirroring real-world survivor bias in cohorts.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
The Beta-Geometric model is a cornerstone of probabilistic customer retention analysis. These related terms form the ecosystem of models and metrics used to forecast lifetime value.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us