Consumer technology · Retention · Monetization
Turning a Seasonal Relationship Into an Always-On One
Every season brought the same players back to the starting line.
I worked on the same fantasy sports platform, where engagement was heavily concentrated around that same recurring cricket season.
When the season ended, engagement dropped off, and every new season meant winning the same players back again: season, disengagement, reacquisition, season.
When the season ended, engagement dropped off, and every new season meant winning the same players back again: season, disengagement, reacquisition, season.
What else could the relationship be worth?
Could the existing player relationship create value outside the original game and season?
The opportunity was bigger than a cross-sell.
The business had another game on the same platform: an always-on game with a very different engagement pattern than a seasonal sport.
Rather than treating the two player bases as separate, I worked with Product, Engineering, Data, and Commercial teams to explore how a seasonal player's existing relationship with the business could extend into that always-on game.
This required more than a cross-sell campaign. The experience itself had to make the move feel natural, not like being pitched a second product.
How do you make the next experience feel natural?
The work focused on reducing the friction between the two experiences and building a more connected player journey between them.
It took multiple iterations over an extended period. Some early approaches underperformed, and parts of the underlying experience had to be reconsidered before the broader model started working as intended.
What changed when the relationship extended beyond one game?
Cross-product engagement grew meaningfully over time.
The more important change was that the business started treating an existing seasonal player relationship as something that could create value well beyond the original game and season. That changed the operating question from "how do we bring this player back next season" to "what other value can this relationship create."
The takeaway
The best retention systems change what happens by default.
A campaign can create a temporary behavior change. Infrastructure can change the relationship itself.
Instead of asking what campaign can bring a player back, the better question is what should happen next for that player if no campaign gets sent at all.
Case studies describe real problems and decisions at a strategic level. Company names, product names, financial figures, campaign mechanics, and other operating details have been generalized or omitted out of respect for confidentiality obligations to past employers.