教程 16: Advanced Contract Intelligence

使用我们的标准化分类法提取全面的合同条款。

Contract: [Insert full contract text or upload file]
Extraction Focus: Complete provision mapping across all 40+ areas

Please provide:

1. PROVISION INVENTORY
   Extract from these 40+ areas:

   COMMERCIAL TERMS (15 areas):
   - 付款条款和条件
   - 定价和费率结构
   - 数量折扣和返利
   - 价格调整机制
   - 币种和支付方式
   - 开票时间和流程
   - 逾期付款罚则
   - 提前付款折扣
   - 信用条款和额度
   - 计费争议和调整
   - 最低采购承诺
   - 最惠国条款
   - 价格上涨触发条件
   - 终止费用
   - 续签定价

   COMPLIANCE & RISK (12 areas):
   - 数据安全要求
   - 保密和 NDA 条款
   - 保险覆盖要求
   - 赔偿范围和上限
   - 责任限制
   - 保证免责声明
   - 合规认证
   - 监管要求变化
   - 第三方受益人权利
   - 转让和分包
   - 审计与合规核验
   - 违约救济

   OPERATIONAL (13 areas):
   - 服务级别协议 (SLAs)
   - 绩效指标和目标
   - 响应时间承诺
   - 正常运行时间保证
   - 支持和维护窗口
   - 升级流程
   - 变更管理流程
   - 资源分配要求
   - 人员配置和技能要求
   - 质量保证流程
   - 灾难恢复条款
   - 业务连续性要求
   - 终止流程和时间安排

2. CUSTOM EXTRACTION TEMPLATES
   For each identified provision:
   | Area | Provision Type | Source Section | Exact Language | Interpreted Obligation | Risk Level |
   | --- | --- | --- | --- | --- | --- |

3. NESTED CLAUSE DETECTION
   - 识别含有条件逻辑的条款
   - 映射条款之间的依赖关系
   - 展示相互作用链条
   - 标记复合条件

4. CROSS-REFERENCE MAPPING
   - 哪些条款引用了其他条款？
   - 定义是否一致？
   - 是否存在相互冲突的条款？
   - 是否存在含糊不清的交叉引用？

5. OBLIGATION SUMMARY TABLE
   | Party | Obligation | Timing | Condition | Failure Consequence |
   | --- | --- | --- | --- | --- |

为该合同生成红黄绿风险评估。

Contract: [Insert contract]
Company Perspective: [Buyer/Seller/Service Provider/Vendor]
Risk Appetite: [Conservative/Moderate/Aggressive]

Please provide:

1. EXECUTIVE RISK DASHBOARD

   Color-Code Definitions:
   - GREEN: 低风险，市场条款标准，符合政策
   - YELLOW: 中等风险，需要监控或轻度修正
   - RED: 高风险，存在重大偏离，需要升级处理/谈判
   - GRAY: 语言不清晰，存在需要澄清的歧义

2. TRAFFIC LIGHT ANALYSIS BY AREA

   | Area | Risk Level | Provision | Deviation from Standard | Severity | Recommended Action |
   | --- | --- | --- | --- | --- | --- |

   CRITICAL AREAS (Rate all as GREEN/YELLOW/RED):
   - 付款和财务条款
   - 责任限制
   - 终止权和通知
   - 保密和 IP 所有权
   - 赔偿范围
   - 保险要求
   - 数据安全与合规
   - 履约保证

3. POSITION DEVIATION SCORING
   For each RED or YELLOW provision:

   Standard Market Position: [典型市场措辞通常如何表述]
   This Contract Position: [本合同如何表述]
   Deviation Analysis: [与标准相比偏离程度如何]
   Impact if Accepted: [接受后的业务后果]
   Negotiation Priority: [1=必须修改, 2=应当修改, 3=可修改]

4. RISK AGGREGATION METHODOLOGY

   计算整体合同风险：
   - Count RED items: _____ x Weight 3 = _____
   - Count YELLOW items: _____ x Weight 1 = _____
   - Sum = _____ (Risk Score out of 100)

   Interpretation:
   - 0-20: 低风险 (GREEN) - Approval level: Manager
   - 21-50: 中等风险 (YELLOW) - Approval level: Director
   - 51-80: 高风险 (RED) - Approval level: VP/General Counsel
   - 81-100: 严重风险 (ALERT) - Approval level: C-Suite + Outside Counsel

