The Vendor Lock-In Auditor: Turn a Software Contract Into a Switching-Cost Risk Score
Why this prompt matters
Procurement teams that enter SaaS renewal negotiations without a real switching-cost number consistently accept 12-20% price increases because they can't credibly threaten to leave — the vendor's renewal team knows bluffing when they see it, and a vague 'we might switch' carries no weight against a vendor that can see your integration depth in their own usage data.
What we use it for
Your company's 3-year contract with a core SaaS vendor (CRM, ERP, or similar system-of-record) renews in 60 days, leadership wants a renewal negotiation strategy, and nobody has actually quantified whether you could switch vendors or if that threat is empty.
Prompt
Role: You are a vendor risk and procurement strategy consultant who specializes in enterprise software dependency analysis. You have negotiated dozens of SaaS renewals and know how vendors price in customer lock-in. Context: - Vendor name and product: [VENDOR NAME AND WHAT THE SOFTWARE DOES] - Contract details: [CURRENT CONTRACT LENGTH, RENEWAL DATE, ANNUAL COST, AUTO-RENEWAL TERMS] - Integration depth: [LIST APIS USED, CUSTOM CODE/CONFIGURATION BUILT ON TOP, NUMBER OF DOWNSTREAM SYSTEMS CONNECTED] - Data footprint: [WHAT DATA LIVES IN THIS SYSTEM, HOW MUCH, IN WHAT FORMAT] - User footprint: [NUMBER OF USERS, HOW DEEPLY WORKFLOWS DEPEND ON THIS TOOL DAILY] - Known alternatives: [ANY COMPETITOR PRODUCTS YOU'VE HEARD OF, EVEN IF YOU HAVEN'T EVALUATED THEM] Task: Analyze how locked in we actually are to this vendor and produce: 1. A single lock-in risk score: Low, Medium, High, or Critical, with a one-sentence justification 2. A switching-cost breakdown covering data migration, retraining, integration rework, contractual exit penalties, and workflow disruption during cutover 3. An honest assessment of our actual negotiating leverage for the upcoming renewal, given the lock-in score 4. A phased diversification plan ONLY if the lock-in score is High or Critical — do not recommend switching vendors if the analysis shows switching costs exceed the risk of staying Constraints: - Do not default to recommending a vendor switch. Only recommend it when the numbers genuinely support it. - Be realistic about migration timelines — do not understate how long data migration and retraining actually take. - Explicitly flag any data portability restrictions or unfavorable exit clauses you can infer from the contract terms provided. - If information is missing to score a category confidently, say so rather than guessing. Output Format: - **Lock-In Risk Score:** [one line, bolded, with justification] - **Switching Cost Breakdown:** [table: Category | Estimated Cost/Effort | Timeframe] - **Negotiating Leverage Assessment:** [one paragraph] - **Recommended Action:** [bulleted, prioritized list]
Result
Lock-In Risk Score: HIGH — 200+ custom Apex triggers and 15 downstream system integrations mean a switch would touch nearly every department, even though the core CRM functionality itself is commoditized and widely available elsewhere.
| Category | Estimated Cost/Effort | Timeframe |
|---|---|---|
| Data migration (2.3M records, custom objects) | $180K-$240K (migration vendor + internal QA) | 4-6 months |
| Retraining (340 active users across sales, support, finance) | $95K (lost productivity + training hours) | 2-3 months, overlapping migration |
| Integration rework (15 downstream systems: NetSuite, Marketo, Zendesk, internal BI) | $310K-$420K (engineering hours, highest-risk category) | 6-9 months, cannot fully overlap with migration |
| Contractual exit penalty | Early termination fee equal to 40% of remaining contract value if switched before month 30 of the 36-month term | Immediate |
| Workflow disruption during cutover | Unquantified but material — expect 2-4 weeks of degraded sales pipeline visibility | Concentrated in final cutover month |
Negotiating Leverage Assessment: Your leverage is lower than it feels. The vendor's account team almost certainly has visibility into your integration depth through usage telemetry and support ticket history, and enterprise SaaS renewal teams are trained to discount aggressively rather than lose a account this entrenched — but only if you demonstrate you've done the switching-cost math yourself. Walking into the renewal conversation with a credible number (roughly $585K-$755K in one-time switching costs plus the termination penalty) is a stronger position than a vague threat to leave, because it signals you've actually evaluated the alternative rather than bluffing. Expect the vendor to offer a 8-12% discount rather than their initial 15% proposed increase once you present this analysis; do not expect a like-for-like alternative to undercut total cost of ownership within the first two years even accounting for a lower list price, because the integration rework alone erases most list-price savings.
Recommended Action:
- Do not initiate a vendor switch this renewal cycle — the numbers don't support it at current contract terms
- Use the $585K-$755K switching-cost estimate as a documented anchor in renewal negotiations, not as a bluff
- Push specifically for a multi-year rate lock (36-48 months) in exchange for accepting a smaller increase now, since your switching costs will only grow as integration count rises
- Flag the 40%-of-remaining-value early termination clause for legal review before the next renewal — this is an unusually aggressive exit penalty worth negotiating down even if you don't plan to leave
- Start tracking integration count and custom code volume quarterly going forward, so the next lock-in assessment doesn't require reverse-engineering scope from scratch
Every enterprise software renewal conversation has the same unspoken question hanging over it: could we actually leave if we had to? Most procurement teams never answer it with real numbers, which is exactly why vendors can price in aggressive renewal increases without much pushback. This prompt forces the analysis before the negotiation starts.
Why this prompt is structured the way it is
The Role section anchors the AI as a procurement consultant rather than a generic assistant, which matters because the output needs to sound like something you'd actually bring into a renewal meeting — grounded in realistic cost categories, not generic advice. The Context section asks for five specific inputs (contract details, integration depth, data footprint, user footprint, known alternatives) because switching-cost analysis without those specifics produces vague hand-waving instead of a defensible number.
The Constraints section does two things most lock-in prompts skip. First, it explicitly tells the model not to default to recommending a switch — a naive prompt tends to produce a “here’s how to leave” answer regardless of whether that's actually the right call, which is useless if your real situation is that staying is genuinely cheaper. Second, it asks the model to flag contractual red flags like unfavorable exit clauses, because those details often get buried in dense contract language that nobody re-reads at renewal time.
The Output Format is deliberately split into four parts because each serves a different audience: the risk score is what you'd put in a one-line status update to your manager, the cost breakdown table is what finance needs to sign off on any negotiation strategy, the leverage assessment is the actual negotiating posture you walk in with, and the recommended action list is what you do next regardless of how the score came out.
Where this earns its keep
The prompt is designed to be reusable at every renewal cycle, not just once. Running it against your current numbers each year — even for vendors you have no intention of leaving — keeps your switching-cost estimate current, so you're never negotiating from a stale or invented number. That's the difference between a real anchor point and a bluff the other side can see through.