The proposed library looked substantial because our engineers recognised its contents. Sixty-four models had accumulated across years of work, and many contained methods the team understood well. The commercial presentation treated that familiarity as a head start in building a product. I could see the attraction. An archive already in use seemed different from a new capability that had to be developed from the beginning. What the initial account had not established was whether the company could offer every asset in the form now proposed.
The review divided the library into forty-one company-owned generic models, fifteen with client restrictions and eight whose rights remained uncertain. Those categories did not overlap. The first launch contained only the forty-one cleared assets. The smaller number changed the sales forecast, the offer's breadth and the timing of release. It also changed the question I ask when someone describes accumulated delivery work as an immediately reusable company resource.
Separate technical reuse from commercial entitlement
An engineer can often explain why a model would work for another assignment. That explanation concerns technical suitability, assumptions and effort. It may be very good without resolving the rights in the particular material. A model may include client-specific inputs, code, geometry or terms arising from the engagement in which it was developed. Removing a customer's name does not, by itself, establish what may be commercialised. The actual assets and agreements need examination by the appropriate owners.
I do not want that distinction to become a dismissive response to engineers who recognise a valuable capability. Their understanding is necessary. The commercial review needs to preserve it while asking the additional questions. Which material is generic and owned by the company? Which use was agreed with the client? What remains uncertain? What continuing support would a new buyer receive? Treating these as separate questions makes the proposal more useful than either unquestioning enthusiasm or a broad instruction never to reuse anything.
Some colleagues believed the uncertain files could be reviewed after launch because they represented a minority of the library. That framed uncertainty as an administrative backlog rather than a limit on the offer. I asked whether the company was prepared to make a commercial commitment before it had established the basis for doing so. A schedule should not turn an unresolved right into an assumed one. The eight uncertain assets therefore remained outside the launch, alongside the fifteen excluded under the assessed restrictions, though their reasons for exclusion differed.
The distinction between those groups mattered. We did not report all twenty-three as permanently unusable, nor assume that all eight would eventually be cleared. A precise account leaves room for further evidence without treating a hoped-for result as part of today's product. It also helps the board see what management has actually decided. The launch was narrower because the assessed rights supported less than the archive count had implied, not because a technical team suddenly lost the ability to operate the models.
Let the review change the forecast
The programme cost ₹1.8 crore and the launch moved twelve weeks. Our annual sales forecast changed from ₹9.2 crore to ₹6.8 crore. I kept those consequences in the recommendation. A review that changes the offer should change the commercial account, rather than leave sales responsible for a total built around assets they cannot sell. The ₹2.4 crore difference was a forecast reduction, not realised revenue lost and not a valuation of the excluded intellectual property. Those are different claims requiring different evidence.
The sales head reasonably asked whether a smaller library would be harder to position. It would. We had initially sold the idea internally through breadth, and breadth was now reduced. The response was to describe the intended uses and support of the cleared portion more carefully, not imply that the excluded assets would be available on request. A commercial team needs an offer it can explain without quietly rebuilding the rejected promise during a customer conversation. The release record and the selling account must describe the same product.
I also wanted the cost of review to remain visible as part of product development. Rights work can be presented as a late interruption to an otherwise complete engineering programme. In this case it helped establish what the programme actually was. Starting earlier might have reduced rework and made the first forecast more realistic, but it would not have made the underlying assessment unnecessary. A product built from prior work still needs a deliberate account of the rights and obligations that travel with it.
For an executive, the difficult moment is often when an attractive opportunity becomes more qualified after the organisation has invested confidence in it. People may hear a smaller recommendation as a retreat from ambition. I regard it as a test of whether the ambition is answerable to evidence. The board can still choose to fund further development, seek permissions or create new material. Those are new decisions with costs and conditions. They should not be confused with releasing an archive as though those decisions had already been made.
Make the next addition earn its place
The launch established a basis for future additions rather than a permanent conclusion about every model the company might create. Each proposed asset needs its own record of origin, rights, intended use, support and change responsibility. That record should be usable by the people selling and maintaining the product, not exist only in a file they cannot interpret. Technical and legal owners retain their assessments; the CEO's role is to ensure that the commercial commitment follows them.
The same discipline applies when a model is altered. A cleared asset can acquire new inputs, code or client-specific work. Its earlier status is relevant history, not an automatic answer to every later use. I want the organisation to recognise the point at which a change needs further review without making ordinary maintenance impossibly cumbersome. That requires judgement about the material and proposed use, supported by a process that reaches the people authorised to decide.
At board level, I would ask whether the company's growth account distinguishes a technical resource from a commercial asset. What can it use, in what form, for whom and with which continuing responsibilities? Which part remains uncertain, and has that uncertainty changed the forecast? Directors do not need to resolve each ownership question themselves. They do need to know whether management's product and financial commitments rest on an assessed basis rather than confidence generated by a large archive count.
The forty-one-asset launch was smaller than the first presentation. It was also an offer whose basis we could explain. I would start that explanation earlier next time, before a familiar collection becomes a public promise. Engineering knowledge can support a valuable product, but its commercial use is a proposition to establish, not a conclusion contained in the fact that our people once did the work.