5. VISUAL DASHBOARD TEXT DESCRIPTION
   [该合同包含：
   - 15 项 GREEN 条款（安全）
   - 8 项 YELLOW 条款（需监控）
   - 3 项 RED 条款（需谈判）
   - 1 个 GRAY 领域（需澄清）

   Overall Risk: MODERATE，且有 3 个关键事项需要关注]

6. EXECUTIVE SUMMARY
   适合董事会/客户汇报的关键结论：
   - 主要风险及其业务影响
   - 建议采取的行动和谈判方向
   - 批准建议（Yes/Conditional/No）

对我们的合同库开展组合层面的分析。

Input: [Directory of contracts OR contract list with key metadata]
Scope: [All contracts OR specific category: vendors, customers, employees, etc.]

Please provide:

1. PORTFOLIO OVERVIEW
   - 分析的合同总数： _____
   - 覆盖的时间区间： _____
   - 交易对方： _____ 个唯一主体
   - 合同金额：$_____ 至 $_____ 区间

   | Category | Count | Total Value | Risk Level |
   | --- | --- | --- | --- |

2. RISK DISTRIBUTION ANALYSIS

   按风险级别划分的合同：
   | Risk Level | Count | Percentage | Total Value | Examples |
   | --- | --- | --- | --- | --- |
   | GREEN (Low) | | | | |
   | YELLOW (Moderate) | | | | |
   | RED (High) | | | | |
   | GRAY (Unclear) | | | | |

   Interpretation: 识别风险集中情况

3. PROVISION FREQUENCY ANALYSIS

   哪些条款出现最频繁？

   | Provision Type | Frequency | Standard Language | Deviations | Outliers |
   | --- | --- | --- | --- | --- |
   | Liability Limitation | 48/50 | "Limit to 12 months fees" | 2 contracts differ | [List] |
   | Termination Notice | 50/50 | "30 days written notice" | 8 contracts use 60 days | [List] |
   | Indemnification | 42/50 | Mutual, capped at $X | 8 contracts unilateral | [List] |

4. TREND ANALYSIS

   历史模式：
   - 随时间推移，条款是变得更有利还是更不利？
   - 我们是否更频繁地接受高风险事项？
   - 对手方比较：谁的谈判最强硬？
   - 团队比较：哪些团队接受的风险最多？
   - 行业基准：我们与同行相比如何？

5. RISK AGGREGATION BY DIMENSION

   从多个视角查看组合风险：

   By Counterparty:
   | Counterparty | # Contracts | Aggregate Risk | Highest Risk Contract |
   | --- | --- | --- | --- |

   By Contract Type:
   | Type | # Contracts | Aggregate Risk | Average Risk |
   | --- | --- | --- | --- |

   By Provision Area:
   | Area | # High-Risk Items | Frequency | Standardization Opportunity |
   | --- | --- | --- | --- |

6. STANDARDIZATION OPPORTUNITIES

   我们可以在哪些方面提升一致性？

   | Provision | Current Variation | Recommended Standard | Contracts to Update |
   | --- | --- | --- | --- |
   | Liability Cap | Ranges from 6-24 months | Standardize to 12 months | [List 8 contracts] |
   | Notice Period | 30, 45, 60 days mixed | Standardize to 30 days | [List 5 contracts] |
   | Insurance | $1M-$10M coverage varies | Standardize to $5M minimum | [List 12 vendors] |

7. BENCHMARK COMPARISON

   我们的合同组合与行业标准相比如何？
   - Liability limitations: 我们[更/较少]保护自己
   - Payment terms: 我们付款[更快/更慢]
   - Termination rights: 我们[更/较少]灵活
   - Confidentiality: 我们[更/较少]严格

8. RECOMMENDATIONS

   高影响改进：
   1. 在 [X] 份合同中标准化 [provision]（工作量：低，影响：高）
   2. 与 [Y] 家 vendors 就 [provision] 重新谈判（工作量：中，影响：中）
   3. 实施 [policy]，防止未来合同中出现 [Z]

比较多份合同中的特定条款，以识别差异。

Clause to Compare: [e.g., "Limitation of Liability"]
Contracts to Include: [Specific contracts or full repository]

Please provide:

1. CLAUSE LANGUAGE MATRIX

   | Contract | Clause Language (full text) | Key Variables | Interpretation |
   | --- | --- | --- | --- |
   | Customer A | "Neither party shall be liable for..." | Cap: 12 months, Excludes IP/Confidentiality | Moderate risk |
   | Customer B | "Liability of either party limited to..." | Cap: 24 months, Includes everything | Aggressive |
   | Vendor X | "Company's total liability shall not exceed..." | Cap: 6 months, Narrow scope | Conservative |

