Different contractor names can still lead back to one project

The growth paper showed eighteen rental contracts and 540 units. The customer names appeared to tell a story of dispersed demand, with several relationships supporting the proposed addition to the fleet. The project review told a more concentrated story. Eight contracts covering 270 units involved four contractors working on one underlying construction project. The remaining ten contracts covered another 270 units across six projects. We therefore had seven underlying projects in the selected account, with half the units linked to one of them. Neither the contract list nor the project view was false. The problem was treating the first as sufficient evidence for a conclusion about the second.

Separate contractors can have different obligations, work packages, payment positions and rental needs. The growth sponsor was right to remind us of those differences. A shared project does not make every contract identical, and it does not mean that all units will return at the same moment. Yet distinct counterparties do not remove the possibility that a change in the larger project's timing could affect several relationships together. I wanted the strategy paper to preserve both accounts. The enterprise needed to understand who it contracted with and what underlying activity supported the demand, without forcing those two questions into a single customer-count measure.

The contract and the construction project answer different questions

The review cost ₹44 lakh and concerned the selected 540-unit population. It was not a claim about the distribution of every unit in our 1,800-unit fleet. Commercial and legal colleagues examined the actual relationships; credit and operations retained their own decisions. My team connected the demand account to the growth choice. We did not infer that any contractor would default or make a legal conclusion about one party's obligation from its involvement in the same project as another. The strategic question was narrower: what conditions might affect several proposed service relationships together, and how should those conditions influence the sequence of additional commitment?

A count is useful when it remains attached to the thing being counted. Eighteen contracts describe contractual records. Seven projects describe the underlying project groupings identified in this review. Four contractors within the concentrated project describe another relationship again. None should be substituted casually for the others. A board paper can become misleading without containing an incorrect number if it lets the reader infer a broader independence than the count establishes. I consider it part of strategy's responsibility to make that inference visible, particularly when the number is being used to support a capital proposal whose consequences will outlast the presentation.

The work also required us to distinguish a shared dependency from identical exposure. Contractors may enter and leave at different stages, and their requirements may respond differently to a change in the project. That matters to operating plans and to any further assessment. It would be as careless to assume perfect correlation as to assume independence from the presence of different names. I did not want the review turned into a dramatic claim that half the selected fleet was about to become idle. The finding identified a relationship requiring consideration. Its practical effect needed the context and judgement of the people responsible for those contracts and the service around them.

Concentration is a condition to examine, not a prediction

The sponsor worried that making the project link prominent would discourage growth around a customer base that had supported the business. That concern deserved a response. Concentration can accompany a deliberate, commercially valuable commitment to an important project; it is not automatically evidence of a bad strategy. The issue is whether management understands and accepts the dependency, rather than discovers it after approving additional assets on a different premise. A board may choose concentrated demand for reasons it considers sound. It should make that choice with the concentration in view, not under a headline that equates several contracts with several unrelated sources of activity.

The review did not settle credit policy, staffing, technical suitability or the timing of individual returns. Those questions remained with their respective owners. My contribution was to show how the proposed fleet addition interacted with the selected demand pattern. Strategy can become overconfident when it takes a useful relationship and tries to answer every operational question from it. I wanted the opposite discipline: retain enough specificity to challenge the growth account while acknowledging where another function's evidence was required. That made the finding more useful because colleagues could see what they were being asked to examine rather than defend their entire area against a broad inference.

There was also a communication responsibility toward the customer relationships. We did not describe the finding publicly as evidence of a troubled project or contractor. The case is fictional, but the principle in a real leadership account would be to protect confidential terms and avoid turning internal scenario work into an unsupported external claim. Even within management, the language matters. Saying that several contracts share a project dependency invites examination. Saying that the customers are effectively one risk may conceal differences and encourage conclusions the review has not established. Precision is not a softening of the issue; it is what makes the issue assessable.

Change the next commitment before changing the headline

The original growth discussion concerned one hundred additional units. We changed the sequence and approved forty units for two unrelated projects, with ₹4.8 crore of authorised fleet expenditure. The other sixty units were not committed through that decision. This was a smaller programme with a different demand basis, not a like-for-like saving against the original scope. Nor did the presence of two additional projects establish that the whole company had become diversified. The supported outcome was a revised next commitment, made after a more complete account of the selected relationships. The broader portfolio still required continuing review.

The decision gave up part of the expansion the commercial team wanted immediately. It also required us to explain why a positive relationship history did not justify every proposed addition under the same assumptions. I did not want that explanation to sound like distrust of the contractors or a prediction that the original project would stop. It concerned how the company would sequence capital while retaining room to respond to different demand conditions. A growth plan can remain ambitious while changing which commitments it makes first. The strategic account should make the consequence of that sequence clear, including the opportunities it chooses not to pursue at once.

I would now map the underlying project when a fleet proposition is first assembled, alongside the counterparty and relevant operating context. Waiting until the investment paper is almost complete makes the relationship feel like a new obstacle rather than part of the business from the start. The map need not pretend to predict every event. It should help colleagues identify which assumptions connect several demand records and which further questions need qualified examination. That is a more useful starting point than celebrating the number of customers and then asking why the portfolio behaved less independently than its labels suggested.

For directors, the case is a reminder to ask what supports the diversity management claims. The answer may involve projects, locations, time periods or other shared conditions beyond the names on a contract list. The board should not replace detailed operating or credit work with a simple concentration slogan. It can require management to show the relationship and explain its effect on the next commitment. Our eighteen contracts remained eighteen contracts. The project review changed what we were entitled to conclude from that count, and the forty-unit decision reflected that change without pretending to remove every uncertainty from the fleet's future.