Your Competitors Know Who Will Buy Next. You Should Too.13
Your Competitors Know Who Will Buy Next. You Should Too.
By Dr. Elara Voss, PhD in Artificial Intelligence
π Every company has a customer base. Few have a predictive customer base. The difference is the gap between "we know who bought last time" and "we know who will buy next time" β and that gap is where modern competitive advantage lives.
The title of this article is a provocation. Your competitors probably do know who will buy next. Not because they have better taste, not because they have better brand, but because they have built a prediction pipeline that turns behavioral signals into a ranked list of likely buyers β and then they act on that list before the buyer has fully decided. You might be doing the same, or you might be doing something slightly different that costs you the sale. This article is about that pipeline: what it's made of, how to think about it mathematically, and how to build or improve one.
1. The Shift From Segments to Probabilities
For most of marketing history, the unit of analysis was the segment. You'd say: "Our customers are 35β55, suburban, household income over $150K." Segments are useful. They're also static, coarse, and symmetric β everyone in the segment gets the same treatment, and the segment boundaries are drawn by humans with a red pen.
The unit of analysis is now the probability. Instead of "is this person in segment S?", the question becomes: "what is P(buy in next 30 days | xβ, xβ, β¦, xβ)?" where xα΅’ are hundreds or thousands of behavioral, transactional, and contextual features. The customer is no longer a bucket. The customer is a vector of signals, and the job of the prediction system is to map that vector to a number between 0 and 1.
That number β call it the purchase likelihood score, $p_i$ for customer $i$ β becomes the currency of your go-to-market. You rank the list, you spend budget where $p_i$ is highest, you allocate sales effort to the top decile, you design onboarding for the top quartile. The list is alive: it updates as new signals arrive, and it's private: only your team sees the scores, not the customers.
π A rough breakdown of where the signal comes from:
Signal class | Example | Weight (typical) |
|---|---|---|
Transactional | Recency, frequency, AOV, category mix | 40β50% |
Behavioral | Page views, cart adds, time on PDP, search queries | 25β35% |
Engagement | Email opens, app sessions, support tickets | 10β15% |
Contextual | Seasonality, lifecycle stage, device, geo | 5β10% |
Social / referral | Referrals in/out, community activity | 2β5% |
The weights are illustrative, not universal. The point is that no single class dominates, and the mix is what makes the score robust.
2. The Math That Actually Matters
A lot of articles on "predictive analytics" stop at "we use machine learning." That's not an explanation. Here's a more honest one.
The core model is usually a ranker, not a classifier. You don't need to know the true probability of purchase. You need the order to be right, because the order is what you spend money on. Formally, you're optimizing:
$$\ text{maximize} \quad \sum_{i=1}^{N} w_i \cdot \mathbb{1}[\text{rank}(i) \leq k]$$
where you want the top-$k$ customers by score to be the top-$k$ by actual purchase. This is a pairwise or listwise ranking problem, and it's solved with gradient-boosted trees (XGBoost, LightGBM, CatBoost), neural rankers, or more recently, learning-to-rank objectives like LambdaMART.
Two properties matter more than the model family:
Calibration. If you tell sales "this customer has a 72% chance of buying," and 100 such customers are contacted, about 72 should buy. Uncalibrated scores misallocate effort. A simple fix: isotonic regression or Platt scaling on a holdout.
Stability over time. The score for a stable customer should not swing wildly week to week. High variance in the score means the model is overfitting to noise, and your team will lose trust in it. Track a score drift metric: the standard deviation of $p_i$ across weeks for the same customer, normalized.
A small formula that captures the useful part of the score:
$$p _i = \sigma!\left(\theta_0 + \sum_j \theta_j f_j(x_i) + \sum_k \phi_k g_k(t, x_i)\right)$$
where $\sigma$ is the sigmoid, $f_j$ are static features (demographics, transaction history), and $g_k$ are temporal features (trends, recency, seasonality). The second term is where the magic lives. It's the term that says "this customer is currently leaning toward a purchase" versus "this customer is historically a good buyer."
3. The Competitor's Playbook
Here's what a well-run competitor's pipeline actually looks like, stripped of the marketing-speak:
Step 1 β Signal ingestion. Every touchpoint emits a structured event. Website, app, email, CRM, support, billing. The goal is event density: 200+ events per active customer per month. Below that, the model is under-determined.
Step 2 β Feature engineering. Raw events become features. A page view is not a feature. "Views of the pricing page in the last 7 days, weighted by session depth" is a feature. A support ticket is not a feature. "Tickets mentioning 'onboarding' in the last 14 days, weighted by sentiment" is a feature.
Step 3 β Model training. A supervised ranker, trained on labeled windows. The label is "bought in the next 30 days" (or 7, or 90, depending on the product). The training window is typically 12β24 months of history, so the model sees multiple seasons.
Step 4 β Score and rank. Every night (or every hour, for fast-moving products), the model scores the full active base. The list is sorted. The top $k$ (say, top 5%) get the most expensive treatment: 1:1 outreach, custom offers, early access. The next tier gets nurture. The tail gets broadcast.
Step 5 β Feedback loop. Purchases and non-purchases flow back. The model re-trains. The scores update. The list reshuffles. A customer who was 40th last week might be 4th this week because they viewed the comparison page three times.
This is not a one-time project. It's a system, and systems require maintenance. The competitors who have it don't have a better model than you. They have a better loop than you.
4. Where AI Changes the Pipeline
AI changes the pipeline in three concrete ways, and they're worth separating because they're often conflated.
4.1 β Feature discovery. Pre-AI, feature engineering was a human craft. A data scientist would sit with a product manager and brainstorm "what might matter?" Post-AI, you can let a model propose features. Give it the raw event stream and the label, and it can suggest: "customers who viewed the FAQ page for more than 90 seconds and then opened the pricing page within 5 minutes have 3.2Γ the purchase rate." The human validates; the model explores. The search space of features is huge, and AI lets you explore it.
4.2 β Personalization at scale. Pre-AI, personalization meant "use the customer's name in the email." Post-AI, it means: "for this customer, the best next action is a 15-second video about X, sent at 7:15 AM on Tuesday, from the app, with a CTA that says Y." The prediction model outputs not just who will buy, but how to move them. The score $p_i$ is now paired with a treatment score $t_{ij}$ (the expected lift of action $j$ for customer $i$), and you optimize the joint:
$$\ text{maximize} \quad \sum_{i,j} p_i \cdot t_{ij} \cdot x_{ij}$$
subject to budget and frequency constraints. This is a causal problem, not a correlational one, and it's where the field is moving fast.
4.3 β Interpretability and trust. A sales rep won't act on a black-box score. "The model says 72%. Why?" The answer, in a well-built system, is a shapley decomposition: "60% of the score comes from recency of purchase, 25% from engagement in the last 7 days, 15% from category affinity." The rep can explain the score to the customer, and the customer can trust the recommendation. AI makes the score explainable, which makes the score actionable.
5. The Compounding Effect
Here's the quiet math that explains why the predictive pipeline wins over time. Suppose the top-$k$ customers by score have a baseline purchase rate $r_0$, and the score-based targeting lifts that rate by a factor $L > 1$ (because you're reaching the right people with the right message at the right time). Then the effective revenue per customer in the top tier is:
$$R _{\text{top}} = r_0 \cdot L \cdot \text{AOV}$$
versus $R_{\text{tail}} = r_0 \cdot \text{AOV}$ for the untargeted tail. The ratio is $L$, and $L$ compounds because every successful sale generates new signals, which improve the model, which improves $L$, which generates better sales. It's a virtuous loop, and it's the structural advantage over a competitor who's still using segments.
π A rough illustration.
Targeting approach | Top-tier lift $L$ | Effective revenue multiplier |
|---|---|---|
Broadcast (no targeting) | 1.0 | 1.0Γ |
Segment-based | 1.4 | 1.4Γ |
Score-based (basic) | 1.9 | 1.9Γ |
Score + personalization | 2.6 | 2.6Γ |
Score + causal + explainable | 3.1 | 3.1Γ |
The numbers are illustrative. The point is structural: targeting compounds, and the compounding factor is the lift $L$. You're not buying revenue. You're buying a multiplier on revenue, and that multiplier is what the pipeline produces.
6. Building Your Pipeline: A Practical Checklist
You don't need a data team of 20 to start. You need a loop, and the loop has six parts:
Event density. 200+ events per active customer per month. If you're below that, fix the instrumentation before you fix the model.
Label window. Pick a window (7, 30, or 90 days) that matches your product's purchase cycle. A SaaS product with a 90-day trial should use 90 days. A retail product with a 7-day decision cycle should use 7 days.
Feature set. Start with 30β50 features. Recency, frequency, AOV, category affinity, engagement recency, session depth, support tickets, lifecycle stage. More than 100 features without a feature store is overfitting.
Model. Start with gradient-boosted trees. They're fast, interpretable (feature importance), and robust to missing data. Move to neural rankers only if you have 100k+ customers and 100+ features.
Calibration. Isotonic regression on a 2-week holdout. Check that the top decile actually converts at the predicted rate.
Feedback. Weekly retrain. Track score drift, top-$k$ hit rate, and lift $L$. If $L$ drops below 1.5, you're spending on the wrong people.
Run this loop for 6 months. The list will start to feel familiar β not because the scores are stable, but because the patterns in the scores are stable. You'll start to read the list the way a trader reads a tape. That's the skill, and it's the part competitors can't copy.
7. The Quiet Advantage
The predictive pipeline isn't a secret weapon. It's a quiet one. It doesn't show up in the campaign, the deck, or the keynote. It shows up in the next call the sales rep makes β the one where the rep walks in knowing, from the score, which customer is 4 points above the median, what their last three sessions looked like, and what the model says the best next action is.
In a market where everyone has access to the same tools, the same data, and the same models, the differentiator is no longer what you can do. It's how well you know your customer, and how quickly you can act on that knowing.
Your competitors know who will buy next. You should too β not because you have a better model, but because you've built the loop that makes the model yours, and the list that makes the knowledge actionable.
π The list is not the asset. The loop that keeps the list alive is the asset.