Gurmeet QorzaniChief Strategy Officer · Essays & perspective

Chief Strategy Officer India

Give the asset count its operating context

A rental-fleet strategy needs the journeys, seasons and shared project dependencies that an asset count leaves out.

01

Putting movement beside the property line

A depot is a place from which a service is delivered, so its rent cannot be the whole strategic comparison. I work with operations and finance to examine the movements, handling and initial preparation implied by a location under stated assumptions. My own preference for a peripheral site showed how the most visible expense could dominate the discussion. A closer location can still cost more initially, and a favourable recurring estimate is not an achieved saving. I want the board to see that trade-off without turning a bounded model into a complete valuation. The method concerns the business choice and its dependencies; site suitability, permissions, transport arrangements and technical acceptance remain with their responsible owners. A useful recommendation makes those conditions available for scrutiny before a cheap property becomes an expensive service commitment.

02

Reading a high rate through the months around it

Seasonal rental work can offer an attractive daily rate while leaving idle periods, movements and preparation costs that the rate alone does not explain. I ask for an annual account of the defined segment and a clear statement of which costs it includes. The remainder after selected direct costs is not automatically profit, because depreciation, central obligations and financing may still sit elsewhere. Comparing another segment can identify a question worth testing, but differences in units, locations and customers prevent a casual comparison from proving what a transfer will earn. My contribution is to make the choice assessable and define a bounded experiment where evidence is incomplete. Operations retains deployment and technical suitability, while finance retains the accounting treatment and authorised leaders decide the commitment.

03

Looking through customer names to the project dependency

Several contracts can involve separate counterparties while depending on the same underlying construction project. I examine that relationship when a growth plan presents the number of customers as evidence of diversification. A shared project does not mean every contractor will behave alike or that a disruption is inevitable. It means the strategic account should consider a condition that could affect several demand relationships together. The selected 540-unit review made that connection visible without claiming to describe the entire fleet. Credit, contracts and site operations retained their respective owners. I would use the finding to question the sequence and concentration of proposed additions, while avoiding an unsupported default forecast or an assertion that a different customer name always creates a different source of demand.

04

Preserving options while testing a regional partnership

A partner can offer useful local relationships and still ask for rights that exceed what the company has learned about the opportunity. I compare the proposed reach with the duration, exclusivity and service responsibilities the arrangement would create. Those terms need legal and commercial review for the actual relationship; strategy does not supply a universal contract rule. A bounded non-exclusive pilot can preserve room to learn, but it can also reduce the partner's incentive and the immediate scale of its effort. I keep that disadvantage in the recommendation rather than present flexibility as free. The decision should explain what evidence would justify a later commitment and what the enterprise is giving up by waiting, with programme spending and actual contracted activity distinguished from a broad claim about market entry.

A leadership conviction

The fleet is a continuing service commitment, not simply a collection of units available to buy.

Start a conversation