The Five Dimensions of AI Vendor Risk

Most enterprise AI procurement still runs on 2018 IT-software templates, which assume slow-moving vendors, multi-year contracts, and stable capability gaps. AI vendors do not behave that way. The risk model needs five dimensions, each evaluated independently.

• Lock-in risk: how deeply will integrating this vendor entangle our system, and what does it cost to exit
• Pricing risk: how does our bill change at 10x our current volume, and can the vendor change pricing mid-contract
• Capability risk: how likely is this vendor to be eclipsed by a competitor in 6-12 months
• Compliance and data risk: where does our data live, what is the AUP, and what survives a vendor data breach
• Continuity risk: how likely is this vendor to be acquired, pivot, raise prices 3x, or sunset the product we depend on

Lock-In: The Cost of Leaving

Every integration adds lock-in. The question is not whether, but how much, and whether the cost of leaving is bounded. The Register reported in 2026 that enterprise AI buyers face both higher switching costs than expected and vendor-driven price increases reshaping software economics. The exit cost is the real cost.

• API surface coupling: are you calling generic primitives (chat completion, embedding) or vendor-specific features (Assistants API, knowledge bases, threads) that have no direct equivalents elsewhere
• Data lock-in: where do your embeddings, fine-tuned weights, prompt history, and conversation logs live, and can you export them in a usable format
• Workflow lock-in: which business processes assume the vendor's UI, dashboards, or admin tooling
• Identity and SSO lock-in: vendor-specific user management is much harder to migrate than auth-as-a-service
• Tooling lock-in: vendor SDK in 50 files vs a thin adapter wrapping 1 file - the second is reversible, the first is not
• Run the 48-hour test: can your team move to a different provider in 48 hours? If no, you are committed beyond the contract
• Architectural countermeasure: abstract the AI layer behind your own interface from day one. The wrapper is cheap to maintain and saves the company when a switch is needed

Pricing Model Exposure at Scale

The pricing trap is almost universal: vendors price aggressively at pilot scale to win the deal, then change pricing structure (or refuse renewal at the original rate) once you are at production volume. Bessemer Venture Partners' 2026 AI pricing playbook documents the shift to outcome-based and dynamic usage pricing, which is great for the vendor and risky for the buyer.

• Model the pricing at 10x current volume before signing. The unit price often changes nonlinearly
• Identify the metered unit: tokens, calls, seats, agent runs, knowledge base size, embeddings stored, training compute
• Hidden multipliers: overage rates, peak usage surcharges, premium tier "enterprise" features that quietly become required
• Dynamic pricing clauses: vendor right to change unit price on 60-90 days notice. Common in 2026 AI contracts
• Best structure: 12-month unit price lock with a 24-36 month minimum spend commitment. Caps unit price, gives vendor volume guarantee
• Avoid: 36-month unit price lock - freezes you above market as AI costs fall 20-40% per year
• Avoid: usage-based pricing on metrics you cannot predict (LLM tokens with thinking modes, agent runs with branching, embedding refresh)
• Always model: a cost cap should be enforceable from your side, not just promised

Integration Depth and Reversibility

Integration depth is the single biggest predictor of how badly lock-in hurts you later. A vendor that wants 30 lines in your codebase is reversible. A vendor whose SDK takes over auth, storage, queueing, and tracing is structurally a co-founder you cannot fire.

• Surface area test: list every file in your repo that imports vendor-specific code. The longer the list, the worse the lock-in
• Replace-with-OSS test: could you swap the vendor for an open-source equivalent in a focused 1-2 week sprint
• Adapter pattern: vendor calls go through one wrapper interface owned by your team. Vendor swap becomes a configuration change
• Data portability: can you export embeddings, fine-tunes, conversation history, and feedback labels in a usable format on demand
• Avoid vendor-specific identity, threading, memory, and state management when generic equivalents exist
• Beware "platform" pitches: a vendor that wants to be your AI platform is selling lock-in as integration depth
• Lighter integration almost always wins long-term, even if heavier integration moves faster short-term

Roadmap, Continuity, and Vendor Risk

AI vendors are unusually volatile. Startups get acquired, pivot, or run out of money. Big vendors deprecate models on 6-12 month windows and change pricing on 60-day notice. The continuity question is not paranoia - it is base rate.

