The entry item and the working configuration are different offers

## Read the whole presentation as a customer would

A product presentation can contain only accurate prices and still leave a reader with the wrong account of what must be bought. The base bench exists at the stated figure. The storage module also exists at its stated figure. Yet the image shows a task using both while the most prominent number belongs only to the first. The difficulty is not arithmetic. It is the relationship between the task being promised, the configuration being shown and the amount a customer reasonably expects to pay for that configuration.

In our fictional range review, the base bench was ₹41,000 and the storage module ₹17,000 on the same product-price basis. The depicted working configuration therefore amounted to ₹58,000 before separately stated taxes and freight. Among forty quotations we examined, twenty-seven workflows required the storage arrangement and thirteen did not. The figures did not support making storage compulsory for everybody. They did show why using the base number alone beside that particular workflow gave an incomplete account to many of the readers the proposition was intended to help.

I had approved the earlier presentation because the component information was available. A customer could, in principle, read the options and reconstruct the total. That was an insufficient test. Product management should ask what the page itself invites someone to assume, not only whether a determined reader could eventually discover the qualification. A task photograph has persuasive force. If the product team uses that force to explain usefulness, it also has to explain the configuration that makes the depicted task possible on the terms being offered.

Commercial colleagues worried that a more complete number would make the range appear expensive beside competitors' entry figures. Their concern was real. A buyer comparing several offers may initially see little more than a photograph and a price. We could not solve that market habit by pretending it did not exist. We could decide whether our response would make the comparison clearer or depend on the same ambiguity. I wanted the base offer to remain visible while giving the relevant configuration an equally intelligible account.

## Separate necessary for this task from compulsory for everyone

The first question was what the example actually required. A component can be optional across the range and still be necessary for the workflow used in a particular demonstration. Those descriptions are not contradictory. They become confusing when optional is treated as though it means irrelevant to every customer's total. I asked product and commercial colleagues to describe the job first, then list which items performed it in the example. That gave the discussion a concrete basis instead of arguing abstractly about whether accessories should always be bundled.

The thirteen reviewed workflows that did not need the storage module mattered as much as the twenty-seven that did. Forcing a common bundle on them would have solved our presentation problem by creating a different buying problem. They might already have suitable storage or organise the task differently. Product management should not turn a clearer account into an excuse to sell an unnecessary component. The right outcome was a visible choice between a base item and a defined working configuration, with a reason for the difference that a customer could understand.

Selection still required context. The forty quotations were a review population, not a complete map of every future customer's needs. Technical suitability, the actual workplace arrangement and commercial terms retained their normal owners. A product illustration cannot replace those judgements. Its purpose is to make the first comparison more honest and useful, so the customer reaches the next conversation with a reasonable understanding of what is included. That is a different ambition from claiming that one configuration or one displayed amount covers every possible application.

We also had to state the basis of the prices consistently. A comparison becomes unreliable if one figure contains a charge that another leaves elsewhere. In this example both product figures were on the same basis, with taxes and freight stated separately. Authorised finance and commercial colleagues retained responsibility for actual amounts and terms. My role as CPO was to ensure that the product proposition did not quietly depend on a different account from the one the buying example encouraged. Product leadership does not acquire financial authority simply by noticing that the presentation needs correction.

## Make a fair comparison worth the extra explanation

The review cost ₹22 lakh and covered configuration examples, selection material and the proposition itself. We placed the ₹58,000 working configuration beside the ₹41,000 base item, identifying the ₹17,000 storage module rather than hiding the difference inside an unexplained package. The result required more explanation than one entry figure. Sales colleagues had to help customers understand which comparison suited their task. That effort was a cost of the decision, not something to dismiss as resistance to transparency. A useful proposition must remain understandable in an actual buying conversation.

We did not claim that the change had already increased conversion or reduced complaints. The evidence in this account is the reviewed quotations and the corrected presentation. A later commercial outcome would need its own observation period and a careful interpretation of other changes. It is tempting to attach a favourable result to a correction because the correction feels obviously sensible. I prefer to say what was changed and why, then distinguish that decision from benefits not yet established. Doing so keeps the product account open to examination by colleagues who must live with its commercial consequences.

The strongest objection was that customers may still choose a rival after seeing our more complete amount. That possibility remains. A clearer proposition does not remove price competition or make every buyer value the same thing. The decision was to compete with an account we could explain, including the genuine lower-cost base option for customers whose task did not need the addition. It was not a claim that clarity always pays for itself immediately. Product leaders sometimes need to defend a more coherent offer without inventing a short-term return to make the choice sound effortless.

I would now review the image, headline, configuration and price together before approving a range presentation. Different teams often create those elements separately, each correctly performing its own task. The mismatch appears only when the customer encounters the whole. A brief joint review can ask what job the page depicts, what items make that job possible and where each relevant cost appears. It can also ask whether a supposedly optional item has been made visually indispensable. Those questions are easier to answer before the composition becomes familiar and expensive to change.

The board-level implication is broader than accessory pricing. Directors reviewing a product proposition should understand what the advertised entry point leaves for the customer to add, arrange or pay for later. That may be entirely reasonable if the offer makes it clear. It becomes a risk when a favourable comparison depends on the customer comparing different undertakings as though they were the same. In our case the correction was straightforward: preserve the base item, show the task configuration and explain the difference. The work was in accepting that a true component price did not, on its own, make the whole presentation complete.