A collection of site files is not yet a commercial data business

## Define the proposed use before counting the available files

A professional-service company accumulates records while doing its work. Over time, those records can appear to offer a second business: an aggregate view that helps clients understand patterns beyond a single assignment. The possibility can be real. It is still only a possibility until the company examines the use it proposes, the relevant permissions and the suitability of the material. Possessing files from completed work does not establish that every file belongs in a new commercial product. A strategy paper should make that distinction before presenting the full count as an available asset.

Our fictional 2025 proposal began with 900 site files. The sponsor saw a potential aggregate view of property-risk conditions that could be useful to insurance clients. The first presentation concentrated on the breadth of the collection and the investment needed to turn it into a product. I asked for the proposed use to be described more precisely. Who would receive the output? What would it contain? Which original arrangements addressed that use, and which parties had authority to consider a change? Those questions determined the population we could responsibly evaluate, not merely the wording of a later publication note.

The sponsor proposed removing obvious identifiers and proceeding with the larger set. That could be one relevant technical measure, but it did not settle every question. Site detail might remain recognisable through combinations of characteristics, and the original professional arrangements might have limits independent of whether a name appeared. Suitable specialists needed to assess the actual records and proposed output. I did not want strategy to convert a useful technical suggestion into a general permission that neither the sponsor nor I could establish through assertion alone.

This is not an argument that every new use must be impossible or that accumulated records have no strategic value. It is an argument for defining the business before valuing its apparent inputs. A product with a narrow, explicit scope may be worthwhile. A broader product may require further arrangements and investment. The company needs to know which proposition it is considering. Otherwise it risks approving expenditure against the scale of 900 files while later discovering that only a smaller population is available for the purpose that made the revenue forecast attractive.

## Let the admitted population shape the learning claim

The review admitted 236 files with the explicit permission required for the defined aggregate-use pilot. The remaining 664 stayed outside it. Those categories accounted for the original 900 without describing the excluded records as useless. They were outside the established scope of this use. We committed ₹42 lakh to the bounded pilot, with technical and professional owners retaining their assessments. The smaller population gave the team something concrete to examine while leaving the broader commercial proposition unresolved. It was a deliberate learning boundary rather than a claim that the original idea had already become a complete product.

Permission to include a file also did not establish that the admitted population represented the wider set of sites. The 236 could differ in ways important to interpretation. The analytical work needed to examine composition and limits before drawing a broader conclusion. This is another place where a strategy summary can make one approval do too much work. A file may be appropriate for the stated use and still be insufficient evidence for a national prevalence claim or another generalisation. The professional account should preserve both the inclusion boundary and the inferential boundary rather than merge them into a single approval label.

The excluded population mattered to the investment review as well. If the intended product depended on a breadth the admitted files could not provide, management needed to know that before committing to a larger launch. Further permission work might be possible, but its result should not be assumed merely because the company already held the records. The alternative could be a smaller product, a different question or a decision not to proceed. A pilot is useful when it leaves those choices open and produces evidence relevant to them, not when it becomes a one-way route to a launch that has already been promised.

The sponsor's disappointment was understandable. The original collection count made the opportunity look more substantial, and a smaller pilot could be harder to explain commercially. I needed to retain that consequence rather than describe the boundary as costless prudence. We gave up the apparent scale of a 900-file product at that stage and spent money without a completed revenue result. The decision was justified by the question we needed to answer, but it remained an investment in learning. Directors should be able to examine whether that question was important enough to warrant the expense.

## Do not make a pilot carry the promise of a finished business

The ₹42 lakh commitment was not proof of a viable data business. It funded a defined exercise with 236 admitted files. The pilot did not establish permission for every future extension, a finished product or revenue already achieved. Those limitations belong in the main account because they describe the stage of the strategy. A leadership narrative becomes less useful when it calls a pilot a launch or lets a promising demonstration stand in for the professional, commercial and operating work still required. The unfinished status is part of the evidence, not a presentational inconvenience.

A board can improve this decision by asking for the chain from records to proposed use to supported claim. What is held? What use has been addressed? Which material is admitted? What can the resulting population establish? What remains before the company can offer a dependable product? These are different questions, and progress on one should not silently count as progress on all of them. Management should explain the relevant owners and the evidence at each stage. Directors can then assess the investment without needing to inspect private site records themselves.

The commercial model also needs to account for continuing work. A product may require new material, revised arrangements and checks as its intended use changes. Those responsibilities do not necessarily end when the first collection has been reviewed. Nor should the company assume that an output suitable for one audience can be repurposed unchanged for another. The actual requirements need specialist assessment. Strategy's role is to keep those dependencies visible in the business case, so that the apparent low cost of reusing existing files does not omit the work that makes the use supportable.

I would put that scope review before the revenue model in a future proposal. The existence of a rich collection is a useful beginning, but it can create confidence faster than it creates a business. In our case, the defensible next step was a limited pilot with excluded files still visible and the commercial result unresolved. That is less dramatic than announcing a new data enterprise. It is also a better account of what the company actually knew and chose. A strategist should be able to describe the possibility without asking possession, permission or a preliminary demonstration to stand for a commitment none of them has yet established.