Ask most founders how they think about competition and they will describe a feature comparison - who has the faster delivery, the cheaper subscription, the better UI. That is a real fight, and it is also the wrong one to spend a positioning budget on, because it accepts the terms someone else set.
The founders who actually build category leaders spend that budget earlier - on naming the problem before a customer has a tidy way to describe it themselves.
Being the answer is a rented position
If your pitch is “we do what they do, but better,” you have accepted their frame. Every gain you make is measured against their definition of value, and every feature they ship next resets the comparison to zero. It is an expensive way to compete, because you are financing someone else’s category.
Naming the problem is different. It means putting language around a frustration customers already feel but have not yet organized into a request - not inventing a need from nothing, but being first to say the sentence that makes an existing ache legible. Once that sentence exists, competitors are no longer being compared to you on your terms; they are being asked why they don’t do the thing you named.
The tell is in the vocabulary
Watch how a customer describes their problem six months after a category-namer has been in market. If they are using words the company coined - not the company’s brand name, but its language for the problem - the position is working. If they are still describing the problem the generic, pre-existing way and just slotting your product name into an old sentence, you are still renting.
Why founders skip this
Naming a problem is uncomfortable because it requires taking a specific, falsifiable stand before the market has confirmed you’re right. Feature comparison feels safer because it is defensible with a spec sheet. But a spec sheet is exactly what a well-funded competitor can match in one product cycle. A category definition takes a competitor years to dislodge, because dislodging it means convincing customers to unlearn language they already use comfortably.
This is not a copywriting exercise. It has to happen before the product roadmap locks, because the problem you choose to name will quietly decide which features get built next. Founders who treat naming as something marketing does after launch usually find, a year in, that their product and their story have drifted into two different categories - and rebuilding the story is far more expensive than getting it right the first time.