Is your new product really protected from your core business?

Everyone in this industry knows the risk they are sitting on. One Google update can wipe out three years of ranking work in a matter of days. A regulatory change can close a market before the quarter ends. Most people running affiliate businesses have felt this at some point, and most have decided to do something about it.

The problem is not the decision to diversify, but everything that happens after it. This story is not about one company; it is a story about what happens when a business that is very good at one thing tries to build something completely different.

We had the wrong expectations from the start

The people who built big businesses in iGaming are, almost without exception, comfortable with risk. That comfort is part of what got them where they are, but it creates a real problem when they try to build something new, especially something that works on completely different rules from the core business.

In affiliation, the logic is fast; you try something, see the numbers, and either push harder or stop. That rhythm works brilliantly when you know the game. In product development, it is almost exactly the wrong approach.

A new product needs a realistic runway, and that means three to five years, not three to five quarters. What you should be focusing on in year one is not revenue, but user behaviours and feedback. 

Almost every product that looks like a success today spent years looking like it was going nowhere. Most businesses in this industry never give their new initiatives the time they need because they apply affiliate logic to a product problem and then wonder why it does not work.

The hire that should have changed everything

We had already failed one too many times with a new product. We moved too fast, spent in the wrong places, and shut it down before it had a real chance. The board had not forgotten that, so when the next opportunity came along, and this one had real potential, the room was cautious, and understandably so.

Early on, it became obvious that we did not have the right person with the right skillset internally to lead it. That was a hard thing to admit, but it was the right call. We decided to hire someone from outside who had actually built this kind of product before. The message from the board was simple: get this hire right, because there was no safety net below it.

While we were searching, I slowed things down, paused the big partnership conversations, and held off on the major decision until the right person was in the building and properly up to speed. Some people around me found that frustrating, but handing over half-made decisions to someone who has just walked in the door is not fair to them or to the product.

The hire was good. He understood product-led growth; he had done this before, and for a while, things were moving in the right direction.

Then it started to unravel

A senior person in the broader organisation started taking an interest, not someone with a direct role in the product, not someone who had been asked to get involved, but senior enough that when they had an opinion, people listened, including, eventually, the person we had just hired to run things. 

This behaviour is something I have seen more than once in this industry, and it is worth highlighting: having a lot of experience in one area does not mean that experience transfers to every other area. Seniority can make it feel that way, especially in a culture that moves fast and rarely pushes back on people who have been around a long time.

This influence happens when you have someone senior who thinks they are an expert at everything. Someone with influence but no direct accountability starts steering, not necessarily because they are trying to undermine it (even though I had my doubts). Still, because the structure allows it, and once it starts, it rarely stops.

I did not ask the right question early enough, and that is on me as much as on anyone else. The question was not about the product or the market. It was about protection. When a bad quarter hits and everyone is looking for somewhere to redirect energy and budget, is there anything stopping them from pointing at the new initiative?

Honestly, we knew the answer was no before we admitted it to ourselves. And what came next did not arrive loudly. There was no meeting where someone took over, no memo changing the direction. Just a gradual shift, more opinions in the room, less space for the person we had hired actually to lead, and a quiet but unmistakable message that visible results mattered more than the right ones.

So the budget went way too far into acquisition, not because the product was ready for it or because the numbers told us to, but because someone with influence decided that visible progress was more important than the right progress.

He did not leave. He just stopped fighting for his own judgment. Bit by bit, he started doing what he was told rather than what he knew was right. That is a very specific kind of loss; you have not just lost his contribution, you have lost the whole reason you brought him in.

Good ideas stifled by bad conditions

Within a year, we spent most of the budget. The users we acquired were not the right ones, and they did not stay. The product was quietly sunsetted not long after, and the person we had hired to lead it left, not because he had failed, but because we had made it impossible for him to succeed.

While we were chasing numbers, our competitors were quietly building. No big announcements, no pressure to show progress before the product was ready. They just kept going. By the time we closed ours down, they had something that worked, not because they were cleverer than us, but because nobody had pulled the rug from under them.

The idea was still good. It had always been good. But good ideas do not survive bad conditions. Three things went wrong, and none of them was about the product:

• The success metrics were wrong from the beginning. We set revenue targets for a product that had barely had time to find its feet, and then used those targets to judge whether it was working. Of course, it was not hitting them. Nothing does at twelve months. What we should have been asking was much simpler: are people using it, do they come back, do they recommend it? Those are the signals that matter early on. We were not even looking at them.
• We hired the right person, only to make it impossible for them to do the job. Bringing in external expertise only works if the organisation is willing to step back and let that person lead. The moment someone more senior starts overriding the decisions of the person you hired, you have not delegated the product; you have just added an expensive layer of confusion.
• There was no real separation between the new initiative and the core business. The budget sat in the same pool shared by the same people, and when the core business had a few hard months, everything that was not immediately revenue-generating became fair game. A new product cannot compete with that pressure if it lacks structural protection against it.  

When the sharp people stop believing

There is a cost to a failed diversification attempt that never makes it into the post-mortem. It does not show up in the budget review or the board presentation, but it is real and it is expensive.

The sharp people in your organisation, the ones you most need committed to the next big initiative, were watching. They saw what happened. They saw a real opportunity get starved the moment the core business felt uncomfortable. They did not say anything as they are too smart for that, but certainly filed it away.

The next time leadership stands up and says, "This time will be different”, those same people show up. They do the work. But they hold something back because they have already seen how the story ends. The commitment looks the same from the outside. The belief behind it does not.

Good leaders can feel that shift even when nobody names it out loud. Most organisations never connect it back to the project they walked away from two years earlier, and they wonder why the culture feels a little flat, why the best people seem slightly disengaged, and why the next initiative never quite gets the traction it should.

It is not a coincidence; it is a ripple effect, and it starts the moment you let something real get sacrificed for something convenient.

What actually has to change

Diversification does not fail because the ideas are bad. It fails because the conditions around those ideas are never properly built. Three promises should be made before initiating a project: 

• Give the new initiative its own budget, one that cannot be touched when the core business has a rough quarter. 
• Give the person leading it real authority, and agree on what that means right from the get-go. 
• Decide early what success looks like at 12 months, two years and three years, and make sure those definitions reflect where the product actually is, not where you need it to be for the board presentation.

AI will speed up how quickly you can build and test, but it will not shorten how long it takes a product to earn trust, find its market, and move from early adopters to something sustainable (yet). That curve has not moved; the businesses that mistake faster building for faster product-market fit will make the same mistakes just more efficiently.

The moment that tests all of this is not when the new product is struggling, but when the core business is struggling at the same time; that is when every shared resource snaps back to protect what already works, and that is when the line breaks. This moment is harder to prepare for than it sounds, and most businesses find out too late that they were never really set up to do it.

The companies that succeed will not be the ones with the smartest ideas. They will be the ones who protected those ideas when it was inconvenient to do so.