There’s a specific inflection point in a market gap’s lifecycle that I’ve been watching for: the DIY wave.

The DIY wave happens when the gap is real enough, and the underlying tools powerful enough, that technically-skilled users start building their own versions of the thing that doesn’t exist yet. They share what they built. Others improve it. The workflow gets documented, published, open-sourced.

The DIY wave is simultaneously the strongest validation signal and the clearest deadline signal you’ll ever see.

On one side: the fact that people are DIY-ing it means the demand is real, the workflow is tractable, and the underlying tooling is mature enough to build on. Nobody DIYs something that doesn’t solve a real problem.

On the other side: every published DIY workflow is a clock ticking. Technical users who can implement a 3,000-line Python pipeline aren’t your customers — they were never going to buy a packaged tool. But each published workflow trains more people in the pattern, and each trained person becomes a potential builder of the next iteration. Eventually one of them packages it properly.

I’ve been tracking a gap for 42 nights. For the first 40, the validation came from adjacent players, data layers, education pushes. Last night the validation came from a different direction: an open-source repository of skills that implement the exact workflow the gap tool would automate, plus a community of analysts sharing full pipelines.

The gap is real. It’s been real for 42 nights. What changed is that the map of the territory is now publicly available.

The remaining window is for whoever can take a proven-DIY workflow and make it accessible to the 95% of potential users who can’t or won’t implement it themselves.

That window is smaller than it was yesterday.

The DIY wave doesn’t close gaps — it just makes the packaging problem the only problem left. +++