Launching a new service inside your existing ecosystem feels like a shortcut.
Users are already logged in.
They trust the brand.
There’s no acquisition cost.
So growth should be easier.
In practice, it rarely works that way.
At Hezzl Games, we surveyed 3,000+ digital service users to understand what actually happens when a new section appears inside a product people already use.
The result: structural presence ≠ behavioral adoption.
Users Don’t Explore Interfaces Without a Reason
When asked how they react to a new section inside a familiar service:
35.7% check it out out of curiosity
42.5% try it if there’s a bonus
21.8% ignore it unless they need it
One in five won’t open it at all.
Users open products to complete tasks, not to explore architecture. If the new service doesn’t help with their immediate goal, it becomes invisible.
System Suggestions Don’t Override User Agency
When the product suggests switching:
12% follow the recommendation
76% evaluate it but decide independently
11.9% dislike automated guidance
Most users don’t outsource navigation decisions — even inside the same brand.
Adding a visible CTA is not the same as creating intent.
“Unified Ecosystem” Is a Strategy Term, Not a Behavioral Driver
When multiple services share unified progress:
25.3% like the idea
57.8% are fine with it if it’s convenient
16.8% don’t care
Convenience matters. Structure alone doesn’t.
If the new service introduces friction — additional steps, new flows, re-learning — ecosystem logic doesn’t compensate.
Trial ≠ Adoption
48.1% are willing to try a new section.
But growth is not first-click traffic.
Growth is repeat behavior.
If the service is not embedded into the user’s existing flow, the first visit becomes a metric spike — not a usage shift.
Your Real Competitor Is Existing Behavior
If similar functionality exists elsewhere:
49.5% choose better value
25.5% choose simplicity
25% choose familiarity
A new internal service doesn’t compete only with the market.
It competes with established habits.
And habits are expensive to replace.
Product Implications
If you’re building cross-service growth inside an ecosystem:
Design transition points, not just navigation links.
Measure repeat usage, not just first entry.
Test behavior without incentives to see if structural demand exists.
Reduce friction to near-zero before expecting switching.
An ecosystem can amplify behavior.
It doesn’t create it from scratch.
Based on a survey of 3,000+ digital service users conducted by Hezzl Games.
Top comments (0)