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/objection_handling.md
View on GitHub# Objection Handling Framework for Technology Contract Negotiation
Five-tier objection handling methodology with real examples, prediction matrices by client type, communication templates, and common negotiation mistakes.
## Table of Contents
- [Five-Tier Methodology](#five-tier-methodology)
- [Objection Prediction Matrix](#objection-prediction-matrix)
- [Communication Templates](#communication-templates)
- [Common Negotiation Mistakes](#common-negotiation-mistakes)
## Five-Tier Methodology
Every objection response follows the same five-tier escalation. Start at Tier 1 and escalate only as needed. Most objections resolve at Tier 2 or 3.
### Tier 1: Acknowledge
**Purpose:** Demonstrate that you heard and understand the concern. Build rapport. Never dismiss.
**Technique:** Restate the objection in your own words. Show you understand the business reason behind it.
**Example:**
> "I understand your concern about the liability cap. Given that this service will process your customer payment data, it's reasonable that you'd want stronger protection against potential data breaches."
**When to use:** Always. Every objection response starts here.
| Do | Don't |
|----|-------|
| Restate the specific concern | Jump straight to your counter-position |
| Reference the business context | Say "that's standard" or "everyone signs this" |
| Show genuine understanding | Minimize or dismiss the concern |
### Tier 2: Market Context
**Purpose:** Frame your position within industry norms and market practice. Reduce the sense that your terms are unusual.
**Technique:** Reference market standards, industry benchmarks, and comparable deals without revealing specific counterparty names.
**Example:**
> "The liability cap we've proposed -- 12 months of fees -- is consistent with what we see across the enterprise SaaS market. Gartner's most recent report on cloud contracts notes that 12-24 month fee caps represent the standard range for services at this tier."
**When to use:** When the objection targets your position as unreasonable or non-standard.
| Provision | Market Context Data Points |
|-----------|---------------------------|
| Liability cap | 12-24 months fees is standard SaaS range |
| Uptime SLA | 99.9% is standard; 99.99% is premium/enterprise |
| Payment terms | Net 30 is standard B2B; Net 60+ is enterprise |
| Warranty period | 12 months is standard; 90 days for bug fixes |
| IP ownership | Provider retains platform IP; client owns bespoke is standard |
### Tier 3: Business Rationale
**Purpose:** Explain why your position exists from a business perspective. Connect terms to pricing, service quality, or sustainability.
**Technique:** Show the economic logic. Link specific terms to the deal economics.
**Example:**
> "The reason we cap liability at 12 months of fees is that our pricing model is built on that risk allocation. If we were to accept unlimited liability for consequential damages, we'd need to purchase additional insurance coverage, which would increase the annual fee by approximately 15-20%. We're happy to discuss that trade-off if it's important to you."
**When to use:** When market context alone doesn't resolve the objection. This tier is the most effective for educated counterparties.
### Tier 4: Alternatives
**Purpose:** Offer concrete trade-offs. Show flexibility without conceding your core position.
**Technique:** Present 2-3 alternative structures that address the concern while protecting your interests.
**Example:**
> "I'd like to propose three alternatives that address your liability concern:
> 1. **Super-cap structure:** We maintain the 12-month general cap but create a separate, higher cap (2x annual fees) specifically for data breach and confidentiality claims.
> 2. **Insurance backstop:** We increase our cyber insurance to $10M and name your company as an additional insured, while keeping the contractual cap at 12 months.
> 3. **Tiered pricing:** We remove the cap for data breach claims but adjust the annual fee by 12% to reflect the additional risk we're assuming."
**When to use:** When the counterparty has a legitimate business need that your standard position doesn't address.
### Tier 5: Bright Lines
**Purpose:** Clearly communicate non-negotiable positions with respect and finality.
**Technique:** State the bright line, explain why it exists, and confirm what you can do within those boundaries.
**Example:**
> "I appreciate the discussion on this point, and I want to be transparent: unlimited liability without any cap is a position we cannot accept. It's a board-level policy that applies across all our enterprise agreements. What I can do is work with you on the super-cap structure to ensure meaningful protection for data breach and IP claims. Would that approach work for you?"
**When to use:** Only when a true organizational constraint exists. Overuse destroys credibility.
| Typical Bright Lines | Rationale |
|---------------------|-----------|
| No unlimited liability (general) | Existential risk to provider; uninsurable |
| No penalties exceeding 100% of fees | Makes the deal unprofitable |
| No assignment of background IP | Core platform value; affects all clients |
| No audit rights into source code (non-escrow) | Trade secret protection |
| No unilateral termination for convenience without payment | Revenue certainty |
## Objection Prediction Matrix
Predict which objections to expect based on client type and industry sector.
### By Client Type
| Provision | Enterprise (F500) | Mid-Market | Startup | Government |
|-----------|-------------------|------------|---------|------------|
| Liability cap | Push for uncapped/high cap | Accept balanced cap | Often accept standard | Uncapped; statutory requirements |
| IP ownership | Demand bespoke ownership | Negotiate per project | Flexible | Government owns all |
| Payment terms | Net 60-90 | Net 30-45 | Net 30; may need flexibility | Net 30-60; PO-based |
| SLAs | 99.99% with financial penalties | 99.9% with service credits | 99.9% acceptable | Strict SLAs; liquidated damages |
| Warranties | Extended; fitness for purpose | Standard 12-month | Flexible | Extended; compliance warranties |
| Data protection | GDPR-plus; DPA required | Standard DPA | Basic compliance | Sovereignty requirements |
| Audit rights | Full audit rights; annual minimum | Annual audit right | Rarely requested | Unlimited audit rights |
| Termination | Termination for convenience | Mutual convenience | Mutual convenience | Government convenience; no provider convenience |
### By Industry Sector
| Provision | Financial Services | Healthcare | Technology | Manufacturing | Government |
|-----------|-------------------|------------|------------|---------------|------------|
| Top concern | Data security, regulatory | HIPAA, PHI | IP ownership | Supply chain | Sovereignty |
| Liability focus | Regulatory fines coverage | PHI breach liability | IP infringement | Product liability | Statutory compliance |
| Regulatory leverage | DORA, SOX, PCI DSS | HIPAA, HITECH | GDPR (data) | Product safety | FedRAMP, ITAR |
| SLA priority | Availability, RPO/RTO | Uptime, data integrity | Performance, scalability | Delivery timelines | Availability, accessibility |
| Expected difficulty | High | High | Moderate | Moderate | Very High |
| Typical rounds | 5-8 | 4-6 | 3-5 | 3-4 | 8-12 |
## Communication Templates
### Template 1: Opening Position Statement
Use when presenting your initial position on a marked-up contract.
> Subject: [Company] / [Provider] -- Contract Discussion: Initial Position
>
> Dear [Name],
>
> Thank you for sharing the draft [Agreement Type]. We've completed our review and have a few areas where we'd like to discuss alignment.
>
> **Summary of our position:**
> We're aligned on the majority of the terms. We've identified [N] provisions where we'd like to discuss adjustments, and [M] areas where we have questions for clarification.
>
> **Key discussion items:**
> 1. [Provision 1] -- [One-sentence summary of your position]
> 2. [Provision 2] -- [One-sentence summary of your position]
> 3. [Provision 3] -- [One-sentence summary of your position]
>
> We've attached a marked-up version with our proposed changes. We're available to discuss these at your convenience and are confident we can reach terms that work for both parties.
>
> Best regards,
> [Name]
### Template 2: Responding to Aggressive Demands
Use when the counterparty's position is significantly more aggressive than expected.
> Dear [Name],
>
> Thank you for sharing your position on [specific provision]. I want to make sure I fully understand the business concern driving this request.
>
> As I understand it, your primary concern is [restate their concern]. Is that accurate?
>
> For context, the position we've proposed is consistent with market practice for [deal type] of this size and scope. [Cite specific market data point if available.]
>
> That said, I recognize that your [specific business context -- e.g., regulatory environment, service criticality] may warrant a different approach. I'd like to propose we schedule a call to discuss [2-3 specific alternatives you can offer].
>
> Would [date/time] work for a 30-minute discussion?
>
> Best regards,
> [Name]
### Template 3: Proposing Trade-Offs
Use when offering a concession in exchange for something.
> Dear [Name],
>
> Following our discussion on [date], I'd like to propose a package that addresses both parties' priorities:
>
> **We're prepared to:**
> - [Concession 1 -- be specific]
> - [Concession 2 -- be specific]
>
> **In exchange, we'd ask for:**
> - [Counter-request 1 -- be specific]
> - [Counter-request 2 -- be specific]
>
> This approach addresses your concern about [their key issue] while ensuring [your key interest] is protected. I believe this represents a fair balance.
>
> Shall we schedule a call to discuss, or would you prefer to respond in writing?
>
> Best regards,
> [Name]
### Template 4: Drawing Bright Lines
Use when communicating a non-negotiable position.
> Dear [Name],
>
> I appreciate the constructive dialogue we've had on [provision]. I want to be transparent about where we stand.
>
> After careful internal review, [specific position] represents a firm policy position that we apply consistently across all our [enterprise/strategic] agreements. This is driven by [brief rationale -- e.g., insurance constraints, board policy, regulatory requirements].
>
> What I can offer is [maximum flexibility within your constraint]. Specifically:
> - [Alternative 1]
> - [Alternative 2]
>
> I'm confident one of these approaches can address the substance of your concern. I'd welcome the opportunity to discuss which option works best for your team.
>
> Best regards,
> [Name]
### Template 5: Closing the Deal
Use when agreement is near and you want to lock down remaining items.
> Dear [Name],
>
> Great progress on our discussions. I believe we're very close to final terms. Here's my summary of where we stand:
>
> **Agreed items:** [List resolved provisions]
>
> **Remaining items (proposed resolution):**
> 1. [Item] -- We propose [specific resolution]
> 2. [Item] -- We propose [specific resolution]
>
> If you're aligned on these final points, I'd suggest we move to execution copies. Our target is to have signatures by [date].
>
> Please confirm whether you're comfortable with the above, or let me know if there are any remaining concerns I've missed.
>
> Best regards,
> [Name]
## Common Negotiation Mistakes
| # | Mistake | Impact | Fix |
|---|---------|--------|-----|
| 1 | Opening with your bottom line | No room to negotiate; counterparty assumes there's more | Start with your aspirational position (one tier more favorable than your target) |
| 2 | Negotiating provisions in isolation | Conceding on SLAs without linking to liability creates exposure | Always negotiate related provisions as a package (SLAs + credits + liability) |
| 3 | Treating "standard template" as non-negotiable | Leaves value on the table; every template is negotiable | Analyze the template objectively; mark up based on your position, not theirs |
| 4 | Making concessions without getting something in return | Sets expectation of one-way movement; weakens future positions | Always frame concessions as trades: "We can move on X if you can move on Y" |
| 5 | Escalating to Bright Lines too early | Credibility damage; counterparty stops engaging | Reserve Bright Lines for truly non-negotiable items; use Alternatives tier first |
| 6 | Failing to document concession rationale | Loses institutional knowledge; repeats mistakes | Maintain a concession log: what was traded, why, and what was received |
| 7 | Letting internal stakeholders negotiate directly | Inconsistent positions; unauthorized concessions; loss of control | Single point of contact for all external communication; brief stakeholders separately |
| 8 | Ignoring the counterparty's internal constraints | Demands that their negotiator cannot deliver create deadlock | Ask: "Is there a way to structure this that works within your approval framework?" |
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 |