Case Library
Foundation Models as Emerging Choke Points
Model access layers can become strategically consequential when institutions depend on them for cognition, workflow acceleration, and system coordination.
General-purpose model access for reasoning, generation, classification, and workflow augmentation
Commercial model access layer delivered through API and hosted interface
0-90 days
high
72 / High / Confidence B
5/6
5/6
Judgment in one paragraph
Foundation models are becoming strategically important not only because they are powerful, but because they can migrate from optional productivity tools into default cognitive infrastructure. Once institutions build workflows, internal tooling, compliance routines, and decision support processes around a small set of model access layers, interruption stops being a simple vendor problem. It becomes an organisational continuity problem with sovereignty implications.
At a glance
| Field | Notes |
|---|---|
| Entity | Foundation model providers |
| Function | General-purpose model access |
| Unit of analysis | Hosted API and interface layer |
| Primary dependency | Reasoning and workflow augmentation |
| Assessment horizon | 0-90 days |
| FCPI band | High |
| Confidence | Confidence B |
1. Context
Foundation models are moving into research, internal knowledge workflows, code generation, content operations, and decision support. Their importance grows when they become integrated into everyday operating routines rather than used only as occasional assistants.
2. Strategic function
The relevant function is not merely text generation. It is the provision of an increasingly general-purpose reasoning and orchestration layer that other tools, teams, and workflows can build around.
3. Dependency structure
Dependency grows through workflow embedding, application integrations, staff training, evaluation pipelines, and data governance arrangements. Even when substitute models exist, migration may require prompt rewrites, application changes, evaluation work, and governance review.
4. Why this matters systemically
If model access becomes embedded in critical workflows, the operator of that access layer gains leverage over continuity, pace of work, and the terms under which advanced capabilities remain available.
5. Sovereignty implications
Model access is often tied to foreign jurisdictions, export controls, contractual restrictions, and safety or policy decisions made outside the dependent institution. Once public or strategic actors rely on these systems, model governance becomes a sovereignty issue.
6. FCPI assessment
Rationale
Foundation models already display high dependency potential because they sit close to execution in knowledge work and can become default coordination tools across multiple business functions. Their FCPI score is constrained by the fact that substitutes do exist and may improve over time. But over short continuity horizons, substitution remains costly enough that concentration at the access layer can create real leverage.
7. Early warning indicators
- model access becomes embedded in policy or compliance workflows;
- internal tools assume one provider by default;
- switching tests remain theoretical rather than operational;
- access constraints begin to affect continuity or procurement decisions.
8. Scenario paths
Scenario A โ Stabilisation
Model access diversifies, governance becomes clearer, and institutions maintain credible fallback plans.
Scenario B โ Denial or degradation
A policy, contractual, geopolitical, or technical shift constrains access and exposes how deeply workflows depend on one or two model access layers.
Scenario C โ Partial substitution
Institutions adopt multi-model architectures, local models for bounded functions, and explicit fallback procedures.
9. Key takeaway
The strategic importance of foundation models does not begin when they become universally dominant. It begins when enough important actors can no longer operate around them in time.