Testing whether the idea was possible

What they had

An idea whose entire value depended on aggregating and normalizing data at a scale nobody had attempted in that market, and no evidence that the hard part could be done at all. The honest position before any work started was that nobody knew.

What we did

A four week paid discovery. Three weeks on the technical feasibility question itself: which sources existed, how ingestion and deduplication would work, whether a live refresh was achievable, and what data quality and coverage actually looked like once somebody went and measured them rather than assuming. Alongside it, a working dashboard, a brand identity and a clickable prototype, so they finished holding something rather than reading a memo. The fourth week was the retrospective and the decision.

The decision was not to build it. We said so, and they heard the same from other advisers they trusted. Instead of spending a year and a budget finding that out the expensive way, they stopped, changed direction, and started something else. They brought us with them.

The entire value of the idea rested on one unproven technical assumption. Everything else about the business, the market, the model, the design, was downstream of whether that one thing could be done at scale. A founder in that position does not need a proposal. They need to know.

A free scoping conversation would have produced an opinion, and an opinion is not enough to justify walking away from your own idea. Four weeks of paid work produced evidence: real data sources examined, ingestion and deduplication tested, refresh rates measured, coverage and quality counted rather than estimated. That is the only kind of answer that can carry a decision this size.

Bundling the brand identity and a working prototype alongside the feasibility study was deliberate. If the answer had been yes they would have finished the four weeks ready to move rather than ready to start planning. Because the answer was no, they still finished holding something real, which is what makes a difficult conclusion possible to accept rather than merely correct.

Putting the retrospective in week four made the decision the deliverable. The engagement was not scoped to end with a recommendation to proceed. It was scoped to end with a decision either way, which is the only structure under which a no is a successful outcome rather than a failed sale.