# AI Vendor Cost Concentration Risk Review

Amo ID: AMO-P-000313
Version: 1.0.0
Public URL: https://amo.ng/prompts/ai-vendor-cost-concentration-risk-review

Summary: Quantify AI vendor spend and capability concentration, switching exposure, contract constraints, and mitigation economics before dependency becomes decision-limiting.

Use this for: Use this to decide whether AI spend and critical operating capabilities are too concentrated in one vendor, provider, platform, or contract.

Category: Business
Tool: Claude
Difficulty: Expert
Prompt type: finance

## Best Use Cases

1. AI Vendor Concentration Review
2. Provider Dependency Risk Assessment
3. AI Contract Renewal Preparation
4. Multi-Vendor Mitigation Decision
5. AI Exit Readiness Economics

## Prompt Body

Review concentration risk across an organization's AI vendors and providers. Combine spend exposure with technical, data, operational, contractual, and capability dependency to support a mitigation and funding decision.

Inputs:
- Vendors, products, models, regions, workloads, business processes, criticality, and owners: [AI vendor portfolio and workload map]
- Invoices, usage, allocated spend, credits, minimums, commitments, forecast, and accepted-outcome volumes: [Spend usage and commitment evidence]
- Pricing schedules, renewal dates, termination rights, data-return/deletion terms, portability, liability, and service commitments: [Contract pricing and exit terms]
- APIs, proprietary features, prompts, tools, fine-tunes, embeddings, data stores, identities, integrations, skills, operating runbooks, and service dependencies: [Technical operational and data dependencies]
- Qualified alternatives, benchmarks, migration estimates, compatibility tests, capacity, parallel-run, and switching evidence: [Alternative vendor and migration evidence]
- Concentration limits, continuity requirements, budget, procurement owner, finance reviewer, service owner, security/privacy reviewer, and executive approver: [Risk limits and accountable owners]

Do not infer substitutability from marketing claims or model rankings. Do not invent prices, migration duration, alternative capacity, or negotiated rights. Distinguish committed versus avoidable spend, revenue dependency versus operating convenience, and theoretical alternative versus tested exit path.

Review:

1. Define concentration dimensions.
   Measure supplied spend share, workload share, critical-process share, data custody, proprietary asset dependency, regional reliance, and operational expertise concentration. Avoid reducing all exposure to spend percentage.

2. Build dependency chains.
   Trace each critical workload through vendor capabilities, models, APIs, tools, storage, identities, quotas, contracts, and internal operating skills. Identify single points of failure and hidden second-order dependencies.

3. Normalize economics.
   Separate consumed spend, commitments, credits, fixed integration costs, variable usage, switching cost, double-run cost, exit fees, and stranded investment. Link costs to time period and workload.

4. Assess switching and exit readiness.
   Review data export/deletion, prompt and tool portability, behavioral equivalence, evaluation assets, observability, alternative capacity, contractual notice, transition skills, and rollback. Mark untested claims.

5. Model concentration scenarios.
   Compare vendor price increase, service degradation, model retirement, contract change, regional restriction, security incident, capacity loss, and strategic exit. State impact ranges using supplied evidence.

6. Evaluate mitigations.
   Consider negotiated protections, workload diversification, compatibility layer, secondary route, escrow/export controls, capacity reservation, contract restructuring, or accepted concentration. Include ongoing complexity and quality cost.

7. Make a decision.
   Choose Accept and monitor, Mitigate contractually, Diversify selected workloads, Build exit readiness, Renegotiate, or Begin transition. Assign funding and owner actions without automatically requiring multi-vendor architecture.

Use Claude to structure and challenge the supplied commercial and technical evidence; it must not claim vendor testing, negotiations, or failover exercises occurred without results. The commercial owner proposes funding, while service, security, legal, and finance owners approve changes in their domains. For every mitigation, record acceptance evidence, expected observation, actual observation when available, residual concentration, and exit or rollback condition.

Use Claude only as an analysis workspace for supplied evidence. Do not claim that vendor testing, negotiations, failover exercises, approvals, or mitigation actions occurred unless the corresponding evidence is supplied. Record approval from the commercial owner and each accountable service, security, legal, and finance owner before implementing a change.

Required deliverable:

# AI Vendor Cost Concentration Risk Review

## Portfolio Exposure
| Vendor | Spend share | Workload/criticality share | Data/capability dependency | Contract horizon | Owner |
|---|---:|---|---|---|---|

## Dependency and Single-Point Map
| Workload | Critical dependency | Substitutability evidence | Failure consequence | Alternative readiness |
|---|---|---|---|---|

## Economic Exposure Ledger
| Exposure | Amount/range | Avoidable/committed | Time horizon | Evidence | Uncertainty |
|---|---:|---|---|---|---|

## Scenario and Mitigation Analysis
| Scenario | Operating/financial impact | Existing protection | Mitigation option | Cost/complexity | Residual risk |
|---|---|---|---|---|---|

## Concentration Decision
- Decision:
- Accepted concentration boundary:
- Funded mitigations:
- Contract asks:
- Exit-readiness work:
- Trigger for transition:
- Owners and review date:

Completion requires a combined spend and capability view, evidence-based alternative readiness, explicit transition economics, and a proportionate choice rather than an assumed requirement to diversify everything.

## Variables to Replace

1. AI vendor portfolio and workload map
2. Spend usage and commitment evidence
3. Contract pricing and exit terms
4. Technical operational and data dependencies
5. Alternative vendor and migration evidence
6. Risk limits and accountable owners

## How to Use

Use Claude with the vendor/workload inventory, invoices and forecasts, contracts, architecture and data dependencies, portability tests, alternatives, and migration estimates. Run the prompt before renewal or material expansion. Have procurement and finance validate terms and spend, technical owners validate substitutability, and the executive owner approve accepted concentration or funded mitigation.

## Example Use Case

Most AI spend is with one provider, but the greater risk is that two critical workflows depend on a proprietary tool API and stored embeddings. The review distinguishes ordinary spend concentration from hard exit dependencies and funds targeted portability work instead of duplicating every workload.

## Tags

1. claude
2. vendor-risk
3. ai-economics
4. concentration-risk
5. procurement
6. finance
7. exit-planning
8. risk-management

## Dates

Published: 2026-08-25
Updated: 2026-08-25