A capital demonstration can be persuasive because it removes the distractions of ordinary production. The material is ready, the sequence is clear and the chosen model moves through the proposed process as intended. Those conditions help people understand a machine. They can also conceal the question an enterprise needs answered: how much of our actual work does this represent, and what will happen to the rest? In 2023, our proposed ₹12 crore assembly automation scheme was demonstrated around a standard chair configuration. The demonstration was useful. Treating it as a complete account of the order mix would have made it misleading.
Ask what the demonstration leaves outside
I asked the team to examine a defined sample of 2,400 orders before we advanced the proposal. Of those, 1,440 were standard and 960 were configured. The standard group therefore represented sixty per cent of that sample, with forty per cent configured. Those proportions described the reviewed orders, not a timeless forecast of all future demand. Their immediate value was to make the remaining work visible. The proposed sequence did not fully handle the combinations and steps in the configured group. We needed to know who would do that work, with which equipment and skills, around the proposed investment.
The production sponsor had a reasonable argument: substantial standard volume might still justify automation. A machine does not need to process every possible order to be useful. Assembly supervisors had an equally relevant concern: a plan built around the standard sequence could leave their teams responsible for difficult variation without a funded account of how to manage it. These were not opposing attitudes towards progress. They were different views of the work the investment would change. I wanted the capital discussion to retain both, rather than turning confidence in technology and concern about operating detail into rival camps.
Configuration is not merely an inconvenience to remove from a model. It can reflect the product choices the company offers and the requirements through which an order reaches the factory. That does not mean every variation should be preserved indefinitely. It means that a decision to simplify the range is a product and commercial decision, with consequences that should be examined as such. The capital case should not quietly assume simplification has occurred because the proposed equipment works best with a narrower range. A company cannot purchase its way out of a commitment it has not actually decided to change.
We worked with Maya and the operating leaders to consider what capability the business needed next. The discussion included fixtures and training for a wider range of configurations. Those elements were less dramatic than the original automation demonstration, but they addressed a different part of the operating problem. The board was asked to choose between understood scopes, rather than between a supposedly modern future and an unchanged factory. That reframing mattered because a smaller programme should not win merely by being cheaper, just as a larger one should not win merely by appearing more technologically ambitious.
Compare capabilities before comparing prices
The board approved a ₹4.2 crore fixtures and training programme instead of the proposed ₹12 crore automation scheme. The approved work was completed in 2024. It provided the capabilities described in that programme and did not deliver the same standard-model automation. This limitation belonged in the outcome account. Otherwise, the company could make an attractive decision twice on paper: first by celebrating the lower expenditure, then by speaking as though it had still received the larger scheme's benefits. A responsible comparison needs to state which capabilities were chosen and which remained outside the commitment.
Subtracting ₹4.2 crore from ₹12 crore gives ₹7.8 crore. The arithmetic is easy; the meaning requires more care. We had not bought an identical asset for ₹7.8 crore less. The first proposal was not approved and the second had another scope. Calling the difference a realised saving would imply a like-for-like comparison that did not exist. The board could reasonably prefer the second programme without needing that claim. Its decision was about which investment better addressed the current operating question, with the resources and limitations made explicit. That is sufficient reason to choose without inventing an additional financial result.
A similar discipline applies to benefits. Completion of fixtures and training does not itself establish a measured increase in productivity, let alone a clinical benefit for a wheelchair user. Those questions would need relevant evidence, suitable comparisons and professional interpretation where appropriate. I did not want the programme's closing presentation to fill an evidential gap with a plausible number. It should first state what was installed, what training was undertaken and what capability had been made available. The company could then assess its use without confusing implementation with proof of every hoped-for consequence.
For a manufacturing CEO, this can feel like an unnecessarily restrained way to discuss an investment. Teams have worked hard, the programme is complete and colleagues want to describe its value. I think restraint makes that account stronger. It separates the decision we can explain from a result we have not yet established. It also leaves room to learn. If a capability is not being used as expected, the company can investigate without appearing to retract a broad success claim it made too early. Confidence in the work should not depend on closing every uncertainty in the presentation.
Keep the unpurchased promise out of the result
The original automation proposal remained outside our approved capital plan. It could return in a revised form if the order mix, scope or economics supported it. We did not need to declare the technology permanently unsuitable to explain why it was not our next investment. That distinction prevents a particular decision from becoming an unhelpful organisational belief. The useful record identifies the sample examined, the work excluded by the proposed sequence and the capability selected instead. A later team can then revisit the question with new evidence rather than arguing against a simplified story that management once rejected automation.
I would ask a board reviewing a comparable proposal to examine the boundary of the demonstration. Which orders does it represent? Which activities occur before and after the visible sequence? What does the plan assume about product variety, staffing and technical approval? These questions do not require directors to design the factory. They help directors understand whether management has connected the investment with the business it actually operates. The appropriate specialists should still own detailed engineering and implementation. Oversight concerns the completeness of the proposition and the basis on which the enterprise commits capital.
The same questions can improve the executive team's own conversation. Finance can see why the cheapest scope is not automatically the most useful. Production can explain the work that a standard demonstration leaves behind. Commercial leaders can understand how product choices enter the factory's cost and capability. Technical colleagues can preserve approval responsibilities without being cast as an obstacle to a settled investment. The CEO's contribution is to bring these accounts into one decision that can be understood by the board, with disagreements resolved explicitly enough that the final choice does not conceal them.
Our order sample changed the question before the company spent the money. That was the central outcome of the review. We chose and completed a differently scoped programme, retained the limits of what it provided and kept unsupported benefit claims out of the account. A capital proposal should earn approval through its relationship with actual work, not through the neatness of its best demonstration. When the order mix is inside the decision, the enterprise can see both the capability it is purchasing and the work it will still need to perform afterwards.