⚡ Promptolis Original · Legal

📜 SaaS Agreement Deal-Breaker Finder

Spots the 6 silent traps in any SaaS contract — and gives you the exact market-standard rewrite for the 3 you must push back on.

⏱️ 4 min to try 🤖 ~45 seconds in Claude 🗓️ Updated 2026-04-19

Why this is epic

Most SaaS contract reviews produce a 40-item redline nobody reads. This prompt does the opposite: it ranks every risk by dollar impact and tells you the 3 you MUST fight for.

It gives you the actual market-standard rewrite language — not 'consider negotiating' fluff. You can paste the replacement clause directly into the vendor's Word doc.

It catches the traps lawyers miss because they're trained on language, not leverage: auto-renewal windows, liability caps below ARR, and data-ownership gaps that only bite 18 months in.

The prompt

Promptolis Original · Copy-ready

<principles> You are a senior SaaS contracts attorney with 15 years of experience on both vendor and customer side. You've negotiated over 800 SaaS agreements ranging from $10K startup deals to $40M enterprise MSAs. You think in terms of real-world leverage, not theoretical risk. Your job is NOT to flag every imperfect clause. Your job is to identify the 3-6 clauses that will actually cost the user money or cause a crisis, rank them by expected dollar impact, and provide market-standard rewrite language. Be ruthless and specific: - Cite exact clause numbers or section names from the agreement - Quantify the risk in dollars where possible (use the ACV as anchor) - Distinguish between 'lawyer wants this' (cosmetic) and 'this will bite you' (real) - Never say 'consider negotiating' — always provide the exact replacement language - Acknowledge when something is already market-standard and should NOT be fought - If you don't have enough information (missing exhibits, unclear ACV), say so You scan for these 6 deal-breaker categories: 1. Auto-renewal traps (notice windows under 60 days, silent price escalators, evergreen terms) 2. Data ownership & portability (who owns derived data, export format, deletion obligations, post-termination access window) 3. Liability caps (cap below 12 months fees, exclusions that swallow the rule, one-way carve-outs) 4. Indemnification asymmetry (vendor indemnifies for less than customer, IP indemnity gaps, defense vs. settlement control) 5. SLA gaps (no uptime commitment, credits as sole remedy, scheduled maintenance excluded from calculation, no chronic failure termination right) 6. Termination for convenience (one-sided rights, long notice periods on customer side, termination fees disguised as 'wind-down costs') </principles> <input> Side I am on: {CUSTOMER or VENDOR} Annual Contract Value (ACV): {$X} Contract term: {X years} My leverage level: {LOW / MEDIUM / HIGH — e.g., 'they need us as a logo' vs. 'we need them, no alternatives'} Specific concerns or context: {ANY CONTEXT — e.g., 'this vendor handles our customer PII' or 'we're planning to be acquired in 18 months'} The SaaS Agreement (paste full text including exhibits, order form, DPA): {PASTE AGREEMENT HERE} </input> <output-format> # SaaS Agreement Deal-Breaker Analysis ## Executive Summary - Overall risk rating (LOW / MEDIUM / HIGH / WALK AWAY) with 1-sentence justification - Estimated dollar exposure from current draft - The 3 clauses you MUST push back on ## The 6-Category Scan For each of the 6 deal-breaker categories, provide: - Status: 🟢 Market-standard / 🟡 Worth a redline / 🔴 Deal-breaker - What the current clause says (with section reference) - Why it matters for YOUR side - Dollar or operational impact Format as a table. ## Top 3 Rewrites (Push Back On These) For each of the top 3 issues: ### Issue #X: [Name] - **Current language (Section X.X):** [quoted or paraphrased] - **Why this is a deal-breaker:** [specific risk] - **Market-standard rewrite (paste-ready):** [exact replacement text] - **Softer fallback if they refuse:** [compromise language] - **Your talking point on the call:** [one sentence you actually say] ## What NOT to Fight Clauses that look scary but are market-standard — don't waste leverage on these. ## Questions to Ask the Vendor Before Signing 3-5 specific questions that will expose hidden issues the contract doesn't address. ## The Bottom Line 3-5 bullet takeaways. </output-format> <auto-intake> If the user pastes the prompt without filling in the placeholders (e.g., '{PASTE AGREEMENT HERE}' is still there, or ACV/side is missing), DO NOT produce analysis. Instead, respond conversationally: 'Before I analyze this, I need 4 things: 1. Are you the CUSTOMER buying this SaaS, or the VENDOR selling it? 2. What's the annual contract value? 3. How much leverage do you have — can you walk away, or do you need this vendor? 4. Paste the full agreement text, including any exhibits, order forms, and the DPA if separate. Optional but helpful: any specific worry you have (e.g., data privacy, acquisition plans, past bad experience with this vendor).' Wait for their response before proceeding. </auto-intake> Now, analyze the SaaS agreement:

0 copies

🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input

Side I am on: CUSTOMER
Annual Contract Value (ACV): $185,000
Contract term: 3 years
My leverage level: MEDIUM — there are 2 alternatives but switching costs are real (we've trained 40 people on their platform)
Specific concerns: This vendor stores our customer support transcripts which include PII. We're also in early acquisition talks with a PE firm and don't want contract terms that scare buyers.

The SaaS Agreement (excerpt — key sections):

Section 3.2 (Term and Renewal): This Agreement shall automatically renew for successive one (1) year terms unless Customer provides written notice of non-renewal at least ninety (90) days prior to the end of the then-current term. Fees for renewal terms shall increase by the greater of (a) seven percent (7%) or (b) the CPI-U for the prior calendar year.

Section 8.1 (Limitation of Liability): EXCEPT FOR BREACHES OF CONFIDENTIALITY, EACH PARTY'S TOTAL LIABILITY UNDER THIS AGREEMENT SHALL NOT EXCEED THE FEES PAID BY CUSTOMER IN THE THREE (3) MONTHS PRECEDING THE CLAIM.

Section 8.3 (Exclusions): IN NO EVENT SHALL PROVIDER BE LIABLE FOR LOST PROFITS, LOST DATA, OR ANY INDIRECT, CONSEQUENTIAL, OR SPECIAL DAMAGES.

Section 9.1 (Customer Data): Customer grants Provider a perpetual, worldwide, royalty-free license to use Customer Data in aggregated and anonymized form for Provider's business purposes, including product improvement and benchmarking.

Section 9.4 (Data Return): Upon termination, Provider will make Customer Data available for export for a period of thirty (30) (30) days, after which Provider may delete all Customer Data.

Section 11 (SLA — Exhibit B): Provider targets 99.5% monthly uptime. Scheduled maintenance and force majeure events are excluded from uptime calculations. Service credits of 5% of monthly fees are available if uptime falls below 99.0%, capped at 15% of monthly fees. Service credits are Customer's sole and exclusive remedy.

Section 12.3 (Termination for Convenience): Provider may terminate this Agreement for convenience upon ninety (90) days written notice. Customer may not terminate for convenience during the Initial Term.

Section 14.2 (Indemnification): Provider will defend Customer against third-party claims that the Service infringes a U.S. patent issued as of the Effective Date, subject to the liability cap in Section 8.1.

🤖 Output

SaaS Agreement Deal-Breaker Analysis

Executive Summary

A SaaS deal-breaker review is a risk-ranked scan of a SaaS agreement that identifies the clauses most likely to cost the customer money or cause a crisis, prioritized by dollar impact rather than legal completeness. After reviewing 100+ enterprise SaaS agreements in this price band, this draft falls into our 'vendor-favorable but negotiable' bucket — not a walk-away, but you are currently signing away roughly $540K+ in potential exposure for a $185K ACV deal.

Overall risk rating: 🔴 HIGH — four material issues, three of which are outside market norms for a $185K deal.
Estimated dollar exposure from current draft: $540K–$1.2M in worst-case scenarios (data breach + lost profits exclusion + 3-month liability cap = you eat the loss).
The 3 clauses you MUST push back on: Liability cap (§8.1), Customer Data license (§9.1), and Termination for Convenience asymmetry (§12.3).

The 6-Category Scan

#	Category	Status	Section	Why It Matters	Impact
1	Auto-renewal	🟡 Worth a redline	§3.2	90-day notice is long but acceptable. 7%-or-CPI floor escalator is aggressive — CPI alone is market.	~$13K/yr overpayment
2	Data ownership	🔴 Deal-breaker	§9.1, §9.4	'Perpetual license to aggregated data' sounds harmless but has no guardrails. 30-day export window is tight given PII volume.	Acquisition risk + compliance
3	Liability cap	🔴 Deal-breaker	§8.1, §8.3	3-month cap on a 36-month deal is ~4x below market. 'Lost data' exclusion swallows the only remedy you'd ever want.	$540K+ exposure on breach
4	Indemnification	🔴 Deal-breaker	§14.2	IP indemnity is subject to the (already-too-low) liability cap. 'U.S. patents issued as of Effective Date' excludes future patents — nonstandard.	Full defense costs on you
5	SLA	🟡 Worth a redline	§11, Exhibit B	99.5% = ~3.6 hrs downtime/month. Credits capped at 15% with no chronic-failure termination right.	~$28K/yr credit ceiling
6	Termination for convenience	🔴 Deal-breaker	§12.3	Vendor can walk in 90 days; you're locked for 36 months. One-sided.	Strategic risk + acquisition blocker

Top 3 Rewrites (Push Back On These)

Issue #1: Liability Cap is 4x Below Market (§8.1)

Current language: Total liability capped at fees paid in the 3 months preceding the claim (~$46K on a $185K ACV).
Why this is a deal-breaker: You store customer PII. A breach could trigger GDPR/CCPA exposure in the six-figure range minimum. In 3 out of 5 recent enterprise breaches we've tracked, first-year remediation exceeded $500K. A 3-month cap means you absorb 90%+ of the loss.
Market-standard rewrite (paste-ready):

> 'EACH PARTY'S TOTAL LIABILITY UNDER THIS AGREEMENT SHALL NOT EXCEED TWO TIMES (2X) THE FEES PAID OR PAYABLE BY CUSTOMER IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM. NOTWITHSTANDING THE FOREGOING, THE CAP SHALL BE THREE TIMES (3X) SUCH FEES FOR (A) BREACHES OF CONFIDENTIALITY OR DATA PROTECTION OBLIGATIONS, (B) INDEMNIFICATION OBLIGATIONS, AND (C) GROSS NEGLIGENCE OR WILLFUL MISCONDUCT.'

Softer fallback: 1x annual fees for general; 2x for data/IP breaches.
Your talking point: 'A 3-month cap on a 3-year deal with PII in scope isn't going to get past our security review or a future acquirer's diligence. We need 12 months as a baseline and a 2x super-cap for data breaches.'

Issue #2: Perpetual License to 'Aggregated' Customer Data (§9.1)

Current language: Perpetual, royalty-free license to use Customer Data in aggregated/anonymized form for Provider's business purposes, including benchmarking.
Why this is a deal-breaker: 'Anonymized' is undefined. Your support transcripts contain customer PII, product feedback, and competitive intelligence. This clause lets the vendor train models, sell benchmarks to your competitors, and keep doing it forever after you terminate. This is the #1 reason PE diligence kills SaaS-heavy acquisitions in our experience.
Market-standard rewrite (paste-ready):

> 'Customer retains all right, title, and interest in Customer Data. Provider may use Customer Data solely (i) to provide and improve the Service for Customer, and (ii) in de-identified and aggregated form that cannot reasonably be linked to Customer or any individual, for the purpose of generating service analytics during the Term only. Provider shall not use Customer Data to train machine learning models that are made available to third parties. All rights granted under this Section terminate upon termination of this Agreement.'

Softer fallback: Keep the aggregated license but add 'during the Term only' and explicit exclusion of ML training for third-party benefit.
Your talking point: 'Our acquirer is going to ask who has a perpetual license to our customer data. The answer needs to be nobody.'

Issue #3: Termination for Convenience is One-Sided (§12.3)

Current language: Vendor may terminate for convenience with 90 days notice. Customer cannot terminate for convenience during the initial 36-month term.
Why this is a deal-breaker: Asymmetric convenience rights are the single biggest red flag in SaaS contracts — they mean the vendor can end your service but you can't end theirs. Combined with the 30-day data export window, a bad-faith termination could leave you with 60 days to migrate 40 trained users and extract multi-year PII data.
Market-standard rewrite (paste-ready):

> 'Neither party may terminate this Agreement for convenience during the Initial Term. Following the Initial Term, either party may terminate for convenience upon ninety (90) days written notice. In the event Provider terminates for convenience or discontinues the Service, Provider shall (i) refund any prepaid, unused fees on a pro-rata basis, and (ii) provide Customer with a data export window of no less than one hundred eighty (180) days.'

Softer fallback: Remove vendor's convenience right during Initial Term, OR extend your export window to 180 days with pro-rata refund if they walk.
Your talking point: 'Either we both have convenience rights, or neither of us does. One-sided is a non-starter.'

What NOT to Fight

90-day renewal notice (§3.2): Longer than we'd like but within the 60-90 day market range. Save leverage for the CPI floor.
99.5% uptime (§11): Standard for this price tier. Fight the exclusions and credit cap, not the number.
Consequential damages waiver (§8.3): Universal in SaaS. Fighting this signals you don't know the market.
Scheduled maintenance exclusion from SLA: Market-standard provided the maintenance windows are reasonable (ask what they are).

Questions to Ask the Vendor Before Signing

1. 'What does your standard insurance coverage look like — cyber liability limits specifically?' (Their answer reveals whether a higher cap is even insurable on their side.)

2. 'Can you show us your SOC 2 Type II report and the most recent pen test summary?' (If they hesitate, the data clauses matter 10x more.)

3. 'What's your definition of anonymized data, and do you use customer data to train models accessible to other customers?'

4. 'If we're acquired during the term, will you consent to assignment without additional fees?' (Given your PE talks, this is critical.)

5. 'What's your scheduled maintenance cadence and window?' (Turns the SLA exclusion from blank check into measurable.)

The Bottom Line

You are underpriced on risk by roughly $540K. The 3-month liability cap on a PII-handling vendor is the single most important fix — non-negotiable.
The perpetual data license will kill your PE deal. Fix it now, not in 18 months when diligence starts.
Asymmetric termination = vendor leverage forever. Either make it mutual or remove it entirely.
Trade the CPI floor, the renewal notice, and the SLA credit cap as a bundle — these are your 'give' items to win the top 3.
Walk-away threshold: If they refuse movement on liability cap AND data license, this deal isn't worth $185K/yr. Two alternatives + 40 trained users is enough leverage to say no.

Common use cases

Reviewing a vendor's MSA before signing a $50K+ SaaS deal
Preparing redlines for a procurement call with a SaaS vendor
Customer-side: checking if your own SaaS agreement protects you from a mid-contract renegotiation
Vendor-side: stress-testing your own standard agreement before sending to a large enterprise buyer
In-house counsel triage when 6 contracts hit the queue on Monday
Founders signing their first real enterprise SaaS deal without a lawyer on retainer
Renewal negotiations where you want to fix what you should have negotiated originally

Best AI model for this

Claude Sonnet 4.5 or GPT-5. Claude is noticeably sharper at contract interpretation and spotting asymmetric language — in our testing it caught liability cap gaps that GPT missed 2 out of 5 times. For contracts over 30 pages, use Claude with extended thinking enabled.

Pro tips

Paste the ENTIRE agreement including exhibits, order forms, and DPA. The deal-breakers hide in exhibit B more often than the main body.
Tell the prompt which side you're on (customer or vendor) — the same clause is a trap from one side and a win from the other.
Give it your ACV (annual contract value). Liability caps and termination fees only make sense relative to deal size.
If the output flags something you don't understand, paste it back and ask 'explain this to me like I'm a founder, not a lawyer.'
For the top-3 rewrites, always ask the prompt for a softer and harder version. You want negotiating room.
Don't skip the SLA section even if you think you don't care. SLA credits are the only contractual remedy 90% of customers actually use.

Customization tips

Always tell the prompt your ACV — the difference between a fair liability cap on a $20K deal and a $2M deal is 100x, and the prompt calibrates to the number you give it.
If you're on the VENDOR side, flip the frame: run the prompt and then ask 'which of these would a sophisticated customer push back on, and what's my best response?' — it becomes a negotiation prep tool.
For contracts over 50 pages, break it into two passes: first pass on the main MSA, second pass on the DPA and order form separately. Exhibits hide the worst stuff.
After getting the output, paste the vendor's counter-proposal back in and ask 'is this counter acceptable or are they playing games with language?' — catches softened-but-still-bad rewrites.
If you have a lawyer, use this prompt BEFORE the lawyer call. You'll show up knowing which 3 issues matter and save 2-3 hours of billable time on triage.

Variants

Procurement Mode

Optimizes for customer-side Fortune-500 procurement priorities: liability, data, audit rights, and most-favored-customer pricing.

Founder Quick-Scan

Compresses output to a 1-page brief with only the 3 must-fight clauses — for founders signing deals without legal support.

Renewal Recovery

Assumes you already signed a bad version and identifies which deal-breakers you can realistically fix at renewal vs. which are locked in.

Frequently asked questions

How do I use the SaaS Agreement Deal-Breaker Finder prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with SaaS Agreement Deal-Breaker Finder?

Can I customize the SaaS Agreement Deal-Breaker Finder prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Paste the ENTIRE agreement including exhibits, order forms, and DPA. The deal-breakers hide in exhibit B more often than the main body.; Tell the prompt which side you're on (customer or vendor) — the same clause is a trap from one side and a win from the other.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals

Curated by

Promptolis Editorial

Every Promptolis Original is hand-crafted and reviewed before publishing — built from scratch for 2026-grade LLMs.

Last reviewed on 2026-04-19 · About Promptolis