Possession made the proposal look ready
The product proposal began with an archive we already held. Forty-eight fictional client projects had generated records that appeared relevant to a commercial evidence service. The collection existed, the team understood its format and a larger dataset would make the proposition easier to explain. It was tempting to treat the main remaining work as product design. I wanted to examine an earlier question: what basis did we have for using each project's records for this new purpose? Possession and technical accessibility did not answer that question on their own.
The review found twenty-nine projects with a documented basis for the specified reuse and nineteen with unresolved permissions or scope questions. Those categories concerned the proposed purpose. They were not a permanent statement that one project could be used for anything while another could never be used again. The contract and legal owners needed to establish the relevant conditions. My team's responsibility was to connect those decisions to the records the product intended to include, rather than allow a general statement about the archive to stand in for the individual positions.
Removing client names did not eliminate the need for that review. The proposed product could still use material in ways an agreement did not cover, and a different presentation would not automatically resolve the question. I do not offer a general legal conclusion about anonymisation or contractual rights here. The point is organisational: a data function should not assume that a technical transformation creates permission. The appropriate owners must assess the actual circumstances, and the product should be able to show how their decisions affect its scope.
The commercial sponsor had a reasonable concern. Excluding nineteen projects would reduce coverage and might make the early proposition less attractive. A narrower release could also make it harder to compare some categories consistently. Those disadvantages needed to remain visible. I did not want the discussion to become a ceremony in which everyone praised restraint while pretending that nothing valuable was forgone. The proposed breadth was part of the commercial appeal. Respecting the unresolved positions meant giving up some of that appeal until a proper basis for inclusion could be established.
Two questions that should not be merged
Permission was only one part of the account. Imran asked whether the archive could support the word benchmark in the way the pitch used it. The projects reflected work clients had commissioned from our regional practice. They were not a designed sample of an entire industry, region or category of materials. The reasons a client requested testing could affect the collection, as could the types of work the practice served. Even if every project had been cleared for reuse, the selection would still need an honest description before the product implied a wider comparison.
I find it useful to keep the questions separate. Are we entitled to use these records for this purpose? What can this particular collection tell the intended reader? A favourable answer to one does not supply a favourable answer to the other. Legal clearance does not establish statistical representativeness. A carefully designed analytical sample does not create contractual permission. The data leader needs to bring the owners of both questions into the proposition without allowing either discipline's approval to become a universal endorsement of the whole commercial account.
The twenty-nine-project subset could still be useful. A bounded collection may help a reader examine patterns within its stated scope or compare observations whose conditions are sufficiently understood. It does not have to represent every possible project to provide value. The important choice is whether the product describes that value accurately. If the proposition depends on a claim about the entire market, the organisation may need different evidence. If it serves a narrower question, the smaller collection may support an honest offer without being dressed as a universal reference.
We approved ₹34 lakh for mapping and review, with ₹9 lakh annual stewardship provision for the bounded product. The initial scope included only the twenty-nine projects cleared for the specified purpose, subject to their recorded conditions. The nineteen unresolved projects remained outside it. The data layer retained the relationship between an included record and its permission basis, while the product description retained the collection's selection limits. Those expenses did not buy a universal right or make the sample representative. They funded the work needed to keep the actual product aligned with the account we were prepared to give.
A smaller product with a more defensible promise
The resulting proposition was smaller and required continuing attention. That is a more demanding operating model than declaring the archive an asset and assuming that its value will increase whenever another project is added. New records can bring new restrictions, different methods or a different selection pattern. Existing permissions may also need review when the purpose changes. I want the enterprise to recognise those responsibilities in the product's economics. A service whose commercial case omits stewardship is not necessarily cheaper; it may simply have left part of its work outside the proposal.
There was no invented revenue uplift to make this choice look easy. The fictional case records a narrower release scope and the expense of supporting it. It does not establish adoption, renewal or a premium price. I would expect a real business to test those matters separately. That distinction is useful in a leadership profile because the decision's quality should not depend on a convenient success story added afterwards. We chose a proposition whose scope we could substantiate, while retaining uncertainty about whether the market would value it enough to justify further investment.
At board level, I would ask how management distinguishes an archive from a saleable data product. Which rights, conditions and professional decisions sit behind the proposed use? How was the collection formed, and what does that imply for the claims being made? What continuing resources will keep the product aligned with those conditions? These questions can reveal why apparently similar datasets have different commercial possibilities. They also prevent the volume of stored records from becoming the only measure of a data strategy's progress.
The board should not negotiate every permission or choose every analytical inclusion rule. Those tasks belong with management and qualified advisers. It should understand material assumptions behind a new revenue proposition, particularly when the product can be copied and distributed more widely than the original service. I would want directors to hear the exclusions and the unresolved questions beside the attractive opportunity. A proposal is easier to assess when management explains what would change its scope, what would stop a release and which decisions require another review.
I now describe a reusable collection through its purpose, permission and selection before I describe its size. The order helps the reader understand what the asset can actually become. A larger archive may offer more possibilities, but those possibilities are not identical to a ready product. The forty-eight-project proposal became a twenty-nine-project scope with a narrower promise and continuing stewardship. I regard that as an honest starting point for commercial learning. It allows the business to test real value without asking the reader to accept rights or representativeness that the evidence has not established.