Work
Work
Anonymised case studies and references from independent CRM and player-retention consulting in iGaming.
The work that would make the sharpest case studies is under NDA, so what follows is written to prove judgment without disclosing anyone. These are not trophy metrics. A number lifted out of someone else’s operation tells you little about whether the person reporting it can read your situation, and most of the numbers worth quoting belong to the client, not to me. So each of these is a pattern I have seen more than once: the situation as it presented, the constraint that turned out to be binding, what I did about it, and the kind of result that followed. The proof, if it is anywhere, is in the diagnosis.
The operation was the ceiling
An operator convinced its next gain needed new technology, when most of it was waiting in how the operation was run.
An established online casino operator, running on an informal structure that had never been built out into a professional one. Performance had settled below where it should have been, and the reading in the room was that the next gain would come from technology: a heavier platform, more automation, more spend.
It was mostly the operation. Functions had no clear ownership, process was improvised, and acquisition was being bought at a price no one was interrogating. The tooling was a genuine constraint too, and I want to be precise about that rather than reach for the comfortable line that it never is: the platform was custom-built and could not run basic lifecycle actions, giving away free spins or sending an email among them. But the platform was the second problem, not the first, and the order mattered.
So I built the structure that was missing. I organised and staffed the functions, put ownership and process where there had been improvisation, and set a strategy the operation could actually run. Two results came before any change of platform. Acquisition spend fell to a third of its previous level with no loss of output, and performance rose by a clear double-digit margin. Part of the work was simply holding the operation together: when acquisition activity was cut off abruptly from above, I rebuilt the affiliate and partner relationships the business depended on. Only once the operation was sound did I replace the stack, not to fix the current problem, which was already fixed, but to lift the ceiling on the next phase.
The lesson is the one the industry is most reluctant to hear. A new platform would have been sold internally as the cause of the turnaround, and it would have been the wrong story. The operation was the ceiling. The platform only mattered once that ceiling had been raised.
The constraint above the operation
An operation built well from nothing, decided in the end by the one seat no operator sits in.
A new casino brand in a fast-emerging, newly-regulating market. Greenfield in the fullest sense: no brand, no platform, no team, no CRM, no players.
I built it end to end. Platform and CRM selection, integration, and the automated lifecycle flows on top; brand and positioning from a blank page; and the acquisition engine that drove fast early traction across several channels at once. I hired and led the team across acquisition, service and compliance. The build worked, and it worked quickly.
The constraint that decided the outcome was not the build, and it was not, in the end, the market, though the market is the easy story to tell. The regulatory landscape shifted, a route through it existed and was worth taking, and I found one. The binding constraint sat higher up, at ownership level. The strategic call was not mine to make, and it went the other way.
So this one closes honestly. An operation can be built well, read its market correctly, and still be decided by the judgment of the person who owns it. That is the most senior constraint there is, and the one an operator cannot fix from below.
Differentiation without the spend
A portfolio of near-identical brands, differentiated by design rather than by budget.
Brought in at senior level to an established multi-brand operation. On paper it ran several brands; in practice it ran one, several times over: the same offers, the same flows, the same mechanics reused across all of them, separated by cosmetic skins and slightly different numbers.
The instinct to reuse was not irrational. Resources were finite, and building each brand out properly looked like the kind of technical and human investment no one wanted to sign off. What follows from thin resource is a reactive reflex: a number dips one day, and a campaign is scrambled for the next to chase it back. It keeps everyone busy, and it quietly makes the brands more alike, not less. The binding constraint was not budget in the abstract; it was the assumption that real differentiation had to be bought with more of it.
So I designed a way to give each brand a genuine identity and its own marketing strategy without a step-change in spend or headcount. The differentiation came from structure: clean campaign taxonomies, a repeatable build framework so each brand could run its own campaigns without reinventing them by hand, and automation that let each lifecycle run on its own terms. The aim throughout was to replace the reactive scramble with something planned, so the brands could diverge by design instead of drifting together by default.
This engagement was redirected before it ran its full course, for a legal constraint on the client’s side, unrelated to my performance and to the work itself. I include it anyway, because the diagnosis is the part worth showing: the cheap instinct was reasonable, and the fix was design, not budget. Telling those two apart is most of the job.