Look for the obligation the proposal leaves out

I review a module's commercial activity alongside the commitments that survive it. In one portfolio of forty-eight modules, eleven showed no recent activity, but three remained necessary for explicit client obligations. That changed the retirement proposal. The useful method is to connect the product record with contracts, support arrangements, customer dependencies and the proposed transition, involving the colleagues who own each source. A quiet usage report cannot make those obligations disappear. I ask for the cost and owner of the transition before treating retirement as a resource release. This does not mean retaining every old product indefinitely. It means distinguishing a decision to stop new investment from the work needed to end or transfer an existing commitment responsibly, so the organisation knows which part it has actually approved.

A build-or-license comparison needs a common decision question even when the alternatives cannot be made economically identical. Our proposed internal engine build carried a ₹9.6 crore, twenty-four-month plan; the selected licence involved ₹2.4 crore over three years and ₹3.1 crore integration work. The licensed route also had renewal, permitted-use and ownership conditions. I kept those differences visible instead of reporting the initial cost gap as a saving. Strategy should help the authorised decision-maker understand timing, control, future dependency and what would happen if the relationship changed. Legal, technical and finance colleagues examine their respective assumptions. My role is to assemble a choice whose consequences can be debated, not to decide that the cheapest initial proposal must be the right long-term architecture.

I combine evidence of buyer need with the practical conditions required to serve it. For an early expansion review we interviewed nine water-utility training teams, eight food-plant teams and seven warehouse teams. Available instructors differed across those discussions, with two, seven and three respectively able to support the proposed pilot format. Those small samples were not market-size estimates. They helped us choose a bounded food-plant pilot because the learning process could actually be organised there. I want a market recommendation to identify what the company expects to learn, how much it is prepared to spend and what would cause it to pause. Strong interest alone is insufficient when the service depends on people, equipment context or client responsibilities that have not yet been arranged.

Expressions of interest, facilities and delivery capability describe different stages of a partner relationship. In our thirty-organisation review, eight had both suitable demonstration facilities and trained instructors, ten had facilities only, seven had instructors only and five had neither in the required form. Six of the eight accepted the initial programme. I used that smaller number in the launch proposal because it represented the capability we could actually organise. The other organisations remained potential future participants, with different preparation needs. A strategy team should not discard them simply to create a neat distinction, but neither should it add them to a network claim before the necessary work is done. The programme needs clear responsibilities, preparation funding and a way to reassess readiness as circumstances change.