Chief Marketing Officer / India
When the attractive headline needed a different answer
- Marketing colleagues
- 15
- Three leads; ₹4.9 crore annual function expense
- Commercial communication experience
- 31 years
- Industrial products to hospital call-signalling markets
- Company revenue
- ₹58 crore
- FY 2025–26; distinct from the marketing budget
Decisions & consequences
01Withdrawing a response promise that a signal test could not support
In 2022 we prepared a campaign around instant assistance from the patient's call point. The supporting demonstration had recorded a 19-second signal-delivery interval in a defined simulated setup. It had not measured staff attendance or a clinical response. I approved the campaign because the equipment demonstration looked convincing and the phrase seemed to communicate reassurance. A review with Dinesh Mervqashi exposed the gap: we had moved from a technical event to a service outcome that depended on hospital staffing and workflow.
The agency proposed retaining the headline with a small qualification beneath it. That would preserve the creative work and the launch date, but it would leave the main impression unchanged. I chose to withdraw the material. We replaced the claim with an explanation of how a request was carried and indicated, using only the conditions supported by the reviewed evidence. Hospital teams retained responsibility for their response arrangements. We did not turn the 19-second result into a general specification for every installation or suggest that a faster signal necessarily improved a clinical outcome.
The decision wrote off ₹8 lakh of prepared material and required ₹6 lakh of replacement work over four weeks. Sales colleagues needed a revised explanation and a clear answer for buyers who had seen the earlier material. The commercial head opposed the delay because an exhibition booking was already committed. We used that event for scoped product conversations instead of repeating the unsupported promise. I reported the write-off as a correction to my approval, not as an unexpected technical expense.
The new material distinguished equipment signalling from staffed response and carried the relevant installation conditions. We did not claim that the revised campaign had shortened waiting times in a hospital. The outcome was a more defensible account of the offer and a change to how technical review could interrupt a marketing decision. I now ask whether the reassuring result in a headline belongs to our product, to the customer's operating system or to a combination we have not actually evaluated.
Replacing a bedside-point price with a scoped installation illustration
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?
Reducing the reported pipeline while retaining every useful enquiry
In 2025 our campaign report described 120 enquiries as an active project pipeline. A review with sales separated forty-five approved projects with stated timetables, forty-two early research enquiries and thirty-three requests for replacement components. All 120 contacts were real within the fictional case, but they did not represent the same buying decision. The first group was still a set of opportunities rather than orders. The other groups needed relevant responses without being used to inflate the forecast for new installations.
The campaign lead wanted to retain the total as the main success measure because it showed the strongest improvement against the previous activity. I had accepted that presentation and asked the team to change it. We recorded purpose, timing and the next agreed action, then created different follow-up routes for project discussion, research and component support. Technical and service colleagues helped define the handover so that a replacement request did not disappear merely because it was outside the new-system campaign. We kept the original enquiry total available while separating its commercial meaning.
The eight-week programme cost ₹19 lakh for record review, revised intake questions, sales materials and staff training. It was a change to our marketing and sales process, not a claim that a software field alone could determine buyer intent. Some contacts could not yet answer the qualifying questions; those uncertainties remained visible. We also redirected part of the team's time from collecting additional names to helping buyers clarify their requirements. I reported the smaller active-project count to the CEO with the reason for the change and the continuing work attached to the other enquiries.
The revised report showed forty-five timed, approved projects, forty-two research conversations and thirty-three component requests. It did not claim that the forty-five had converted or that the correction created incremental revenue. The outcome was a more useful allocation of attention and a less inflated basis for planning. I learned that marketing accountability includes reducing a number I had previously presented favourably when its categories do not support the decision management is making.