Most European gaming groups arrive at the same place eventually: several operating companies, acquired at different times, each with its own platform, trading operation, product roadmap and local leadership. Duplicated cost is obvious. The synergy case writes itself.
Then the programme runs for three years, costs twice the estimate, and delivers a portion of the benefit. This happens often enough that it is worth being precise about why.
The interim state is the real programme
Consolidation business cases model two states: today, and the consolidated target. The money is spent in neither.
It is spent in the interim — eighteen months to three years during which two platforms run in parallel, two trading operations are staffed, integration layers are built that will be thrown away, and every product decision has to be made twice. Teams are asked to maintain a system they know is being retired while learning one that is not finished.
This period is not a transition cost line. It is the programme. Planning it properly — staffing it, funding it, and being explicit that delivery velocity will fall — is the single biggest predictor of whether the thing lands.
Centralise a short list
The instinct is to centralise everything that appears duplicated. The list that genuinely benefits is shorter than it looks.
Worth centralising:
- Pricing and risk. One trading operation, one set of models. This is where the margin is and where scale genuinely compounds.
- Platform and core product. One codebase, one roadmap, one release train.
- Data. One definition of a customer, one definition of margin. Nothing else works without this.
Usually worth leaving local:
- Payments. Local rails, local providers, local conversion behaviour. Centralising this reliably costs more in conversion than it saves in vendor fees.
- Regulatory and compliance. Licence conditions are local and the relationships take years to build.
- Customer service and local marketing. Language, culture, and market-specific promotional norms.
The expensive error is centralising the second list, because it is more visible on an org chart than pricing models are.
Product convergence is where local goodwill dies
Two operating companies with different products cannot both keep theirs. Somebody's product is being retired, and the people who built it are being asked to help retire it.
The default answer — pick the larger OpCo's product — is politically simple and frequently wrong. The larger book is not automatically the better product; it is often just the one in the bigger market.
The better process is a structured assessment, journey by journey, using data rather than seniority, with the outcome accepted as a genuine mix. A target product that takes the winning components from each side costs slightly more to build and buys a great deal of cooperation from the side that would otherwise have lost outright.
Trading consolidation is the hardest part and goes last
Merging trading operations is the largest source of synergy and the largest source of risk. Two teams with different models, limits, risk appetites and tooling do not combine cleanly.
Realistic sequencing:
- Standardise data and market definitions across both books.
- Align risk appetite and limits explicitly, at board level.
- Move the lower-risk book onto the target pricing stack first.
- Run both in parallel long enough to compare margin honestly.
- Migrate the primary book last, with a rollback position held longer than feels necessary.
Attempting this early, before data is unified, is the most common way a consolidation programme produces a visible margin dip in a public reporting period.
Retention risk sits one layer below the executive team
Retention packages are usually scoped around OpCo leadership. The capability is not there.
It is in the traders who tuned the models, the engineers who know why the risk engine has the exceptions it has, and the product managers who remember the reasoning behind every override. Those people read a consolidation announcement as a redundancy announcement with a delay, and the good ones have options.
Mapping capability dependency at that layer — and funding retention there specifically — costs a fraction of the programme and protects most of its value.
A more honest business case
Four adjustments make consolidation cases considerably more accurate:
- Model the interim period as its own phase with its own cost and reduced delivery velocity.
- Restrict centralisation to pricing, platform and data, and defend that boundary.
- Sequence trading last and price the margin risk explicitly.
- Fund retention below the executive layer.
None of these reduce the synergy available. They change whether it is actually realised.