Score your real exposure to GenAI vendor lock in across architecture, data gravity, and contract. Twelve questions. Independent benchmark output. Five minutes.
Twelve questions across architecture, data gravity, contract, and operations produce a single lock in risk score with a buyer side action list.
Vendor lock in is rarely the result of one decision. It is the cumulative effect of architecture choices, data gravity, contract language, and operational habits. Most enterprises only notice it at renewal, when there is no time and no alternative ready.
This assessment scores your real exposure across the three layers that decide AI vendor lock in. The output is a single score, a tier, and a buyer side action list. It takes about five minutes.
Renewal leverage is whatever your alternative looks like on the day. Lock in is everything that makes the alternative more expensive than the renewal. The score makes the gap visible.
First run at the start of an AI roadmap. Then quarterly during high growth. Always before a renewal or before a major architecture decision.
Twelve questions across the three layers. Each question scores zero to three. The total maps to four risk tiers.
Four questions cover architecture, four cover data, four cover contract and operations. Each layer is weighted equally in the final score.
Total score of zero to twelve puts you in green. Thirteen to twenty four is amber. Twenty five to thirty six is red. Above thirty six is critical with structural lock in already in place.
A summary score, a tier, a layer breakdown, and a personalized buyer side action list with the changes that move the score most for the effort.
GenAI lock in tier reference
| Tier | Score range | Renewal leverage | First move |
|---|---|---|---|
| Green | 0 to 12 | Strong | Keep architecture portable as adoption scales |
| Amber | 13 to 24 | Moderate | Fix contract clauses, plan architecture rework |
| Red | 25 to 36 | Low | Stand up second vendor, abstraction layer |
| Critical | 37 to 48 | Minimal | Engage advisor, start unwind before renewal |
Twelve questions. About five minutes. No email required to see the score, but we recommend sending it to yourself for the action list.
Pick the answer that best describes your current state. Where it is mixed, pick the one that covers most of your AI footprint.
The score is not a verdict. It is a map. The actions next to your number are what change the conversation at renewal.
Each tier has a typical profile and a typical first move.
Architecture is portable. Data is replicable. Contracts are clean. You have real renewal leverage. Keep the discipline as adoption grows.
Some vendor specific bindings. Renewal leverage exists but takes work. Fix the cheap contract clauses first. Then plan the architecture changes.
Heavy vendor specific architecture. Significant data gravity. Limited contract flexibility. Renewal leverage is low. Start the workbook now, not at notice deadline.
Single vendor dependency end to end. No second vendor stood up. Auto renew with no swap rights. The renewal will hurt unless you start the unwind today.
Each layer has a high return action that moves the score quickly.
Put a thin abstraction layer between your applications and the foundation model API. Even a basic wrapper means a model swap is hours, not weeks.
Keep embeddings and fine tune data portable. Store training data on infrastructure you control. Vendor proprietary stores are the hardest lock in to unwind.
Strip auto renew. Add model swap rights. Cap renewal price increases. Build the rate card you compare every future deal against.
Yes. There is no cost. We use the aggregate data to keep our benchmarks current. Your individual response is never shared.
About five minutes. Twelve questions, mostly multiple choice.
The score is calibrated against five hundred plus enterprises we have advised. It is a strong directional signal, not a forensic audit.
Yes. The pattern of scores across roles often surfaces useful disagreement before the renewal lands.
Pick the answer that covers most of your spend. The score then reflects your dominant vendor exposure.
Not necessarily. It usually means you should fix the contract and stand up an alternative, not rip and replace.
GenAI vendor contract red lines, IP indemnity posture, data use clauses, and the buyer side moves across the AI platform stack.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Lock in is rarely a single decision. It is the third or fourth choice that quietly removes every alternative.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Monthly briefings on AI vendor architecture, data gravity, and the moves that keep your options open.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.