NovProduct positioning starts with the change the buyer wants
Naming, branding and a polished landing page cannot fix an unclear job-to-be-done. Define what should become different in the buyer’s world.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
Teams can spend days debating whether a programme is a “system”, “lab”, “accelerator” or “membership”. If the buyer still cannot explain why they need it, the positioning problem remains.
I start with the change the buyer wants in their working reality. A category name can help people recognise the type of product, but it does not define the job. “Growth system” sounds substantial and still leaves a basic question unanswered: what becomes different after I buy this?
Describe the situation before you describe the solution
A creator may say they want a marketing system. Dig deeper and the frustration may be having to rebuild demand manually before every launch. A company may ask for automation when the real problem is that enquiries disappear between marketing and sales. A founder may ask for “better analytics” because nobody can explain which channel produces qualified conversations.
Those situations are much more useful than the category label. They tell you what the buyer is trying to stop, start or make more reliable.
This is why I prefer to examine behaviour. What is the team doing manually today? Where does work pile up? Which decision takes too long? What does a bad week look like? What would have to change for the buyer to say the product worked?
The clearer those answers become, the less pressure there is to invent impressive language.
A positioning claim should survive one follow-up question
“Scale sales” sounds attractive. My next question is: what specifically becomes easier, faster or more predictable? If the answer is another layer of abstraction — growth, efficiency, transformation — the claim has not reached the operational reality yet.
A useful statement often contains a visible before-and-after. Perhaps the team stops rebuilding the same launch process every month. Perhaps customer context reaches the salesperson without manual copying. Perhaps management can distinguish audience growth from commercial demand.
That does not mean every headline must include a paragraph of detail. The short line can open the door. The explanation beneath it should make the promise testable.
One of my favourite checks is retelling. After reading the page, can a prospect explain the product to a colleague without repeating the brand’s own category words? “It helps us stop losing enquiries after the form” is stronger evidence of clarity than “It is an integrated revenue operating system.”
Boundaries are part of the position
Positioning gets stronger when the buyer can see who should not buy.
If the product only works for teams with an existing audience, a certain volume of leads or a person responsible for implementation, that condition belongs in the decision before payment. Hiding it widens the apparent market and weakens the actual customer fit.
The same applies to the nature of the problem. An automation product may be excellent for a repeated process and nearly useless where every project is unique and low volume. Saying “save time with automation” ignores the condition that makes the promise true.
Clear exclusions can feel commercially uncomfortable, but they reduce the cost of wrong expectations. They also make the positive case more credible because the product is no longer pretending to solve every adjacent problem.
Evidence should match the promise
A positioning page is not only a set of words. The evidence around those words matters.
If the claim is about speed, show where time is saved. If the claim is about lead handling, demonstrate the path of a lead before and after. If the value is ease of use, a product walkthrough may be more relevant than a quote saying “great experience”.
Social proof and proof of a specific outcome are not the same thing. A thousand customers can reduce perceived risk, but that number does not establish that a new buyer will achieve a particular result. A case study can be useful, but only if the starting conditions are clear enough for a reader to understand whether the comparison is meaningful.
For every major promise, I ask what kind of evidence would actually support it. Sometimes that is a demonstration. Sometimes it is a number. Sometimes it is a process description. Sometimes the most persuasive evidence is a precise limitation.
Positioning continues after the landing page goes live
Questions from sales conversations are a live test of the message. If prospects repeatedly ask the same basic question, the page may not be answering it clearly enough. If people arrive expecting a feature the product does not have, the problem may be in the promise, not in the sales team.
That does not mean adding every question to the homepage. The task is to identify when the uncertainty appears and place the answer at the right stage.
A product name can be changed in an afternoon. Selling the wrong problem will spread through ads, emails, sales calls and customer expectations for months. That is why I would spend more time defining the change the buyer is paying for than polishing the label placed on top of it.