A 2024 sales illustration showed a bedside call point at ₹6,000 and suggested forty points would cost ₹2.4 lakh. The multiplication was correct, but the example described a component purchase as though it were the complete defined installation. The same scope needed ₹1.8 lakh of central equipment, ₹1.1 lakh of wiring and ₹0.7 lakh of commissioning. Together those items brought the illustration to ₹6 lakh before tax. The omitted ₹3.6 lakh was not an optional enhancement a buyer could simply decline while expecting the illustrated system.
I had approved the short price panel because it was easy to compare and generated enquiries. The sales manager argued that a later site visit would explain the additional items. I considered that too late for a headline that had already shaped the buyer's expectation. Finance and technical colleagues reviewed a complete example on a consistent tax and scope basis. We replaced the panel, identified the essential components and described the assumptions that could change at a real site. The ₹6 lakh figure remained an illustration, not a fixed quote or a statement that every forty-point hospital installation had the same needs.
The five-week correction cost ₹12 lakh in materials, sales aids, training and direct clarification with the affected prospect list. We did not change an accepted contract or invent a recovery of the expense through new sales. Some prospects found the fuller example less attractive, and the number requesting a quick price fell. That consequence was preferable to carrying a misleading anchor into a detailed buying discussion. The team also gained a clearer way to compare scope without asserting that another supplier's lower headline necessarily covered less.
The lesson was that an arithmetically correct unit price can still describe the wrong purchase. As CMO I was responsible for the impression created by the example, even though finance owned quotations and engineering owned configuration. The correction made the buyer's next question more useful: which installation assumptions apply here, and which items are required to support the intended workflow?