2. SIMILARITY SCORING

   比较每个变体：
   | Pair | Similarity Score | Key Differences | Risk Differential |
   | --- | --- | --- | --- |
   | Customer A vs. B | 65% similar | 上限期间不同 | Medium |
   | Customer A vs. Vendor X | 45% similar | 范围差异显著 | High |
   | Customer B vs. Vendor X | 50% similar | 多项关键差异 | High |

   是什么让合同相似/不同？
   - 责任上限（期限/金额）
   - 排除范围（哪些内容不受限制）
   - carve-outs（责任限制的例外）
   - “damages”的定义

3. BEST-IN-CLASS IDENTIFICATION

   哪个版本最符合我们的利益？

   **For our vendor relationships (we want narrow liability):**
   Recommended: [Contract name] language
   Rationale: [具体保护我们的条款]

   **For our customer relationships (we want broad liability):**
   Recommended: [Contract name] language
   Rationale: [具体降低我们风险的条款]

   Best Overall Drafting Quality: [Contract] because [reasons]

4. STANDARDIZATION RECOMMENDATIONS

   建议的标准措辞：

   [Drafting recommended language that incorporates best elements]

   Rationale:
   - 与我们的风险偏好更一致
   - 更符合市场标准
   - 起草更清晰（更少歧义）
   - 与新交易对方谈判更容易

5. CLAUSE EVOLUTION TRACKING

   如果是在比较同一合同不同时期的版本：

   | Version | Date | Key Changes | Why Changed | Impact |
   | --- | --- | --- | --- | --- |
   | v1.0 | 2023 | 上限为 6 个月 | 标准市场做法 | 低风险 |
   | v2.0 | 2024 | 上限提高到 12 个月 | 对手方施压 | 中等风险 |
   | v3.0 | 2024 | 增加 IP carve-out | 内部要求 | 对我们而言风险更高 |

6. NEGOTIATION GUIDANCE

   向对手方说明时：
   - "Our standard language (from [contract]) uses..."
   - "Market-standard approach (seen in [X]% of deals) suggests..."
   - "Balanced approach: yours says X, ours says Y, how about Z?"

提取所有合同义务和 SLA，以便进行结构化跟踪。

Contract: [Insert contract]
Party Perspective: [We are the Service Provider / We are the Customer]

Please provide:

1. OBLIGATION INVENTORY

   提取每一项义务，并按当事方分类：

   | Party | Obligation | Source Section | Due Date | Condition | Performance Standard |
   | --- | --- | --- | --- | --- | --- |
   | Service Provider | 在 4 小时内提供支持 | Section 5.2 | 在收到通知后 4 小时内 | 在营业时间内 | 初步响应 |
   | Service Provider | 维持 99.5% 正常运行时间 | Section 4.1 | 持续按月 | 不包括计划维护 | 每月测量 |
   | Customer | 在 30 天内支付发票 | Section 2.1 | Net 30 | 收到发票后 | 无逾期付款罚金 |

2. SLA DASHBOARD

   用于监控的结构化服务级别协议：

   | SLA Metric | Target | Measurement | Owner | Verification Method | Consequence if Missed |
   | --- | --- | --- | --- | --- | --- |
   | Response Time | 4 小时（营业时间） | 自工单创建起 | Provider | 系统日志 | 当月 5% 服务抵扣 |
   | Resolution Time | 24 小时（严重问题） | 自工单创建起 | Provider | 系统日志 | 当月 10% 服务抵扣 |
   | Uptime | 99.5% | 每月计算 | Provider | 监控系统 | 每差 0.1% 服务抵扣 1% |
   | Availability | 99.9% | 每日 8am-6pm | Provider | 状态页 | 升级处理与重新谈判 |

3. DEADLINE & RENEWAL TRACKING

   所有有时间敏感性的义务：

   | Obligation | First Due | Recurring | Frequency | Owner | Escalation Point |
   | --- | --- | --- | --- | --- | --- |
   | 续签决定 | 2025-03-15 | 每年 | 到期前 60 天 | Account Manager | 提前 90 天 |
   | 保险证明 | 2025-06-30 | 每年 | 应请求提供 | Vendor | 到期前 30 天 |
   | 合规审计 | 2025-04-01 | 每年 | Q2 | Compliance Officer | 应请求时 |
   | 费用增长 | 2025-01-01 | 每年 | 通胀率 | Finance | 需提前 60 天通知 |

