Chief Product Officer / India
The simpler offer did not survive the service evidence
- Product employees
- 31
- Three heads; company headcount totals 260
- Annual product function expense
- ₹4.9 crore
- Fleet investment and technical approvals separately controlled
- Career since June 1998
- 28 years
- Service research through portable-power product leadership
Decisions & consequences
012019: our collection delay had become the customer’s rental charge
The short-hire product I approved in 2019 described a straightforward period of use followed by an agreed collection arrangement. Internally, the rental calculation ended at the depot’s return scan. I had accepted that event because it was easy to record and reconcile. I had not examined whether it remained a fair description of the customer’s responsibility when our own collection was delayed. Service head Farah Vezqlarni challenged the proposition using thirty completed booking records.
Twenty-two collections followed the agreed schedule. In eight cases, the customers had met the defined readiness and access arrangements, but supplier-side delays added two days to the charged period. The aggregate excess charge across those eight bookings was ₹1.6 lakh. Those figures belonged to the reviewed set, not an estimate of all historical hire. The mistake was in the product boundary I had authorised, rather than a claim that depot staff had entered false dates or that equipment could be abandoned without a proper handover.
The finance sponsor preferred to retain the depot event because it gave one consistent endpoint and avoided disputed notices. I agreed that a customer’s informal message could not settle every custody or safety question. I disagreed that our easiest internal record should automatically transfer a supplier delay to the customer. Contract, service and finance owners agreed a revised account of the confirmed collection-readiness condition and the separate physical handover. The design preserved required access, custody and safe collection responsibilities.
Management funded ₹36 lakh and six weeks for the product and process revision. Finance corrected the ₹1.6 lakh in affected charges through its own controls. The revised proposition distinguished the event governing the rental period from the later depot scan, with exceptions requiring the responsible owners’ review. I accepted the extra coordination and the loss of an apparently simple rule. The outcome did not prove that every later collection would be timely. It made the consequence of our delay explicit and stopped using completion of our internal journey as a proxy for the customer’s agreed obligation.
2023: one advertised duration concealed three different enquiry routes
A proposed portable-power package used an eight-hour headline because it was easy to understand and suited the duration of many commercial events. The number appeared to make equipment selection simple. Yet an event length was not a sufficient description of the connected load, the conditions of use or the engineering assessment required. I asked the product team to examine twenty enquiries before presenting the duration as the defining promise of the package.
Fourteen enquiries supplied enough load information for the defined review. Six still needed further assessment. Within the fourteen, engineering supported the proposed package for ten applications and identified four that needed a different equipment route. The count therefore became ten supported applications, four alternatives and six unresolved enquiries. It was not twenty confirmed orders, nor did a supported application establish a general runtime across other conditions. Engineering retained the actual suitability judgement and operating limits.
The sales sponsor wanted to keep the eight-hour headline and place the qualifications later in the enquiry process. The argument was that a clear opening would attract customers who could then be assessed individually. I thought the opening itself would teach people what the product was supposed to deliver, making a later qualification look like an exception to a promise already accepted. I recommended replacing the universal duration with a defined application-assessment route and a clearer distinction between a supported package, an alternative and an enquiry that could not yet be completed.
The revision used ₹52 lakh and ten weeks of authorised product and journey work. The twenty reviewed enquiries retained their three different routes; we did not convert the unresolved six into a default recommendation to make the funnel look finished. The revised offer gave up an attractive single number and required earlier technical context. It did not assert a new runtime or energy-saving result. My responsibility was to let qualified suitability alter the commercial proposition before the customer relied on it, while leaving engineering permission with the people authorised to make that decision.
2025: answering a call quickly did not mean power had been restored
A proposed service package described a two-hour restoration promise using a support team’s acknowledgement measure. Both concerned time after a customer reported an interruption, so the distinction was easy to miss in a commercial summary. It mattered greatly to a customer deciding whether work could resume. I requested a review of forty-eight service records with acknowledgement and restoration treated as separate events rather than different labels for the same response.
Forty-one records showed acknowledgement within two hours and seven showed later acknowledgement. Only nineteen showed restoration within two hours; twenty-nine were restored later. These were observed records in the reviewed set, not a forecast or a contractual commitment for every future incident. The figures did not establish that faster answering caused faster restoration. They showed that a claim based on the first event could not honestly describe the second.
The commercial sponsor argued that a short restoration promise would differentiate the package and that service teams could improve after launch. Farah warned that actual recovery depended on the circumstances and the qualified response required. I chose to delay the proposed wording and separate the defined support response from any restoration account. Service and contract owners retained responsibility for what could be committed. The product would explain the escalation route and the unresolved period without making an operating assurance from an attractive measure.
Management approved ₹44 lakh and nine weeks for the service proposition and customer communication revision. The resulting account preserved all forty-eight records, including the seven late acknowledgements and twenty-nine later restorations. No record was removed to make the promise easier to defend. We gave up the universal two-hour restoration headline; we did not claim that the revision itself made recovery faster. The change made the customer’s decision more informed and gave management two distinct performance questions to examine. I would rather sell the support we can describe accurately than let a buyer discover during an interruption that our advertised outcome was actually a different event.