The Strategy Got Bigger. The Operating Model Didn’t

I have two conversations very often, and they never happen in the same room.

 

The first is with a CEO or a board. It’s about growth. New markets, new verticals, a product launch, a big sporting calendar to capitalise on. It’s a good conversation. The ambition is usually justified and the strategy is usually sound.

 

The second is with the people who have to deliver it. Heads of operations, payments, CRM, support. That conversation is about a launch that’s slipped, a workaround that’s become a process, a metric that means three different things on three different dashboards, and a Thursday night where deposits dropped and nobody was sure who was meant to make the call.

 

Same company. Same quarter. The gap between the two conversations is, in my experience, where most operational money goes.

 

Growth has outrun the way we run things

 

This isn’t a criticism of ambition. The industry’s growth has been real and, on paper, well managed. EGBA members alone held 401 online licences across 22 European jurisdictions in 2025, up from 321 the year before, with stakes up 28% and active accounts up 13% in a single year. Part of that is new members joining, but the direction is unmistakable: more markets, more licences, more volume. 

 

Now ask what grew alongside it inside the operator. Headcount, usually. Suppliers, definitely. Dashboards, absolutely. What almost never grew at the same rate is the operating model: the agreed way the business decides things, escalates things, and knows whether something worked.

 

Every regulated market has its own payment mix, its own responsible-gambling rules, its own reporting, its own supplier relationships and its own version of normal. Each one is manageable on its own. New markets get added; two, three, four…

Then a fifth one gets added on top, and the business is still running on the habits it formed and systems it used when there were two.

 

What it looks like from the inside

 

You can spot it without a consultant. Some of the tells I see in almost every operator past a certain size:

 

• The same KPI is calculated differently by two teams, and both are right according to their own dashboard
• A local team has built a spreadsheet that now quietly runs part of the business
• A promotion needs four approvals, and nobody can say which one actually carries the decision
• An incident report describes the problem thoroughly and recommends nothing
• The launch plan for the next market is the last market’s plan with the country name changed

 

None of these is dramatic, and that’s the problem. They don’t trigger a review because each one, individually, is just how things are. They only add up on the nights when something goes wrong, or in the months when a launch quietly slides from Q2 to Q4.

 

Why it doesn’t get fixed

 

Partly because operations work is invisible when it goes well. Nobody gets promoted for the incident that didn’t happen or the launch that came in on time. The reward structure of most operators points at growth, and growth is what gets attention.

 

Partly because the fix looks boring. Agreeing what a metric means. Deciding who owns a decision. Writing down when an executive needs to be woken up. Standardising the things that don’t need to be different in every market. It’s unglamorous, and it’s much easier to fund a new market entry than to fund the discipline that would make the next three entries cheaper.

 

And partly because the two conversations don’t meet. Strategy is set in one room and its operational consequences land in another, weeks later, with no clear path back.

 

The same root, two places it shows up

 

What I’ve come to believe, after enough of these engagements, is that the failures look different but come from the same place. A slow, confused response to a sudden change on a match night and a fifth-market launch that costs twice what the fourth one did are the same problem wearing different clothes. In both cases the business has grown past the point where “we’ll figure it out” scales, and nobody has replaced it with anything.

 

That’s why I’m running two sessions at the Acceler8 Lab at SBC Summit Lisbon. The first, takes a single live incident and works through how a well-run operator moves from signal to decision. The second takes an operator entering its fifth market and works through what should stay standard, what should genuinely be local, and what should just be automated. Different scenarios, same underlying fix.

 

If you only make it to one, come to whichever describes the conversation you had most recently.

 

Register here to secure your place: https://gr8.tech/acceler8-lab/