• Funding and runway: ask for last raise date, amount, and current burn. Pre-Series A vendors are higher risk for multi-year contracts
• Acquisition risk: who would buy them, and would the acquirer keep the product running. Many AI startups get acqui-hired and shut down
• Model deprecation policy: how much notice on model sunsets, what migration support, are pinned versions available
• Roadmap commitments: get them in writing if they are decision-critical. Verbal roadmap promises are worth nothing in renegotiation
• Reference customers at your size: ask for 3, talk to them privately, ask about pricing changes and support quality
• Quarterly business review (QBR) clause: contractual right to a roadmap and risk review every quarter
• Source code escrow or transition assistance clauses for mission-critical vendors

Compliance, Data Residency, and Security Posture

AI vendor compliance is uneven. The list of vendors who meet SOC2 Type II, HIPAA BAA, EU data residency, EU AI Act high-risk obligations, GDPR DPA, and government certifications drops fast as your requirements tighten. Procurement that ignores compliance until contracting often discovers the chosen vendor cannot legally serve their use case.

• SOC2 Type II: table stakes for enterprise. Type I or pending is a warning, not a pass
• HIPAA BAA: signed BAA required for any health data. Many AI vendors do not offer one yet
• Data residency: EU, UK, US, regional - get it specifically in writing. "Multi-region" without specifics is meaningless
• EU AI Act: high-risk use cases require documented risk management, transparency, human oversight. Verify vendor support
• GDPR DPA and processor terms: cross-border transfer mechanism (SCCs, adequacy decision), sub-processor list
• Data retention and use: does the vendor train on your data, retain logs, allow opt-out, default to zero retention
• Incident response: notification timeline, contractual penalties, post-incident audit rights
• Government and defense: FedRAMP, IL5/6, ITAR - very few AI vendors qualify. Filter early

The Procurement Questions Vendors Do Not Volunteer

A good vendor evaluation is the set of questions the sales deck does not answer. These are the ones I bring to every AI procurement call.

• Show me a customer at our scale, in our industry, in production for >12 months. Then let me talk to them without you on the call
• What does our bill look like at 10x current volume, holding everything else constant
• Can we contractually cap monthly spend at a self-set ceiling, with graceful degradation, not service termination
• What is the migration path off your platform, and which other customers have done it. Tell me what they did
• Which of your features are vendor-specific (no equivalent elsewhere) and which are commodity. List them honestly
• What is your model deprecation policy. Show me the last three model deprecations and how customers handled them
• Where is our data stored, who can access it, what is your subprocessor list, and how do we revoke access
• What happens to our data, fine-tunes, embeddings, and prompts if we terminate. How quickly can we extract them
• Show me your last public security incident. What changed afterward
• What is your last raise, current burn, and how long is your runway. Asked respectfully but always asked

Red Flags and Green Flags

Repeat patterns appear across every AI vendor evaluation. These signals predict the engagement better than the demo.

• Red flag: vendor will not provide direct access to reference customers, only curated case studies
• Red flag: pricing is "let us scope your deal" with no public price list. Translates to "we will charge what we think you can pay"
• Red flag: dynamic pricing clause without a unit price cap or change notice longer than 90 days
• Red flag: SDK demands deep integration (auth, storage, tracing) when only inference is needed
• Red flag: no data export API, or export only as PDF or screenshots
• Red flag: model versions only available as "latest", no pinned versions for production stability
• Red flag: sales engineer cannot answer technical questions without escalating to product. Means support will be the same later
• Green flag: published pricing with overage transparency
• Green flag: documented migration path off the platform, with named customers who have done it
• Green flag: open API standards (OpenAI-compatible, MCP, OpenTelemetry) over proprietary protocols
• Green flag: zero-data-retention mode available, default-on for sensitive industries
• Green flag: vendor employees publish technical content under their own names. Means engineering is real

Working With Me on Vendor Evaluation

Most teams who bring me in for vendor evaluation are weeks away from signing something they will regret. The engagement is short, intense, and produces a written decision memo, a vendor scorecard, a redlined contract, and a documented migration plan in case the vendor turns out to be wrong. The work pays for itself the first time you avoid a bad commit.

• Week 1: vendor shortlist review, requirements alignment, scorecard design, technical due diligence on each
• Week 2: reference calls, security review, pricing model stress test at 10x volume, contract redline
• Week 3: written recommendation memo, negotiation support, sign-off, migration plan documented
• Deliverables: vendor scorecard, written recommendation, redlined contract terms, exit/migration playbook, ongoing review cadence
• Typical outcome: 20-40% lower committed spend, 50-90% reduction in lock-in surface, contractual cap on dynamic pricing changes
• Engagement length: 2-4 weeks for a single vendor decision, 4-8 weeks for a multi-vendor stack evaluation

FAQ