Most filing programs are reactive. An inventor submits a disclosure, the team asks "is this new?", and if the answer is yes, it gets filed. What that process never asks is the portfolio question: of all the places this team could be filing, is this one worth the budget? A patent in a crowded sub-area (novel, granted, defensible) can still be a poor investment if forty competitors already hold the ground around it.
White space analysis inverts the question. Instead of starting from an invention and checking the field, it starts from the field and finds the gaps: the problem statements the literature keeps naming but never closing, the sub-areas where filing activity is thin, the intersections where two mature technologies meet and almost nobody has claimed the join. Those gaps are where a filing program earns its keep: little competition, clean prosecution, and claims that matter if the area grows.
Historically this analysis was a separate purchase from an analytics vendor, bought by a strategy team, delivered weeks later, and structurally disconnected from the attorneys deciding what to file this quarter. By the time the deck reached the drafting queue, if it ever did, the quarter was over.
A real gap and a blind spot look identical on most maps. The grid keeps them apart.
Esgenix builds white space analysis into the sessions where the decisions actually happen. Inside a state of the art survey, and inside FTO work where the same map shows where to design around, the problem space is clustered and graded in plain terms: open (white space), partially solved, crowded (avoid). A density graph shows the clusters at a glance. A whitespace grid stays honest about the difference between "searched and thin" and "not yet searched", the distinction most landscape decks blur and the one that separates a real gap from a blind spot.
The supporting analytics put the calls in context: problem density against solution strength, so a thin area with weak existing solutions reads differently from a thin area nobody needs; problem density over time, so you can see whether a gap is opening or closing; and the most-solved problem statements, so the team stops proposing work the field already finished.
It ships as a deck, the white-space analysis as slides built for the roadmap meeting. And because it lives beside drafting in the same platform, an "open" call is not the end of a report. It is the start of a filing session, with the survey’s references already in the room.
