The product inside your product that nobody designed

There's a cohort in almost every product that nobody talks about in sprint reviews. They signed up, they stayed, they even pay — but they've never once touched the thing the product was built to do.

They live in a secondary feature. Maybe it's the export tool, or the shared workspace, or the notification digest. Something the team built to support the core experience, not to be the experience. And yet for these people, it is.

We looked at journey data across a few mid-stage SaaS products recently and the pattern was more common than expected. In one case, roughly 14% of weekly active users had zero sessions involving the product's primary workflow over a trailing 90-day window. They weren't churning. Their session frequency was comparable to — sometimes higher than — the power users of the core feature. They just lived in a different room of the same house.

The typical response from a product team, when they notice this at all, is to treat these users as underactivated. They get nudged toward the core flow. They show up in activation funnels as red. Someone builds an onboarding drip that says, essentially, "You haven't tried the thing we actually made yet." The framing is: they're lost, and our job is to find them.

That framing misses what's interesting.

If someone uses a peripheral feature for three months without touching the core product, they're not confused. They found value. The fact that it wasn't the value you intended to deliver doesn't make it less real — it makes it more revealing. They've shown you a product that exists inside your product, one you didn't design on purpose, one that solves a problem you may not have language for yet.

This is where the reframe matters: these users aren't failing your activation metric. Your activation metric is failing to describe what they're doing. The journey they're on is coherent. It just doesn't match the journey you mapped on a whiteboard six quarters ago.

Latent demand is hard to see precisely because it shows up sideways. It doesn't come through the front door of your positioning. It doesn't fill out the form you expected. It adopts a feature you under-invested in, for a use case you under-imagined, and it sustains itself quietly while your team optimizes the primary funnel. The signal is in the sustained engagement with something you thought was secondary. Sustained is the key word. A one-time detour is noise. Repeated, chosen, weekly use of a feature you'd call peripheral — that's someone voting with their attention for a product you haven't built yet.

Companies that catch this early sometimes find their next product line. Slack was a side feature of a game. Flickr was a side feature of a game. The examples at the top are famous, but the phenomenon doesn't require a pivot to matter. Sometimes it just means a feature deserves its own positioning, its own onboarding, its own audience — instead of being buried two clicks deep in a nav bar designed around someone else's workflow.

One counterpoint worth holding: not every secondary-feature cohort represents a real market. Some of them are just people who found one useful thing and never needed more. The difference between a latent product and a convenient utility is whether the usage pattern grows — whether those users start pulling other people in, or whether they start asking for things adjacent to that feature rather than adjacent to your core. The shape of the requests tells you which one you're looking at.

The quiet thing about sideways adoption is that it doesn't ask for permission or attention. It just keeps showing up in the data, waiting for someone to read the story instead of the score.