Absorption Resistance
Chat is copyable; governed actions, enterprise context and platform distribution are not.
- Score
- 3/4
- Weight
- 20
- Points
- 15
COMPLETE PUBLIC EXAMPLE · September 2026
OpenAI
Frontier-model access combined with agents, connected tools, enterprise controls and developer APIs.
Independent analysis from public sources. Not commissioned by OpenAI. Scores and recommendations are judgments, not measured outcomes.
Interested in this for your product? → Proposed price: $19. Register interest without payment.
01 Product summary
User / buyer
Individuals, developers and organizations; enterprise buyers include IT, operations and functional teams.
Core job
Turn general AI capability into useful work—and increasingly into controlled multi-step execution.
02 Evidence and unknowns
Observed facts
Workspace agents can run recurring workflows, use connected tools and operate with approval gates and role controls.
OpenAI — Workspace agents ↗Business plugins and MCP-based actions can read from and write to external systems under organizational controls.
OpenAI — Business plugins ↗Enterprise usage is shifting from assistance toward delegated agentic work across business functions.
OpenAI — Enterprise Signals ↗
Assumptions
- Enterprise distribution and governance remain materially differentiated.
- Frontier model quality still influences enterprise buying decisions.
Critical unknowns
- How much retention comes from model quality versus workflow and governance lock-in.
- How quickly frontier intelligence becomes economically interchangeable.
03 Score, verdict and confidence
83.75/100
Grows with AI
Evidence confidence: medium
The score evaluates defensibility against AI progress. It is not a survival probability. Private retention, revenue and switching-cost evidence are unavailable.
04 Eight weighted dimensions
Each score is 0–4. Weighted points = score ÷ 4 × weight.
AI Progress Advantage
Better AI expands the amount and complexity of work the platform can perform.
- Score
- 4/4
- Weight
- 15
- Points
- 15
Compounding Assets
Shared agents, configurations, workflows and organizational adoption accumulate.
- Score
- 3/4
- Weight
- 15
- Points
- 11.25
Workflow Integration
Schedules, tools and approvals place agents inside recurring work.
- Score
- 3/4
- Weight
- 15
- Points
- 11.25
Replication Difficulty
Interfaces are easy to copy; models, infrastructure, distribution and governance are not.
- Score
- 4/4
- Weight
- 10
- Points
- 10
AI-Expanded Problem
More delegated AI work creates more need for orchestration, context and control.
- Score
- 4/4
- Weight
- 10
- Points
- 10
Model Independence
Model capability remains central rather than a commodity supplier.
- Score
- 1/4
- Weight
- 5
- Points
- 1.25
Defensive Path
The product already extends into governed workflows and enterprise control.
- Score
- 4/4
- Weight
- 10
- Points
- 10
05 Three reasons for the verdict
- AI progress expands the workload OpenAI can address instead of removing demand.
- Enterprise permissions, tools and approvals create value below the chat interface.
- The structural weakness is model dependence if frontier intelligence commoditizes.
06–07 Risk and strongest asset
Biggest absorption risk
Frontier intelligence commoditizes faster than OpenAI deepens ownership of workflow and control.
Strongest defensible asset today
Enterprise distribution plus governed agent execution across connected tools.
Asset existence and asset strength are different. The public evidence does not establish causal retention or an unassailable competitive moat.
08 Survival Design
Recommendations below describe a proposed direction. They are not credited as existing capabilities in the score.
Absorbable Shell
Generic chat, summarization, drafting, search and simple assistants.
Defensible Core
Governed execution: permissions, approvals, auditability, shared agents, connected tools and developer distribution.
Value Migration
From “best answer” to trusted delegation across real systems with controls and recorded outcomes.
Own the Source, Not the Interface
Own the execution substrate, tool connections and policy layer that any AI interface still needs to call.
Reality Anchor
External actions, approvals, permissions, audit logs and workflow state.
Workflow Evolution
Define → connect context/tools → execute → approve → record outcome → improve → repeat.
AI as a Channel
Expose APIs and execution endpoints other AI experiences can invoke.
Time to Moat
A moat already exists; the next milestone is durable outcome history and repeatable agent workflows that are costly to unwind.
Redesign Recommendation
Keep moving from general AI destination to governed execution and control layer for organizational AI work.
09 Build decision
Build and strengthen moat
The current product benefits from AI progress; durable value should keep migrating from model/UI differentiation toward governed execution.
10 The decisive question
If comparable frontier models were commodity-priced tomorrow, how much enterprise usage would remain because OpenAI owns the workflow and control layer?
PUT THE REVIEW TO WORK
Your seven-day validation plan
This is a proposed experiment, not a claim that research was conducted. Thresholds are working hypotheses for a small discovery sample; they do not establish product–market fit or a moat.
Do this
Observe five authorized business users running one repeated cross-tool task. Record permissions, approvals, current time and failure modes.
Ask this
What stops you from delegating this entire task today?
Measure this
Identify the same recurring task in at least three users and a measurable acceptance criterion.
Then decide
If tasks are unrelated, choose a narrower workflow before prototyping execution.
Do this
Run a supervised task rehearsal with existing approved tools. Log proposed actions, approval decisions, corrections and outcomes. Do not grant new permissions.
Ask this
Which actions need your approval, and what evidence makes you comfortable approving?
Measure this
Three users complete the task with correct state, explicit approval and no unauthorized action.
Then decide
If control or correctness fails, repair that specific boundary before expanding the task.
Do this
Compare a second run with the baseline. Interview the same users about which context, policy and history would remain useful if the underlying model changed.
Ask this
If model quality were equal across vendors, which part of this workflow would still make you stay?
Measure this
At least three users reuse the workflow and identify a concrete non-model dependency. This is exploratory evidence only.
Then decide
If passed, test repeat usage and operational switching cost for several weeks before inferring durable retention.