Contract Summary Prompt Templates

Contract Summary: CloudTech SaaS Agreement

**Parties**: [Our Company] (Customer) ↔ CloudTech Inc. (Vendor)
**Contract Type**: SaaS Subscription Agreement
**Effective Date**: November 1, 2024
**Term**: 3 years (ends October 31, 2027)

---

**FINANCIAL TERMS**

| Item | Amount | Timing |
|------|--------|--------|
| Annual subscription | $120,000 | Due annually in advance |
| Implementation fee | $25,000 | Due at signing |
| Total Year 1 | $145,000 | |
| Total 3-year commitment | $385,000 | |

⚠️ **Price escalation**: 5% annual increase built in (Year 2: $126K, Year 3: $132K)

---

**KEY OBLIGATIONS**

*Our obligations:*
- Pay invoices within 30 days
- Maintain confidentiality of vendor pricing
- Provide reasonable access for implementation

*Vendor obligations:*
- 99.9% uptime SLA
- 24/7 support response within 4 hours
- Data stored in US-based data centers
- SOC 2 Type II compliance maintained

---

**IMPORTANT DATES**

- **Signing deadline**: October 15, 2024 (to lock pricing)
- **Implementation start**: November 1, 2024
- **Go-live target**: January 15, 2025
- **Auto-renewal notice**: 90 days before expiration

---

**TERMINATION PROVISIONS**

- Early termination: Only for material breach (30-day cure period)
- No termination for convenience during initial term
- Auto-renews for 1-year terms unless 90-day written notice

⚠️ **Risk**: We cannot exit early without cause; 3-year commitment is firm

---

**ITEMS REQUIRING ATTENTION**

1. **Liability cap is low**: Limited to 12 months of fees ($120K). Industry standard is 24 months. Recommend negotiating.

2. **Data portability unclear**: No specific timeline for data export upon termination. Add 30-day data access requirement.

3. **Price increase clause**: 5% automatic increases are above market. Suggest capping at 3% or CPI.

---

**RECOMMENDATION**

Contract is generally acceptable with three suggested changes before signing. Total financial commitment of $385K over 3 years is within budget.

Contract Comparison: Vendor Alpha vs. Vendor Beta

---

**SIDE-BY-SIDE COMPARISON**

| Term | Vendor Alpha | Vendor Beta | Advantage |
|------|--------------|-------------|----------|
| **Annual cost** | $95,000 | $110,000 | Alpha (-$15K) |
| **Contract term** | 2 years | 3 years | Alpha (shorter) |
| **Implementation** | $15,000 | Included | Beta |
| **Total commitment** | $205,000 | $330,000 | Alpha (-$125K) |
| **Price increases** | CPI capped at 3% | Fixed pricing | Beta |
| **Uptime SLA** | 99.5% | 99.9% | Beta |
| **Support response** | 8 hours | 4 hours | Beta |
| **Termination for convenience** | After Year 1 with 90-day notice | Not allowed | Alpha |
| **Liability cap** | 12 months fees | 24 months fees | Beta |
| **Data portability** | 30 days post-termination | 14 days post-termination | Alpha |

---

**KEY DIFFERENCES**

1. **Flexibility**: Alpha offers termination for convenience after Year 1; Beta locks us in for 3 years.

2. **Service levels**: Beta has stronger SLAs (99.9% vs 99.5% uptime, faster support).

3. **Total cost**: Alpha is $125K less over comparable period, even accounting for implementation fee.

4. **Risk protection**: Beta offers higher liability cap, better protecting us if something goes wrong.

---

**RECOMMENDATION**

**Choose Vendor Alpha** with negotiated improvements.