4. PERFORMANCE MEASUREMENT SETUP

   如何衡量义务是否得到履行：

   | Obligation | Measurable? | How to Verify | Data Source | Frequency |
   | --- | --- | --- | --- | --- |
   | "Provide responsive support" | Soft (vague) | 响应时间跟踪 | 支持工单系统 | 每张工单 |
   | "Respond within 4 hours" | Hard (specific) | 时间戳比较 | 支持工单系统 | 每张工单 |
   | "Maintain 99.5% uptime" | Hard (specific) | 每月计算 | 监控系统 | 每月 |
   | "Best efforts" | Soft (vague) | 文档审查 | 项目日志 | 视争议而定 |

   FLAG: 软性义务会增加争议风险——应澄清或收紧措辞

5. COMPLIANCE MONITORING CALENDAR

   针对义务截止日期的自动提醒：

   | Obligation | Due Date | Alert Date (30 days prior) | Owner | Status |
   | --- | --- | --- | --- | --- |
   | 续签决定 | 2025-03-15 | 2025-02-13 | [Name] | [ ] Set reminder |
   | 保险证明 | 2025-06-30 | 2025-05-31 | [Name] | [ ] Set reminder |
   | 年度审计 | 2025-04-01 | 2025-03-02 | [Name] | [ ] Set reminder |

6. BREACH CONSEQUENCE MATRIX

   如果义务未被履行，会发生什么？

   | Obligation | Minor Breach | Material Breach | Cure Period | Consequence | Termination Right |
   | --- | --- | --- | --- | --- | --- |
   | 响应时间 | 晚 1-2 小时 | 晚 24+ 小时 | 5 个工作日 | 5% 服务抵扣 | 2 次违约后可终止 |
   | 正常运行时间 | 99.4% | 99.0% 或以下 | N/A | 服务抵扣升级 | 连续 3 个月后可终止 |
   | 付款 | 晚 5 天 | 晚 15+ 天 | 10 天 | 滞纳金 (1.5%/month) | 暂停服务 |

为关键合同生命周期里程碑设计自动提醒。

Contract Portfolio: [Describe scope: all contracts, vendors only, etc.]
Timeline: [What future period to plan for: 12 months, 24 months, etc.]

Please provide:

1. LIFECYCLE MILESTONE MAP

   | Milestone | Timing | Owner | Trigger | Notification | Action Required |
   | --- | --- | --- | --- | --- | --- |
   | 合同签署 | Day 0 | Account Manager | 手动上传 | 向利益相关者发送电子邮件 | 分发给团队 |
   | 续签决策截止日 | 到期前 90 天 | Contract Manager | 自动触发 | 向决策者发送电子邮件 | 谈判或续签 |
   | 重新谈判窗口 | 提前 60-90 天 | Account Manager | 自动触发 | 启动会议邀请 | 确定讨论范围 |
   | 最终续签通知 | 提前 30 天 | Contract Manager | 自动触发 | 电子邮件 + 系统提醒 | 需要最终决定 |
   | 自动续签执行 | 于合同日期 | System | 自动触发 | 邮件确认 | 归档签署版本 |
   | 续签后复核 | 续签后 7 天 | Account Manager | 自动触发 | 日历提醒 | 审查变更并更新 |

2. ESCALATION WORKFLOWS

   如果错过截止日期，会发生什么？

   | Milestone | Miss Date T+0 | Miss Date T+7 days | Miss Date T+14 days | Final Escalation |
   | --- | --- | --- | --- | --- |
   | 续签决定 | 发送邮件提醒 | 升级给 Director | 升级给 VP | 通知 CEO |
   | 启动重新谈判 | Slack/Teams 消息 | 给经理发邮件 | 给 VP 打电话 | 触发自动续签 |
   | 保险证明到期 | 邮件提醒 | 请求重新发送 | 发票暂停/警告 | 暂停服务 |
   | 合规审计 | 邮件提醒 | 会议重新安排 | 合规标记 | 升级给 GC |

3. EVENT-BASED TRIGGER RULES

   为事件设置自动化：

   | Trigger Event | Action | Timing | Ownership |
   | --- | --- | --- | --- |
   | 临近价格上调条款 | 收集替代方案报价 | 提前 120 天 | Procurement |
   | 适用数量折扣 | 审查使用指标 | 每年 Q1 | Finance |
   | 保险证明到期 | 请求续期 | 提前 60 天 | Legal |
   | 交易对方被收购 | 标记以供审查和批准 | 收到通知时 | Management |
   | 监管变化影响合同 | 标记以供修订 | 公告发布时 | Compliance |
   | 对方关键人员变动 | 更新联系人数据库 | 收到通知时 | Account Manager |

