borghei/Claude-Skills / legal/tech-contract-negotiation
tech-contract-negotiation
VerifiedNegotiation frameworks for technology services agreements, B2B contracts, and professional services deals. Use when reviewing or negotiating tech contracts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.3 KB |
| references/objection_handling.md | markdown | 12.8 KB |
| references/regulatory_leverage.md | markdown | 15.2 KB |
| references/three_position_framework.md | markdown | 14.5 KB |
| scripts/deal_complexity_scorer.py | script | 13.3 KB |
| scripts/negotiation_position_analyzer.py | script | 15.9 KB |
references/regulatory_leverage.md
View on GitHub# Regulatory Leverage in Technology Contract Negotiation
How to use regulatory requirements as negotiation leverage, with framework-specific arguments, the genuine-vs-preference test, concession roadmap, and industry-specific considerations.
## Table of Contents
- [Overview](#overview)
- [GDPR / Data Protection](#gdpr--data-protection)
- [DORA / Financial Services](#dora--financial-services)
- [NIS2 / Critical Infrastructure](#nis2--critical-infrastructure)
- [SOX / Financial Reporting](#sox--financial-reporting)
- [The Genuine-vs-Preference Test](#the-genuine-vs-preference-test)
- [Concession Roadmap](#concession-roadmap)
- [Industry-Specific Considerations](#industry-specific-considerations)
## Overview
Regulatory requirements create legitimate, evidence-backed negotiation leverage. When a client's industry mandates specific contractual provisions, those requirements are non-discretionary -- the provider must accommodate them or lose the deal. However, distinguishing genuine regulatory mandates from risk preferences presented as mandates is critical to maintaining credibility.
**Key Principle:** Use regulation as a framework for discussion, not a weapon. Informed counterparties will challenge dubious regulatory claims, destroying trust.
## GDPR / Data Protection
### Client Demands with Justification
| Demand | GDPR Basis | Article |
|--------|-----------|---------|
| Data Processing Agreement (DPA) | Mandatory for controller-processor relationships | Art. 28 |
| Sub-processor notification and approval | Controller must authorize sub-processing | Art. 28(2) |
| Data breach notification within 72 hours | Controller must notify supervisory authority | Art. 33 |
| Right to audit processor | Controller must ensure compliance verification | Art. 28(3)(h) |
| Data deletion on termination | Processor must delete/return data | Art. 28(3)(g) |
| Data transfer impact assessment | Required for transfers outside EEA | Art. 46 |
| Records of processing activities | Both controller and processor obligations | Art. 30 |
| Data Protection Impact Assessment support | Processor must assist controller | Art. 35-36 |
### Provider Responses
| Demand | Reasonable Response | Pushback Threshold |
|--------|--------------------|--------------------|
| DPA | Accept; use your standard DPA template | Never push back -- it's mandatory |
| Sub-processor approval | Right to object with switching assistance | Blanket veto right is excessive |
| Breach notification | 72 hours to client; client handles authority | 24-hour notification is aggressive but common |
| Audit rights | Annual audit right; accept SOC 2 as alternative | Unlimited on-site access is excessive |
| Data deletion | 30-day deletion with certification | Immediate deletion may not be technically feasible |
| Data transfers | Standard Contractual Clauses + TIA | Requiring data residency may increase costs |
| DPIA support | Reasonable assistance at provider's cost | Client cannot outsource entire DPIA to provider |
### Genuine vs. Preference Assessment
| Claim | Genuine Requirement | Risk Preference |
|-------|--------------------|-----------------|
| "We need a DPA" | Yes -- Art. 28 mandate | N/A |
| "We need 24-hour breach notification" | Partially -- 72 hours is the legal requirement | 24 hours is preference beyond legal minimum |
| "We need data residency in EU" | Depends -- adequate if SCCs are in place | Preference unless specific national law requires it |
| "We need to approve all sub-processors" | Yes -- Art. 28(2) requires authorization | General authorization with objection right is sufficient |
## DORA / Financial Services
### Client Demands with Justification
| Demand | DORA Basis | Article |
|--------|-----------|---------|
| ICT risk management provisions | Financial entities must manage ICT third-party risk | Art. 28 |
| Contractual right to audit ICT provider | Mandatory for critical ICT providers | Art. 28(2)(e) |
| Exit strategy and transition plan | Required in all ICT service contracts | Art. 28(2)(h) |
| Sub-contracting notification | Must be notified of material sub-contracting | Art. 28(2)(a) |
| Incident reporting support | ICT providers must report major incidents | Art. 19 |
| Business continuity testing | Threat-led penetration testing requirements | Art. 26-27 |
| Regulatory access | Regulators must be able to access/audit provider | Art. 28(2)(e) |
| Service level definitions | Clear performance metrics required | Art. 28(2)(b) |
### Provider Responses
| Demand | Reasonable Response | Pushback Threshold |
|--------|--------------------|--------------------|
| Audit rights | Annual audit; pooled audit model for efficiency | Unlimited audits at provider cost is excessive |
| Exit plan | 12-month transition assistance; data portability | Mandating specific competitor migration is excessive |
| Incident reporting | 24-hour notification for major incidents | Real-time notification for all incidents is excessive |
| Penetration testing | Annual TLPT; share results under NDA | Client-directed pen testing of provider infrastructure is excessive |
| Regulatory access | Facilitate regulator access within reasonable notice | Open-ended regulatory access without notice is excessive |
## NIS2 / Critical Infrastructure
### Client Demands with Justification
| Demand | NIS2 Basis | Article |
|--------|-----------|---------|
| Supply chain security measures | Entities must address supply chain risk | Art. 21(2)(d) |
| Incident reporting within 24 hours | Early warning within 24 hours; report within 72 | Art. 23 |
| Cybersecurity risk management measures | 10 minimum security measures required | Art. 21(2) |
| Vulnerability handling and disclosure | Required cybersecurity hygiene practice | Art. 21(2)(e) |
| Business continuity and crisis management | Backup, disaster recovery, crisis management | Art. 21(2)(c) |
| Encryption and cryptography policies | Basic cyber hygiene including encryption | Art. 21(2)(h) |
| Access control and asset management | Multi-factor authentication, access management | Art. 21(2)(i-j) |
### Provider Responses
| Demand | Reasonable Response | Pushback Threshold |
|--------|--------------------|--------------------|
| Supply chain security | Share SOC 2 + security certifications | Requiring provider to audit their sub-suppliers is excessive |
| Incident reporting | 24-hour early warning; 72-hour detailed report | 1-hour notification for all security events is excessive |
| Encryption | Encrypt at rest and in transit; document standards | Mandating specific encryption algorithms limits flexibility |
| MFA | Enforce MFA for all access to client data | MFA for all internal provider systems is excessive |
## SOX / Financial Reporting
### Client Demands with Justification
| Demand | SOX Basis | Section |
|--------|----------|---------|
| Internal controls over financial reporting | ICFR requirements extend to outsourced processes | Section 404 |
| Audit trail and logging | Must maintain audit trails for financial data | Section 302/404 |
| Segregation of duties | Controls must prevent unauthorized access | Section 404 |
| Change management controls | Changes to financial systems must be controlled | Section 404 |
| Access controls | Limit access to financial data and systems | Section 404 |
### Provider Responses
| Demand | Reasonable Response | Pushback Threshold |
|--------|--------------------|--------------------|
| Audit trails | 7-year retention; immutable logs | Client dictating specific logging technology is excessive |
| SOD controls | Demonstrate SOD in SOC 1 Type II report | Client designing provider's internal control structure is excessive |
| Change management | ITIL-compliant change management | Client approval of all provider system changes is excessive |
## The Genuine-vs-Preference Test
Before citing a regulation as leverage, apply this three-part test:
### Test 1: Does the regulation actually require this specific provision?
| Question | If Yes | If No |
|----------|--------|-------|
| Is there a specific article mandating this exact term? | Genuine requirement -- cite the article | May be an interpretation or preference |
| Does the regulation specify the exact standard (e.g., 72 hours)? | Use the exact standard as baseline | The standard is negotiable |
| Is there regulatory guidance or enforcement precedent? | Reference the guidance | Position is less certain |
### Test 2: Is this the minimum compliance standard or gold-plated?
| Indicator | Genuine Minimum | Gold-Plated |
|-----------|----------------|-------------|
| Matches regulatory text exactly | Yes | N/A |
| Exceeds regulatory text (shorter timelines, broader scope) | N/A | Yes -- acknowledge as preference |
| Required by industry-specific guidance beyond the regulation | Genuine if guidance is binding | Preference if guidance is advisory |
### Test 3: Would a regulator actually enforce this interpretation?
| Evidence | Strength |
|----------|----------|
| Enforcement action on this exact issue | Strong -- cite the case |
| Regulatory guidance specifically addressing this | Moderate -- reference guidance |
| Industry association recommendation | Weak -- present as best practice, not mandate |
| Internal legal opinion only | Very weak -- present as risk position, not requirement |
**Decision Framework:**
| Test 1 | Test 2 | Test 3 | Classification | Approach |
|--------|--------|--------|---------------|----------|
| Yes | Minimum | Strong | Genuine Requirement | Non-negotiable; cite regulation |
| Yes | Gold-plated | Strong | Genuine + Preference | Negotiate to minimum; gold-plating is optional |
| Yes | Minimum | Weak | Likely Genuine | Cite regulation; acknowledge enforcement uncertainty |
| No | N/A | N/A | Risk Preference | Be transparent; frame as "our risk position" |
## Concession Roadmap
Four tiers of concessions, from easy gives to absolute bright lines. Trade concessions strategically -- never give without getting.
### Tier 1: Easy Gives (Concede Early for Goodwill)
Low-cost concessions that signal flexibility and build trust.
| Concession | Cost to Provider | Value to Client |
|-----------|-----------------|-----------------|
| Extend warranty from 90 days to 12 months | Minimal (if quality is good) | High perceived value |
| Add force majeure detail (pandemic, cyberattack) | Minimal (mutual) | Moderate -- reduces ambiguity |
| Provide quarterly SLA reports instead of annual | Low (automate) | Moderate -- transparency |
| Accept client's DPA template vs. your own | Low (if substantively similar) | Moderate -- reduces their review time |
| Add notice period before price increase (90 days) | Low | Moderate -- planning time |
| Include basic data deletion certification | Low | Moderate -- compliance evidence |
### Tier 2: Moderate Concessions (Trade for Counter-Value)
Meaningful concessions that should be traded for something in return.
| Concession | Trade For |
|-----------|-----------|
| Increase liability cap from 12 to 24 months | Longer initial term or volume commitment |
| Add super-cap for data breach claims | Higher annual fee (5-10% premium) or extended term |
| Improve SLA from 99.5% to 99.9% | Higher fees or reduced service credit exposure |
| Shorten payment terms from Net 60 to Net 30 | Early payment discount (1-2%) |
| Grant annual audit right | Accept SOC 2 report as primary evidence; limit on-site to 1/year |
| Add termination for convenience right | Notice period (90+ days) and early termination fee |
### Tier 3: Significant Concessions (Requires Executive Approval)
High-value concessions that materially change the deal economics or risk profile.
| Concession | Conditions |
|-----------|-----------|
| Uncapped liability for data breach claims | Insurance backstop verified; premium reflected in pricing |
| Client ownership of all bespoke IP | License-back for general improvements; background IP retained |
| 99.99% uptime SLA with financial penalties | Premium pricing tier; dedicated infrastructure |
| Most-Favored-Customer pricing clause | Minimum volume commitment; multi-year term |
| Termination for convenience with 30 days notice | Pro-rated payment for work completed; wind-down costs covered |
| Full source code delivery (not escrow) | Restricted use license; confidentiality obligations |
### Tier 4: Bright Lines (Never Concede)
Positions that represent existential risk or fundamental business constraints.
| Bright Line | Rationale |
|------------|-----------|
| Unlimited general liability (no cap at all) | Existential risk; uninsurable |
| Assignment of background/platform IP | Destroys core business value |
| Unlimited penalty exposure exceeding contract value | Makes deal unprofitable by definition |
| Waiver of limitation of liability for gross negligence | Defeats the purpose of the liability framework |
| Unilateral regulatory compliance guarantee | Cannot guarantee future regulatory interpretations |
| Client control over provider's other client relationships | Anti-competitive; affects entire business |
## Industry-Specific Considerations
### Financial Services
| Factor | Impact on Negotiation |
|--------|----------------------|
| Regulatory environment | DORA, SOX, PCI DSS create strong client leverage |
| Audit expectations | Expect extensive audit rights; offer pooled audit model |
| Exit planning | Regulators require documented exit strategy -- concede early |
| Data sovereignty | Often require EEA data residency -- price accordingly |
| Incident reporting | 24-hour notification is becoming industry standard |
| Typical deal difficulty | High -- 5-8 rounds average |
### Healthcare
| Factor | Impact on Negotiation |
|--------|----------------------|
| Regulatory environment | HIPAA, HITECH create strong compliance leverage |
| BAA requirements | Business Associate Agreement is non-negotiable |
| PHI handling | Strict data handling requirements -- price accordingly |
| Breach liability | HIPAA penalties create strong indemnification demands |
| Audit requirements | HHS audit access may be required |
| Typical deal difficulty | High -- 4-6 rounds average |
### Government / Public Sector
| Factor | Impact on Negotiation |
|--------|----------------------|
| Regulatory environment | FedRAMP, ITAR, procurement regulations |
| Non-negotiable terms | Government terms often cannot be modified |
| IP ownership | Government typically owns all deliverables |
| Pricing | Fixed-price or cost-plus; limited flexibility |
| Audit rights | Unlimited government audit rights are standard |
| Typical deal difficulty | Very High -- 8-12 rounds average |
### Technology / Startups
| Factor | Impact on Negotiation |
|--------|----------------------|
| Regulatory environment | GDPR for data; less sector-specific regulation |
| IP sensitivity | Often the most contentious issue |
| Speed | Faster deal cycles; less bureaucracy |
| Flexibility | More creative deal structures possible |
| Payment | May need flexible payment terms (cash management) |
| Typical deal difficulty | Moderate -- 3-5 rounds average |
### Enterprise / Fortune 500
| Factor | Impact on Negotiation |
|--------|----------------------|
| Regulatory environment | Multiple overlapping frameworks |
| Procurement process | Formal RFP/RFI; structured evaluation |
| Template insistence | Will push their paper (client template) |
| Approval layers | Multiple internal approvals; long cycles |
| Volume | Large deal values justify extensive negotiation investment |
| Typical deal difficulty | High -- 5-8 rounds average |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |