Leadership review
Leela Vardhane
Chief Strategy Officer · India
Highlights
54
Strategy colleagues
Six direct reports at October 2026; fleet operations and driver management separately led
₹14.8 Cr
Delegated strategy expense
FY 2026-27 function remit, distinct from fleet and depot capital approval
31
Years reading freight demand
Commercial career began July 1995; executive board presentations from March 2021
A letter from the chief strategy officer
I look for the commercial purpose of the journey after the first delivery. An outbound opportunity can be attractive while its return depends on a market the company has barely examined. Adding another sector does not diversify demand if its busy period coincides with the existing peak. My contribution is to make direction, timing and commitment status part of the growth choice. I want the network to be explained as a set of freight relationships, not only as vehicles, depots and a total amount moved.
My first interest in logistics was commercial rather than mechanical. I wanted to understand why a customer needed a movement, what it committed the carrier to do next and whether the return journey had a purpose of its own. A busy outbound route could make a network look successful while leaving the other direction dependent on chance. That question has followed me through thirty-one years at the fictional Navrathin Logistics, from analysing enquiries to explaining the shape of the company's portfolio.
Leela Vardhane
Chief Strategy Officer
Strategic priorities
01
02
03
04
Performance
Priority outcome 01
The 2023 Pune–Ahmedabad corridor account at Navrathin Logistics showed forty-eight weekly outbound departures and eleven booked return loads. A ₹64 crore depot-expansion proposal was being discussed as the next growth step. I wanted the institution to examine who would use the return movement before it treated a larger physical presence as the answer to the corridor's commercial imbalance. Kunal Tervade supported the depot proposal. He believed stronger local presence could itself help the company win return customers and give the network a more credible position. Waiting for demand to be fully established could make the opportunity harder to develop. I accepted that the relationship between presence and demand could work in both directions. My concern was that the current paper made the outbound strength carry too much of the argument for the wider commitment. I recommended a six-month commercial-return pilot with ₹3.8 crore expense, while deferring the depot expansion. The work concentrated on customers whose movement requirements could fit the return direction. Commercial and operating teams owned the actual discussions and service arrangements. Strategy's task was to make the return-market question specific and connect its evidence with the later network decision, not to prescribe driver schedules or imply that any available load was suitable for the vehicles and service concerned. Booked return loads averaged twenty-three weekly during the final eight weeks of the pilot, compared with eleven at the start. That was a partial commercial result. It did not fill the return side of all forty-eight outbound departures, establish a profit improvement or prove that the pilot alone caused every additional booking. The institution needed to retain the remaining imbalance and the responsible teams' account of the work before deciding what the depot proposal should become. The response postponed capital and surrendered some of the local presence Kunal wanted earlier. I learned to treat a return journey as a market proposition requiring its own evidence, rather than the residual movement after the attractive outbound sale. All routes, volumes and results here are fictional. A real case would need authorised booking and operating records; the public narrative should not infer financial or safety conclusions merely because the direction of a volume measure has improved.
Priority outcome 02
In 2017, a consumer-packaging opportunity at the fictional Navrathin Logistics modelled ₹180 crore annual revenue. Its forecast activity placed 62% of movement in October to December, the same period as a substantial existing peak. The proposal was introduced as sector diversification. I thought that description needed a second view: a new customer category could still ask the network for much of its work at the time it was already most stretched. The commercial sponsors preferred the larger opportunity. They argued that the company's knowledge of the peak period and customer requirements could make the concentration manageable. A familiar busy season was not automatically a reason to reject growth, and the forecast revenue was attractive. I agreed that a different industry label did not have to produce a different demand pattern to be worthwhile. But the institution should choose the overlap knowingly rather than claim diversification simply because the goods belonged to another category. I recommended prioritising an industrial-spares opportunity with a smaller ₹92 crore modelled annual revenue figure and a different movement pattern. The choice did not presume that steadier demand was intrinsically more profitable. Finance, sales and operations needed to assess its actual requirements. My contribution was to bring timing into the portfolio comparison and explain why the smaller forecast could be strategically relevant, including the larger headline we were choosing not to pursue first. Four new customers generated ₹27 crore actual service income in FY 2018-19. I kept that result separate from the ₹92 crore model. It showed realised business at a stated scale, not achievement of the entire opportunity. The consumer-packaging proposal also remained a plausible alternative, rather than becoming a mistake simply because we had chosen another direction. The account makes no claim that the selected business removed the peak, improved margin or solved every capacity question in the network. I learned to describe diversification through the dimension that matters to the institution's choice. Industry, customer, direction and season can tell different stories about the same portfolio. The strategic paper should make those differences visible before one label settles the interpretation. Every company and amount in this demonstration is invented; a real comparison would need verified forecasts, actual income definitions and an operating assessment of the demand patterns being considered.
Priority outcome 03
A 2021 shipper proposal used 90000 tonnes as an annual forecast while recording a 54000-tonne stated minimum. The initial commercial discussion contemplated a three-year arrangement. I was concerned that the larger figure was becoming the number around which the network choice was being explained, even though the proposal itself distinguished an expected volume from a narrower commitment. The account team wanted to retain the 90000-tonne forecast prominently. They believed the customer relationship could grow and that an overly narrow presentation might make the company appear unwilling to support the full opportunity. I agreed that the forecast belonged in the discussion. The problem was not its presence but the meaning it acquired when repeated without the stated minimum beside it. A credible growth account needed to show both the possible scale and the basis on which the institution was being asked to commit. I recommended negotiation around a two-year scope based on the 54000-tonne minimum, retaining the larger forecast as a separate planning scenario. The resulting agreement was signed in 2022, with ₹1.4 crore in commercial preparation expense. The authorised commercial and legal teams owned the terms; finance and operations assessed their relevant implications. My role was to keep the strategic account aligned with the distinction in the proposal rather than allow the highest volume number to act as a substitute for the agreement actually being developed. The shorter period and narrower basis gave up some of the scale and duration the original proposition suggested. The signed agreement was the result claimed. It did not mean 90000 tonnes had moved, that the minimum had already been delivered or that a particular revenue amount had been earned. Those would require later evidence. The institution had a more specific commitment account from which to plan, while the larger customer opportunity remained a possibility rather than an accomplished outcome. I learned that a forecast can become a commitment story through ordinary repetition, without anyone explicitly deciding to change its status. Strategy needs to notice that movement of meaning. The fictional case does not interpret a live contract or advise on enforceability. It shows how a leader can preserve the value of an opportunity while making the basis of the selected commitment intelligible to people responsible for the network's next decisions.
Priority outcome 04
In 2006, I used a cohort of 720 journey legs, 480 of them loaded, to suggest that two-thirds of the return circuits were balanced. The arithmetic for loaded legs was correct, but the conclusion was not. The cohort consisted of 360 two-leg circuits: 120 carried loads in both directions and 240 carried a load in only one direction. Only one-third of the circuits were loaded both ways. Mihira Dervankar challenged the interpretation. I had allowed a useful activity measure to answer a different network question. Some colleagues wanted to retain the two-thirds headline because it still described a substantial amount of loaded movement. They were right that the underlying leg count did not become false. But it could not establish the balance of complete circuits, and the distinction mattered to a strategic account concerned with the return market rather than total loaded activity alone. I withdrew the return-balance claim and supported ₹32 lakh review expense. The corrected presentation kept both measures: 480 loaded legs out of 720, and 120 both-loaded circuits out of 360. I explained why the earlier conclusion should no longer be used. It was not enough to quietly change the label in a later paper, because people had already carried the stronger interpretation into their view of the network. I needed to make the source of the error visible and own the judgement that had allowed it. The correction did not establish empty mileage, fuel use or profitability. A count of legs gives no distance measure, and the commercial result depends on more than whether a vehicle carries something. The review therefore restored the meaning of the chosen measures without claiming a broader operating improvement. I did not present the ₹32 lakh as an investment that had already paid for itself. The immediate consequence was a less flattering circuit account and further work on the underlying analysis. That episode changed how I read freight totals. I ask which unit a percentage uses and whether the conclusion remains about that unit. The figures, people and company are fictional, but the arithmetic is explicit so a reader can assess the mistake. A real public case would need an authorised and well-defined cohort. The lesson is to keep an accurate numerator and denominator from acquiring a different strategic meaning simply because the resulting headline sounds more encouraging.
Priority outcome 05
A 2025 review proposed closing a coastal branch that had recorded ₹36 crore revenue in FY 2024-25. The branch also supplied six weekly return loads to an inland circuit. A branch-level account made closure understandable, but it did not fully explain what the wider network would lose. I wanted the institution to examine whether the collection relationship needed to continue even if the company's own premises did not. The closure sponsors wanted a decisive withdrawal. They argued that retaining arrangements around the location could prolong attention to a business the company had already chosen to leave. That concern was reasonable: a nominal closure can become an indefinite programme of exceptions. I did not recommend preserving every part of the branch. I asked whether the six return movements served a specific commercial purpose elsewhere and whether a bounded partner arrangement could retain that purpose without recreating the old operation. We closed the company branch in January 2026 and established partner collection in three towns by June 2026, with ₹2.6 crore in twelve-month support. The responsible commercial and operating teams managed the actual arrangements. Strategy connected the branch decision with the network relationship so the institution could distinguish leaving a physical presence from abandoning every movement associated with it. The support period and expense were part of the choice rather than an unrecorded consequence of making the closure headline simpler. The outcome was a closed branch and a new collection arrangement at the stated locations. I make no claim about an aggregate saving, unchanged service performance or the final profitability of the inland circuit. Those results would require their own evidence. The selected approach also accepted continued coordination after closure, which was the complication the sponsors had wanted to avoid. It needed to remain bounded to the purpose identified rather than become a general reason to keep every discontinued activity alive through another name. I learned to ask what relationship the network wants to retain before deciding which local form it needs. Sometimes the answer may still be a complete exit. In this invented case, the return movement justified a narrower continuing proposition. A genuine account would require authorised customer and partner evidence. The strategy should explain both the activity stopped and the specific connection preserved, so a reader can understand the choice beyond the revenue of one branch.
Year in review
Navrathin Logistics
Connect directional freight demand, customer commitments and branch choices with the commercial purpose of the network.
Navrathin Logistics
Evaluate growth through the timing and direction of demand rather than the revenue headline or sector label alone.
Navrathin Logistics
Bring regional opportunities into a wider account of freight relationships and the role of the return journey.
Navrathin Logistics
Lead regional commercial work and correct an owned confusion between loaded legs and balanced circuits.
Navrathin Logistics
Study shipper requirements with direction, timing and the status of the customer’s volume expectation retained.
Stakeholder voices
Leela corrected the circuit claim instead of defending the more flattering percentage. She kept the loaded-leg measure useful without giving it a different meaning.
I wanted the depot proposal to lead. Leela asked who would buy the return movement and kept the incomplete result visible when the pilot ended.
Outlook
I examine a corridor whose outbound strength could not settle the return-market question, and why a partial booking result mattered more than a premature claim of network balance.
Read the essayI consider a sector-growth proposal whose seasonal shape mattered alongside its larger revenue forecast, and why a different label did not settle the diversification claim.
Read the essayI revisit a loaded-leg calculation that became an incorrect claim about balanced circuits, and explain how to correct the interpretation without discarding the useful activity measure.
Read the essayAn invitation
I would explore a strategic discussion about directional demand, sector mix or the commercial assumptions of a freight network. A possible first-board opportunity would require preparation, employer permission, conflict review and realistic availability. This fictional person offers no transport operation or contract advice. A genuine introduction should set out the network question through an approved route, leaving shipper terms, driver information and restricted operating records within their authorised processes.
office@leelavardhane.example