Most Growth Problems Are Actually Understanding Problems: How Flo Scaled Globally

A lot of product teams think scaling comes from adding more channels, more features, or more automation.

But when products reach real scale, the bottleneck usually changes.

The challenge becomes understanding people well enough to simplify decisions for millions of users with completely different motivations, expectations, and emotional contexts.

That’s especially true in health apps. Because unlike many utility or productivity products, health products operate in moments that are deeply personal, emotional, and recurring. Retention isn’t just about habit formation. It’s about trust.

In this episode of Reteno’s Expert Voices & Tips podcast, Oleg Lesov sat down with Bohdan Lopatiy to talk about how one of the world’s biggest health apps approaches experimentation, monetization, onboarding, product growth, and long-term retention.

The conversation moved far beyond simple growth tactics.

It became a discussion about what happens when app businesses mature — and why scaling increasingly depends on segmentation, experimentation velocity, user understanding, and operational clarity.

Because eventually, every app business runs into the same question:

How do you keep growing when the easy growth is already gone?

Retention starts before the paywall

One of the strongest ideas throughout the conversation was simple:

For many subscription apps, onboarding still gets treated like a UI problem. But in reality, onboarding is often a trust-building system. Especially in products where users arrive with uncertainty, anxiety, or highly specific goals.

Flo operates in exactly that environment. And that changes how product decisions are made. A recurring theme in the discussion was that experimentation only matters if teams understand why users behave differently inside the same funnel.

What looks like one audience at scale often turns into multiple entirely different behavioral groups once you dig deeper.

That’s where many growth teams hit friction. The same onboarding flow can perform brilliantly for one segment and fail completely for another. The same paywall can attract high conversion but create weak long-term retention. The same acquisition channel can bring strong CTRs but weak LTV.

At scale, averages become dangerous. And that forces product and growth teams to think less about “best practices” and more about behavioral systems.

The fastest-growing teams learn faster than they ship

Experimentation came up repeatedly during the conversation — but not in the usual “test button colors” sense.

The focus was on operational learning.

Modern app businesses are running inside environments where acquisition costs fluctuate constantly, creative fatigue arrives faster, and user expectations evolve almost monthly. In that environment, experimentation stops being a growth tactic and becomes infrastructure.

But there was an important nuance in Bohdan’s approach:

Velocity alone is not enough. Teams also need the ability to interpret experiments correctly. A failed test does not always mean a bad idea. A winning test does not automatically mean a scalable strategy.

That matters more now because many app companies are optimizing highly interconnected systems:

• onboarding
• subscriptions
• lifecycle messaging
• paywalls
• CRM flows
• pricing
• retention mechanics
• AI-powered experiences
• monetization loops

Changing one layer often affects several others.

This is why strong product organizations increasingly combine quantitative experimentation with qualitative research.

Numbers explain what happened.

User conversations explain why.

And the gap between those two things is where most product insights live.

Subscription businesses are really education businesses

One of the most interesting parts of the discussion focused on subscriptions and monetization psychology.

Subscription apps are no longer competing only on functionality.

They compete on perceived ongoing value.

That sounds obvious. But many companies still underestimate how much explanation matters when users move from one mental model to another.

Especially in mature apps.

When people download a subscription product today, they already carry expectations from dozens of other apps. Some expect constant updates. Some expect utility. Some expect personalization. Some expect AI features. Some simply want friction removed.

The subscription itself is rarely the emotional trigger.

The feeling of fairness is.

That changes how onboarding, CRM messaging, lifecycle communication, and even feature launches should work.

The best-performing subscription businesses increasingly behave less like software vendors and more like continuous value-delivery systems.

That’s where retention and product marketing start merging together.

Not as departments.

As one operating model.

AI is changing product teams before it changes products

Like almost every serious product conversation in 2026, AI eventually entered the discussion.

But the most interesting part wasn’t the feature layer.

It was operational behavior.

A lot of companies still talk about AI mostly through product surfaces: assistants, recommendations, content generation, chat interfaces.

But internally, the bigger transformation is already happening inside workflows.

Research.

Experimentation.

Creative production.

Prototyping.

Knowledge sharing.

Lifecycle optimization.

Product marketing.

The teams moving fastest right now are not necessarily the teams with the flashiest AI features. They are the teams that reduced iteration costs across the organization.

That matters because modern app growth increasingly rewards speed of adaptation rather than long planning cycles.

The market moves faster than quarterly strategy decks now.

And AI accelerates that pressure.

For lifecycle marketing teams specifically, this creates an interesting shift. Messaging automation is becoming less about sending campaigns and more about dynamically adapting experiences around behavior, intent, and timing.

Which also raises the quality bar.

Because once everyone has access to automation, differentiation comes from understanding users better — not simply messaging them more often.

Segmentation became a survival skill

One of the clearest takeaways from the episode was that modern growth systems break when companies oversimplify users.

Broad personas stop working at scale.

“Women interested in health” is not a usable product segment.

Neither is “active users.”

Real growth teams now operate through behavioral segmentation layers that connect acquisition source, onboarding behavior, subscription intent, engagement depth, lifecycle stage, and long-term retention patterns.

That shift changes everything:

• onboarding flows become adaptive
• paywalls become contextual
• CRM messaging becomes behavioral
• retention strategies become lifecycle-specific
• monetization becomes more personalized

And importantly, it changes how teams organize internally.

Because segmentation is no longer only a CRM function.

It becomes a product strategy function.

Product growth is becoming more interdisciplinary

Another subtle but important theme throughout the conversation was the blending of roles.

Modern app businesses increasingly require people who understand multiple systems simultaneously:

• product
• analytics
• monetization
• experimentation
• lifecycle messaging
• user psychology
• AI workflows
• performance marketing

The old boundaries between “product,” “growth,” and “CRM” continue disappearing.

Not because specialization is unimportant.

But because growth loops themselves became interconnected.

A paywall affects retention.

Retention affects acquisition economics.

Acquisition quality affects onboarding.

Onboarding affects monetization.

CRM affects LTV.

AI affects operational speed across all of it.

The companies that understand these connections usually make better decisions faster.

The next era of app growth will belong to adaptive systems

One of the quiet insights behind the entire conversation was this:

The most valuable app businesses are no longer static products.

They are adaptive systems.

They learn faster.

They segment better.

They explain value more clearly.

They reduce friction earlier.

They evolve onboarding continuously.

They connect monetization with retention instead of treating them separately.

And increasingly, they build operational processes that allow experimentation to compound over time.

That’s probably why conversations like this matter.

Not because they provide universal “growth hacks.”

But because they reveal how experienced product teams actually think when operating at scale.

And in today’s app market, thinking systems often matter more than tactics.