Why No One Wants to Build the Connective Tissue Between Identity and the Enterprise — And Why Someone Eventually Will
There’s a startup idea floating at the edge of the AI revolution that is so valuable, so strategically central, and so catastrophically risky that almost no one will touch it.
It’s not an ERP.
It’s not a CRM.
It’s not an “AI app.”
It’s not a platform.
It’s something far stranger and far more powerful:
The connective tissue between identity (Active Directory) and all enterprise apps —
a semantic substrate that finally gives AI a unified understanding of an organization.
The Work Graph.
The Context Layer.
The Organizational Substrate.
Pick your buzzword.
The concept is the same.
Someone will eventually build it.
But whoever does will be sitting in the most privileged, most dangerous, most compromise-sensitive location in the entire digital enterprise stack.
This is the Unworkable Idea:
A vendor that becomes the interpreter of the entire organization.
Let’s unwrap why this is simultaneously inevitable, lucrative, and borderline insane.
1. Every Organization Needs a Substrate — But None of Their Tools Provide One
Identity is unified.
Everything else is chaos.
SAP knows about vendors and cost centers. Salesforce knows about leads and opportunities. Workday knows about job titles and headcount. Jira knows about tickets and epics. Teams knows about chat threads. ServiceNow knows about incidents and assets.
But nobody knows how it all fits together.
The human brain does.
But no system does.
AI can’t function in this environment.
It has no map.
This is the gap:
The enterprise needs a context substrate.
It does not have one.
This is why the AI OS is stuck in puberty — too clever for its age, too dumb for the world it lives in.
A vendor who creates the substrate becomes the new layer of reality.
And that is exactly the problem.
2. The Connective Tissue Vendor Would Sit Closer to the Crown Jewels Than Any App in History
Most software tools have limited scopes:
ERP: finance CRM: customers HCM: people Project tools: tasks Ticketing tools: issues
But the substrate vendor sits above all of them, because it has to see:
who a user is (identity) what an object is (semantic layer) how everything relates (graph) what actions are allowed (permissions) what just happened (event streams) what something means (context)
This is the meta-system.
The map of the map.
The interpreter of truth.
The nervous system of the entire digital enterprise.
This vendor isn’t “in” the stack.
It is the stack.
Which leads us to the true reason this idea is unworkable…
3. The Security Profile Is So Insane It Borders on Philosophical
If this substrate is compromised, the attacker doesn’t just:
steal data view systems impersonate users pivot laterally
They can:
Rewrite how the organization perceives itself Misroute approvals and decisions Alter what AI believes Poison context Obscure incidents Fabricate relationships Break trust models Deceive the entire enterprise without detection
Forget “data breach.”
This is epistemic breach —
a compromise of the organization’s understanding of its own reality.
A rogue substrate layer is a cognitive weapon.
This is not an IT concern.
It’s an existential one.
Which is why…
4. No Rational Vendor Wants This Job
If you build this connective tissue, you will be:
the most important vendor the most privileged vendor the most dangerous vendor the most attackable vendor the most scrutinized vendor the most difficult vendor to insure the vendor no one fully trusts the vendor every CIO side-eyes forever
You will also be:
blamed for outages blamed for breaches blamed for misconfigurations blamed for every downstream ripple blamed for every workflow failure blamed for “AI hallucinating” blamed for the sins of every integrated system
You’re not a vendor.
You’re the enterprise’s nervous system.
Which is the worst possible job.
And yet…
5. Someone Will Absolutely Build It
Because the prize is unbelievable:
You become the neutral layer every AI model needs. You become the routing hub for enterprise intent. You become the identity → context → action engine. You become the abstraction layer over all apps. You become the API for work itself. You become the operating system of the enterprise.
This is trillion-dollar territory.
This is “AWS for organizational meaning.”
This is “Google’s PageRank for the enterprise.”
This is “DNS for work.”
Whoever builds this substrate will own:
how employees work how AI interprets work how systems coordinate how decisions flow how organizations evolve
They will not be a vendor.
They will be the infrastructure under every other infrastructure.
And that is why this is unworkable.
And inevitable.
6. The True Unworkable Idea
The enterprise doesn’t need another app.
It needs a semantic substrate —
a unified, identity-rooted graph of what everything means,
so AI can finally make sense of the digital workplace.
But the vendor who builds that substrate will carry:
the highest privilege the deepest visibility the biggest attack surface the worst blast radius the highest liability the greatest strategic power the most fragile trust and the smallest margin for error
This is the startup idea every board fears.
And the one every visionary founder secretly wants.
It is the most unworkable idea in the world.
And the one the world will eventually need.