4. RENEWAL DECISION FRAMEWORK

   当续签里程碑触发时，决策者应考虑：

   Questions to Answer:
   - [ ] 这份合同是否仍有必要？（是/否/调整范围）
   - [ ] 我们的合作关系如何？（极好/良好/一般/较差）
   - [ ] 条款是否仍然有利？（良好/可接受/应重新谈判）
   - [ ] 我们的筹码如何？（强/中性/弱）
   - [ ] 我们是否找到替代方案？（是/否/进行中）
   - [ ] 价格是否可接受？（是/需要谈判）
   - [ ] 建议行动：（按现状续签 / 变更后续签 / 不续签 / 暂停并寻找替代方案）

5. NOTIFICATION ESCALATION MATRIX

   | Level | Trigger | Notification Method | Recipient | Timing |
   | --- | --- | --- | --- | --- |
   | Level 1 (Early) | 提前 90 天 | Slack/Teams 消息 | Account Manager | 一次性 |
   | Level 2 (Attention) | 提前 60 天 | Email + Calendar invite | Manager + Director | 一次性 |
   | Level 3 (Action Required) | 提前 30 天 | Email + Phone call | Director + VP | 一次性 |
   | Level 4 (Critical) | 提前 14 天 | Email + Daily alerts | VP + GC + CFO | 每日重复 |
   | Level 5 (Emergency) | 7 天或更少 | 所有渠道 | 所有利益相关者 + CEO | 每日多次 |

6. IMPLEMENTATION CHECKLIST

   构建该系统时：
   - [ ] 已对合同库及续签日期完成编目
   - [ ] 已配置通知系统（email/Slack/Teams）
   - [ ] 已记录并达成一致的升级规则
   - [ ] 已分配角色和职责
   - [ ] 已为所有合同设置日历提醒
   - [ ] 已安排每月复核流程
   - [ ] 已制定错过截止日期时的应急预案
   - [ ] 已定义成功指标（如按时续签比例等）

分析合同谈判时间线和效率指标。

Data: [Contract negotiation log covering recent deals]
Include: [Contract, counterparty, key dates, redline count, parties involved]

Please provide:

1. NEGOTIATION CYCLE TIME ANALYSIS

   | Contract | Start Date | Signature Date | Total Days | Bottleneck Phase |
   | --- | --- | --- | --- | --- |
   | Customer ABC | 2024-01-15 | 2024-02-20 | 36 days | 商业条款（14 天） |
   | Vendor XYZ | 2024-02-01 | 2024-03-10 | 37 days | 法律审查（18 天） |
   | Partner 123 | 2024-02-15 | 2024-02-28 | 13 days | 快速通道 - 变更极少 |
   | Complex Deal | 2024-03-01 | 2024-05-15 | 76 days | 律师审查周期（38 天） |

   平均周期时长： _____ days
   中位周期时长： _____ days
   区间： _____ to _____ days

   最快交易： _____ days（为什么快？）
   最慢交易： _____ days（为什么慢？）

2. PHASE-BY-PHASE BREAKDOWN

   时间实际花在何处？

   | Phase | Average Days | % of Total Time | Variance | Bottleneck? |
   | --- | --- | --- | --- | --- |
   | 初始起草 | 5 days | 12% | 2-8 days | 低波动 |
   | 首轮审查 | 7 days | 16% | 3-14 days | 中等波动 |
   | 首轮 redlines | 6 days | 14% | 2-12 days | 中等波动 |
   | 商务谈判 | 12 days | 28% | 5-20 days | **波动最大** |
   | 法律审查周期 | 10 days | 23% | 5-25 days | **波动最大** |
   | 最终签署 | 3 days | 7% | 1-5 days | 低波动 |

   **识别出的瓶颈**：商务谈判和法律审查

3. REDLINE INTENSITY TRACKING

   每笔交易经历多少轮谈判？

   | Contract | Initial Draft | Redline Round 1 | Round 2 | Round 3 | Round 4+ | Total Rounds |
   | --- | --- | --- | --- | --- | --- | --- |
   | Fast Deal | Day 1 | Day 5 | Day 9 | Day 12 | N/A | 3 rounds |
   | Moderate Deal | Day 1 | Day 6 | Day 14 | Day 21 | Day 28 | 5 rounds |
   | Contentious Deal | Day 1 | Day 8 | Day 18 | Day 32 | Day 48, 60 | 7+ rounds |

   洞见：每轮 redline 平均增加约 6-8 天
   机会：减少轮次 = 缩短时间

