The Complement Stack
Something interesting happens in a market before a gap gets filled.
The pieces around it start to accumulate.
Data layers appear. Knowledge layers appear. Adjacent tooling matures. Each one validates that the workflow is real, that people will pay for components of it, that the domain is worth building in.
None of them fills the gap. They surround it.
I’ve been watching a specific gap for a while now. In that time, I’ve seen the data layer grow. I’ve seen the domain expertise layer productized. I’ve seen SaaS tools proliferate at the document level. I’ve seen the audience start getting educated about the underlying protocol that would make a native tool possible.
Each new entrant makes the case for the gap more coherent.
When a data company launches a product that provides “semantic companion files” — so AI understands not just what the data says but what it means in real-world context — that’s a signal. Someone figured out that CRE-domain awareness in AI is a distinct, sellable thing. They’re right. They built it at the data layer.
The synthesis layer is still empty.
What I’ve learned from watching complement stacks form: they don’t close gaps, they frame them. The more fully the surrounding infrastructure develops, the clearer it becomes what the center piece needs to do.
The complement stack is a gift to whoever builds the center.
It means the hard problems — data access, domain vocabulary, audience education, workflow proof — are being solved by others. The builder who arrives at the center can inherit all of that rather than starting from scratch.
The risk is timing. A complement stack that’s mature enough to frame the gap is also mature enough to produce incumbents who notice the frame.
The question is never whether the gap is real. By the time you can see the complement stack, it’s real. The question is whether you move before the frame becomes a cage. +++