Rationale:
- $125K savings over contract life
- Exit flexibility after Year 1 is valuable (reduces risk if product doesn't meet needs)
- Service level gap (99.5% vs 99.9%) translates to ~4 hours more downtime per year, acceptable for our use case

**Suggested negotiations with Alpha:**
1. Increase liability cap to 24 months (match Beta)
2. Improve support response to 6 hours
3. Include first year's training at no cost

Obligation Tracker: Office Lease Agreement
123 Business Park Drive, Suite 400

---

**TENANT OBLIGATIONS (Our Responsibilities)**

| # | Obligation | Frequency | Deadline | Consequence of Non-Compliance |
|---|------------|-----------|----------|------------------------------|
| T1 | Pay base rent ($15,000/mo) | Monthly | 1st of each month | Late fee: 5% after 5-day grace |
| T2 | Pay CAM charges (~$3,500/mo) | Monthly | With rent | Same as rent |
| T3 | Maintain liability insurance ($2M) | Annual | Before occupancy, renew annually | Landlord can obtain and charge us |
| T4 | Provide insurance certificate | Annual | 30 days before policy expiration | |
| T5 | Keep premises in good condition | Ongoing | Throughout lease | Charged for repairs at move-out |
| T6 | No alterations without approval | As needed | Before any work | Must restore at own expense |
| T7 | Permit landlord access | As needed | 24-hour notice required | |
| T8 | Notify landlord of damage | Immediately | Within 24 hours | May be liable for additional damage |
| T9 | Renewal notice if desired | Once | 180 days before expiration | Lose right to renew |
| T10 | Return premises in original condition | End of lease | Move-out date | Security deposit forfeiture |

---

**LANDLORD OBLIGATIONS (Their Responsibilities)**

| # | Obligation | Frequency | Standard |
|---|------------|-----------|----------|
| L1 | Maintain building common areas | Ongoing | Good condition |
| L2 | Provide HVAC during business hours | Daily | 8am-6pm M-F |
| L3 | Maintain building systems | Ongoing | Working order |
| L4 | Provide 5 parking spaces | Ongoing | Throughout lease |
| L5 | Complete tenant improvements | Once | Before occupancy |

---

**CRITICAL DATES**

| Date | Action | Owner |
|------|--------|-------|
| Oct 15, 2024 | Sign lease | Both |
| Nov 1, 2024 | Provide insurance certificate | Us |
| Dec 1, 2024 | Occupancy / rent begins | Both |
| Jun 1, 2027 | Renewal notice deadline (180 days) | Us |
| Dec 1, 2027 | Lease expiration | Both |

---

**RECOMMENDED CALENDAR REMINDERS**

- [ ] Monthly: Rent due (set up autopay)
- [ ] 60 days before policy expiration: Renew insurance, send certificate
- [ ] 200 days before lease expiration: Begin renewal discussions
- [ ] 180 days before lease expiration: FINAL renewal notice deadline

Risk Analysis: IT Services Agreement with TechServe Inc.

---

**HIGH PRIORITY RISKS**

**Risk 1: Unlimited Liability for Data Breach**
Clause: Section 8.2 - Indemnification
Issue: We indemnify vendor for "any claims arising from customer data" with no cap
Impact: Potential unlimited financial exposure if data breach occurs
Likelihood: Low probability, catastrophic impact

→ **Recommendation: NEGOTIATE**
Proposed change: Cap data-related indemnification at $1M or insurance coverage amount. Add requirement that vendor maintains cyber liability insurance.

---

**Risk 2: Broad IP Assignment**
Clause: Section 12.1 - Intellectual Property
Issue: "All work product becomes vendor's exclusive property"
Impact: Custom development we pay for could be resold to competitors
Likelihood: High probability this would happen

→ **Recommendation: NEGOTIATE**
Proposed change: We own custom work; vendor retains only pre-existing IP and tools. Add non-compete clause for derivative works.

---

**Risk 3: No Service Level Guarantees**
Clause: Section 6 - Service Levels (missing)
Issue: No uptime commitment, response time guarantees, or remedies
Impact: No recourse if service is unreliable
Likelihood: Medium, new vendor, unproven reliability

→ **Recommendation: NEGOTIATE**
Proposed change: Add SLA addendum with 99.5% uptime, 4-hour response for critical issues, and service credits for misses.

---

**MEDIUM PRIORITY RISKS**

**Risk 4: Auto-Renewal with Price Increase**
Clause: Section 3.2 - Term and Renewal
Issue: Auto-renews annually with "then-current pricing" (no cap)
Impact: Could face significant price increases without warning
Likelihood: Medium, vendor pricing has increased 15% annually

→ **Recommendation: NEGOTIATE**
Proposed change: Require 90-day notice of price changes; cap increases at 5% or CPI.

---

**Risk 5: Unilateral Contract Changes**
Clause: Section 15.3 - Amendments
Issue: Vendor can modify terms with 30-day notice
Impact: Contract terms could change unfavorably mid-term
Likelihood: Low, but sets bad precedent

→ **Recommendation: NEGOTIATE**
Proposed change: Material changes require mutual written agreement.

---

**LOW PRIORITY RISKS (ACCEPT)**

**Risk 6: Jurisdiction in Vendor's State**
Clause: Section 16.1 - Governing Law
Issue: Delaware law, Delaware courts
Impact: Inconvenience if dispute arises
Likelihood: Very low, disputes are rare

→ **Recommendation: ACCEPT** (standard, not worth negotiating)

---

**SUMMARY**

| Risk | Priority | Action |
|------|----------|--------|
| Unlimited data liability | High | Must negotiate |
| IP assignment | High | Must negotiate |
| No SLAs | High | Must negotiate |
| Auto-renewal pricing | Medium | Should negotiate |
| Unilateral changes | Medium | Should negotiate |
| Jurisdiction | Low | Accept |

**Overall assessment**: Do not sign without addressing high-priority risks. Request redlined version with proposed changes.

**Original Clause**: [Confidentiality provision as quoted]

---

**Plain Language Translation**

When they share confidential information with us, we must:

1. **Keep it secret** - Don't share it with others, don't use it for purposes they didn't authorize

2. **Protect it carefully** - Use at least the same security measures we use for our own secrets (but at minimum, reasonable care)

3. **For 5 years** - This obligation lasts 5 years from when they told us the information

4. **Exception** - If the information becomes public through no fault of ours (e.g. they announce it, or someone else leaks it), we're released from this obligation for that specific information

---

**What This Means for Us**

✓ We can receive their confidential information (pricing, technology, business plans)
✓ We must train employees on what's confidential and how to protect it
✓ We need secure storage and access controls for their information
✓ After 5 years, we can use the information freely (unless still secret)

---

**Hidden Implications**

1. **"Same degree of care" standard**: If we have poor internal security practices, we're held to "reasonable care" instead, we can't use our own lax standards as an excuse.

2. **5-year tail**: Even after the business relationship ends, we're still obligated to protect their confidential information for years.

3. **Burden of proof**: If there's a leak, we may need to prove it wasn't our fault. Document all handling of their information.

4. **No carve-outs**: This applies to ALL confidential information. Consider requesting exceptions for information we already knew or developed independently.

---

**Recommended Action**

This is a standard confidentiality clause. Accept as-is, but ensure you have:
- [ ] Employee confidentiality training
- [ ] Secure document storage
- [ ] Process to label and track their confidential materials
- [ ] Destruction procedure for when the obligation ends