4. STAKEHOLDER BOTTLENECK ANALYSIS

   是谁拖慢了进度？

   | Stakeholder | Typical Response Time | Variance | Blocker Count | Cause |
   | --- | --- | --- | --- | --- |
   | 内部法务 | 5 days | 2-10 days | 高 | 资源限制 |
   | 我方 CFO | 3 days | 1-7 days | 中 | 海外时区 |
   | 对方法务 | 8 days | 3-15 days | 高 | 其资源能力 |
   | 对方高管 | 6 days | 2-14 days | 高 | 决策延迟 |
   | 采购团队 | 4 days | 2-8 days | 中 | 流程延迟 |

5. PROCESS IMPROVEMENT OPPORTUNITIES

   | Bottleneck | Current State | Improvement Idea | Potential Savings | Implementation Effort |
   | --- | --- | --- | --- | --- |
   | 法律审查耗时 10 天 | 手动阅读所有变更 | 自动生成仅含关键问题的 redline 摘要 | 每笔交易节省 5 天 | 中 |
   | 商务谈判耗时 12 天 | 来回邮件沟通 | 使用含 3 个预批准变体的 playbook | 每笔交易节省 4-6 天 | 低 |
   | 平均 5 轮 redline | 无 playbook，自由编辑 | 实施带有限选项的标准模板 | 2-3 轮（12-18 天） | 中 |
   | 对方平均 8 天较慢 | 未施加催促 | 在 engagement letter 中设置响应预期 | 每笔交易节省 2-3 天 | 低 |
   | CFO 审批耗时 3 天 | 商业条款未预先批准 | 谈判前让 CFO 对区间预先签批 | 每笔交易节省 2 天 | 低 |

6. NEGOTIATION EFFICIENCY METRICS

   随时间跟踪以下 KPI：

   | Metric | Current | Target | Measurement |
   | --- | --- | --- | --- |
   | 平均周期时长 | 37 days | 25 days（减少 32%） | 从开始到签署的天数 |
   | redline 轮次中位数 | 5 rounds | 3 rounds（减少 40%） | 谈判轮次计数 |
   | 每轮 redline 用时 | 6.5 days | 5 days（减少 23%） | 两次提交之间的天数 |
   | 商务谈判时间 | 12 days | 7 days（减少 42%） | 达成商务一致所需时间 |
   | 法律审查时间 | 10 days | 5 days（减少 50%） | 获得法务批准所需时间 |

7. BENCHMARKING & TARGETS

   我们与行业相比如何？

   External Benchmarks:
   - 对可比交易类型，使用你们律所可信赖的基准来源
   - 按合同复杂度和交易对方画像分层
   - 说明法域、行业和交易规模差异

   Our Performance vs. Benchmark:
   - Fast-track: [Days] vs [Benchmark] - [Better/Worse]
   - Moderate: [Days] vs [Benchmark] - [Better/Worse]
   - Complex: [Days] vs [Benchmark] - [Better/Worse]

8. ACTION PLAN FOR IMPROVEMENT

   按影响排序：

   1. **为商业条款实施 playbook**
      - Cost: [Estimate internal build effort]
      - Impact: [Estimate annual cycle-time improvement]
      - ROI: High

   2. **自动化法律 redline 摘要**
      - Cost: [Estimate setup effort]
      - Impact: [Estimate per-deal time savings]
      - ROI: Very high

   3. **预先批准商业条款区间**
      - Cost: [Estimate governance/admin effort]
      - Impact: Immediate
      - ROI: Very high

# Quick Deep Extraction
"提取本合同中的所有 [provision type]。
Show: section, exact language, obligations, conditions."

# Quick Risk Assessment
"将每个条款评为 RED/YELLOW/GREEN。
Show: area, risk level, deviation, negotiation priority."

# Quick Portfolio Insights
"比较 [N] 份合同中的 [provision]。
Show: variations, standardization opportunity, best version."

# Quick Obligation Tracking
"提取所有义务，并列示：due date, owner, SLA target, penalty."

# Quick Efficiency Analysis
"This deal took [N] days. What took longest?
Show: phase breakdown, bottleneck, improvement ideas."