---
id: "concept-the-enterprise-gap"
type: "concept"
source_timestamps: ["00:16:50", "00:17:40"]
tags: ["enterprise-software", "market-analysis", "go-to-market"]
related: ["entity-nemoclaw", "concept-the-now-what-problem"]
definition: "The failure of enterprise AI deployments to provide operational utility, as they focus entirely on security and infrastructure while ignoring the need for personalized agent operating instructions."
sources: ["s08-real-problem-agents"]
sourceVaultSlug: "s08-real-problem-agents"
originDay: 8
---
# The Enterprise Gap

## Definition

The failure of enterprise AI deployments to provide operational utility, as they focus entirely on security and infrastructure while ignoring the need for personalized agent operating instructions.

## Description

Companies like Nvidia (with [[entity-nemoclaw]]) have successfully built enterprise wrappers around open-source agents, solving critical corporate needs:
- Security and privacy guardrails (OpenShell)
- Sandboxed execution environments
- Advanced model output routing (NemoTron)
- Compliance and audit

**However**, these wrappers only solve the IT and security problems. They completely punt on the operational problem.

## The 9,995 problem

When an enterprise rolls out a secure agent to 10,000 employees, **9,995 of them will not know what to do with it**. The enterprise wrapper does not provide the specific operating instructions (the [[concept-expertise-elicitation|tacit knowledge extraction]]) required to make the agent useful for a specific employee's daily workflows.

## The unresolved question

Will IT departments, HR, or AI vendors take responsibility for generating these personalized operating instructions? See [[question-enterprise-wrapper-utility]].

## Counter-perspective

Vendors like Riskonnect argue cloud wrappers with auto-validation reduce 'Now What?' via *pre-configured* fraud patterns in narrow domains — solving operational gaps that the speaker attributes to user elicitation. This works for highly standardized verticals (claims processing) but does not generalize to senior knowledge workers with idiosyncratic workflows.

## Related
- [[concept-the-now-what-problem]]
- [[entity-jensen-huang-d8]]
