Most companies treat SaaS vendor agreements like a formality. Sign, onboard, move on. But buried inside those contracts are auto-renewal traps, data portability restrictions, and pricing escalation clauses that turn a “good deal” into a six-figure liability within 18 months.
At Seisan, we use the “Pilot vs. Engine” approach. We’ve developed a way to feed contract language and product specs into Gemini 3 as a Risk Analysis Engine, and go one step further: we calculate whether you should even be renting this tool at all, or if building a custom solution gives you a better 3-year ROI. This workflow is optimized for Gemini 3, which handles long-form document analysis and multi-phase reasoning particularly well.
Jump to a Section:
1. The Contract Stress Test | 2. The 5-Point Vendor Risk Protocol | 3. The Seisan Rule
Copy the full prompt below and paste it into Gemini 3 (recommended for its extended context window). Attach your vendor agreement, MSA, or pricing documentation and fill in the company context fields.
You are an Enterprise SaaS Contract Risk Analyst and Build vs. Rent Strategist. I am providing either:
(A) A vendor agreement, MSA, order form, or terms of service for a SaaS product, OR
(B) A product's pricing page, feature documentation, and/or sales proposal.
Along with this context about my company:
- Company size: [INSERT - e.g., 150 employees]
- Projected growth rate: [INSERT - e.g., 20% headcount growth/year]
- Current annual spend on this tool (or category): [INSERT]
- Number of systems this tool integrates with: [INSERT]
- Industry compliance requirements: [INSERT - e.g., HIPAA, SOC 2, GDPR, none]
PHASE 1, CONTRACT RISK AUDIT
Analyze every clause and return a risk-rated assessment using this framework:
For EACH risk found, output:
| Risk | Clause Reference | Severity (Critical/High/Medium/Low) | What It Means in Plain English | Negotiation Counter-Language |
Specifically scan for:
1. Auto-renewal terms and cancellation windows
2. Price escalation clauses (fixed %, CPI-linked, or discretionary)
3. Data portability and export restrictions
4. Usage caps, overage fees, and "unlimited" limitations
5. Termination fees and early exit penalties
6. Data residency, ownership, and processing terms
7. SLA commitments and remedy limitations
8. Liability caps and indemnification gaps
9. Change-of-control and assignment clauses
10. Compliance gaps (GDPR, CCPA, HIPAA, SOC 2, based on my stated requirements)
PHASE 2, BUILD VS. RENT ANALYSIS
Using the contract terms and my company context, generate a 3-Year Total Cost Comparison:
RENT (Current SaaS Path):
- Year 1-3 license/subscription fees (factoring in price escalation clauses found above)
- Integration and middleware costs
- Customization and workaround costs
- Training and onboarding costs
- Estimated exit/migration costs at end of Year 3
BUILD (Custom Solution Path):
- Estimated build cost for equivalent core functionality (not feature parity, functional parity for YOUR workflows)
- Annual maintenance and hosting costs (Years 2-3)
- Integration development costs
- Internal team capacity requirements
Output a Build vs. Rent Scorecard:
| Factor | Rent Score (1-10) | Build Score (1-10) | Analysis |
Factors: 3-Year TCO, Time to Value, Vendor Dependency Risk, Data Control, Customization Flexibility, Scalability at Growth Rate, Compliance Control, IP Ownership
Final Verdict: RENT / BUILD / RENT WITH RENEGOTIATION, with a one-paragraph justification and the single most important factor driving the recommendation.
PHASE 3, NEGOTIATION PLAYBOOK (if Verdict = RENT or RENT WITH RENEGOTIATION)
For every Critical and High severity risk found in Phase 1, provide:
- The exact counter-language to propose
- The business justification for the change
- A walk-away threshold (at what point this term alone justifies switching vendors or building)
Format the entire output as a structured report that can be forwarded directly to Legal, Procurement, or a CTO.
Use this checklist alongside the audit to ensure enterprise-grade vendor diligence:
A SaaS subscription is not a strategy. If your “Build vs. Rent” analysis shows that you’re paying more in vendor fees, customization, and integration costs than it would take to own the solution outright, you’re not saving time. You’re financing someone else’s product roadmap.
If the Contract Stress Test returns more than two “High Risk” findings, and the Build vs. Rent scorecard shows break-even inside 18 months, you already have your answer.
At Seisan, we specialize in replacing rented tools with purpose-built platforms that our clients own: zero per-seat fees, zero vendor lock-in, and an architecture designed around how your business actually operates. If you need full-scope vendor evaluations, architecture planning, and custom build execution that go beyond what any prompt can deliver, Reach out to our team and we’ll scope an engagement that fits.
