Paul Graham says product-market fit feels like a pull. The market is dragging you forward. You can barely keep up with demand. You know it when you feel it.
I felt that pull once, briefly, with Anertia. And then I watched it recede. Not because the product was bad. Because the market was not ready to admit it needed what we were building.
That is a different kind of product-market fit problem, and it is one that most frameworks do not address.
The Latent Need Problem
Most product-market fit frameworks assume that the need is visible. People know they have the problem. They are actively looking for a solution. Your job is to find them and convince them that your solution is better than the alternatives.
Anertia's core need: the need for a space where you can say what you actually think, without performing for an audience: is not that kind of need. It is a latent need. People feel it, but they do not articulate it. They do not search for "authentic self-expression platform." They search for "journaling app" or "private social network" or nothing at all, because they have accepted the performance as the cost of being online.
Latent needs are real. They are often larger than visible needs. But they require a different go-to-market approach, because you cannot find your users by solving the problem they know they have. You have to surface the problem they do not know they have.
The Articulation Gap
The challenge with Anertia was what I started calling the articulation gap. Users would try the platform, feel something: a sense of relief, a sense of being seen: and then struggle to explain why they liked it. "It is different," they would say. "It feels more real." But they could not articulate what "more real" meant, or why it mattered.
That articulation gap made word-of-mouth difficult. People could not easily recommend Anertia because they could not easily explain what it was. And without word-of-mouth, growth was slow.
The product was solving a real problem. But the problem was not legible enough to drive organic growth.
What I Would Do Differently
If I were starting Anertia over, I would invest much earlier in the language problem. Not the product language: the user language. The words that users use to describe the problem Anertia solves.
This is different from positioning. Positioning is about how you describe your product. The language problem is about how users describe their need. And the gap between those two things is where most latent-need products get stuck.
The way to close that gap is through intensive user research: not surveys, not NPS scores, but conversations. Long conversations with people who have used the product and felt something. What did they feel? When did they feel it? What were they doing before they felt it? What would they say to a friend to explain why they should try it?
Those conversations surface the language. And the language is the product, for a latent-need product. Because until you can give people the words to describe the problem, they cannot tell anyone else about the solution.
The Broader Lesson
Anertia taught me that product-market fit is not binary. It is not "you have it" or "you do not." There is a third state: you have the fit, but the market has not found the language for it yet.
In that state, the product work is not about improving the product. It is about improving the market's ability to recognize what the product does. That is a different kind of work: more ethnographic, more linguistic, more patient.
It is also, I think, the most interesting kind of product work. Because you are not just solving a problem. You are naming one.
