iGaming: what we build for casino operators
The studio landing - retention scoring, media-buying agents, and the products behind them.
Read// retention stack
These are not competing products - they solve different halves of the problem. A retention CRM is a delivery and campaign system. A scoring layer is a prioritisation system. The mistake is buying the first expecting it to do the second.
Off-the-shelf platforms segment by rules an analyst writes. That is cohort targeting with a nice interface. It is genuinely useful, and it is a different thing from a model that reads one player's transaction history and returns a decision about that player.
| Dimension | Off-the-shelf retention CRM | Custom scoring into your CRM |
|---|---|---|
| Targeting granularity | Cohort - rules over a handful of attributes. | Per player - a model output per individual. |
| Campaign delivery | Built in. Email, SMS, push, in-app, journeys. | Not included. Feeds the CRM or worklist you already use. |
| Integration with a self-written platform | Often the hard part. Schema assumptions rarely match, and integration can run for months. | An adapter is written against your schema. Mapping exercise, not a migration. |
| Explainability of targeting | The rule is visible, but it is a rule, not a prediction. | Score plus the features that drove it, per player. |
| Learns from outcomes | Only if an analyst manually rewrites the rules. | Retrained on outcome history on a defined cadence. |
| Time to first value | Fast if your stack is mainstream. Slow if it is not. | Data audit plus build - weeks, largely independent of how unusual your platform is. |
| Compliance gating | Usually present but operating on the platform's copy of consent state. | Reads self-exclusion and limit flags from your platform at send time. |
| Ongoing cost | Per contact or per profile. Grows with your player base. | Build cost, then compute. Largely flat as the base grows. |
| What happens if you leave | Segments, journeys, and history live in the vendor. | You own the pipeline and the model. |
In most deployments the answer is both. Keep the CRM for delivery, add a scoring layer that decides who goes into which queue. Replacing a working delivery platform in order to add prioritisation is a large project with a small payoff, and we will say so on the first call rather than after signing.
Thirty minutes, no pitch. We will tell you which of the two your situation actually points to - including when the answer is the one we do not get paid for.
Book a 30-min call