The Contract Negotiation Brief

You spot problematic clauses but struggle to articulate exactly what changes you want and why. Your lawyer charges premium rates just to draft alternative wording you could propose yourself.

That is the gap this drop closes. It is a finance & admin skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.

Who should use it

Business owners and managers who negotiate contracts regularly and need to prepare counter-proposals quickly

How it works

The skill file does five things, in this order.

1. Upload the contract draft. Paste the full contract text or upload the PDF into Claude and identify which party you represent.

2. Request a clause-by-clause assessment. Ask Claude to list every clause that creates imbalance, caps your rights, or shifts risk unfairly to your side.

3. Generate alternative language. For each problem clause, ask for two or three alternative wordings with explanations of how each protects you differently.

4. Build a fallback position. Ask Claude to rank your proposed changes by importance so you know what to concede if the other party pushes back.

5. Draft your response email. Have Claude write a professional email listing your requested amendments with business justifications, not legal jargon.

What comes back

A structured negotiation document that shows exactly what you want changed, why it matters commercially, and where you can compromise

The mistake to avoid

Save Claude's output as a template for similar contract types you see often. When the same vendor sends a new agreement, you already have tested language ready to propose.

Running it

Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.

Where this fits

On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.

In the file

I represent {our_company_name} and have received the attached contract from {other_party_name} for {contract_purpose}.

Please analyze this contract and provide:

1. A list of all clauses that create imbalance or unfairly shift risk to my side, organized by contract section

2. For each problematic clause:
   - Quote the original text
   - Explain the commercial risk it creates for me
   - Provide 2-3 alternative wordings that better protect my interests
   - Note whether this is a critical issue or a nice-to-have improvement

3. A prioritized list of amendments, ranking them as:
   - Must have (deal-breakers)
   - Should have (significant risk reduction)
   - Could have (minor improvements)

4. A professional email I can send to {other_party_name} that:
   - Thanks them for the draft
   - Lists my requested changes with business justifications
   - Maintains a collaborative tone
   - Suggests next steps

Focus on practical business concerns, not theoretical legal perfection. I want amendments that are reasonable to request and likely to be accepted.