SaaS is the industry that professionalised positioning and still gets it wrong at scale, because the gravitational pull of the feature list is so strong. The homepage says what the product does, the category page says which box the analysts put it in, and the claim, who this is for and what it refuses to be, never gets decided.
The cost is structural: a product positioned by its features competes with every product that shares them, on a comparison page someone else controls.
Name the problem, not the product #
Buyers arrive mid-struggle, not mid-taxonomy. The software that wins names the buyer’s situation more precisely than the incumbent does, because the name reframes the purchase: once the problem is called what it is, only products built for that problem qualify. This is demand creation in its purest software form, and it is why definitional content, the glossary, the comparison, the named test, outperforms feature content for anything bought thoughtfully.
When we took a consumer money product from zero, the naming, positioning and identity were built before the interface: the claim decided what the product refused to become, which is exactly the discipline most roadmaps lack. That engagement ran through to the raise, because a decided claim is also what investors are buying.
Product-led growth does not position you #
The comforting SaaS belief is that the product speaks for itself: ship, instrument, let usage argue. Usage argues retention; it does not argue selection. The buyer who never starts the trial was lost at the claim, and no onboarding flow reaches them. Product-led motion needs position-led selection in front of it, or the funnel optimises a population that was mis-assembled at the top.
The test: if your category page vanished, would your best customers describe you by feature, or by the problem you ended? The second group renews. Build for it deliberately.
In SaaS the durable position is the named problem. Features converge; the name of the struggle, once you own it, does not.