Here are the main contractor-unfriendly clauses, why they’re risky, and concrete redlines you should consider. This is business/legal information, not legal advice; for an actual engagement, a lawyer in the relevant jurisdiction should review it.

High-risk clauses

1. Scope: unilateral scope changes without added compensation

Current language

Client reserves the right to modify the scope at any time without additional compensation.

Why this is dangerous

• Lets the client expand work indefinitely while keeping the same budget/rate.
• Creates “scope creep” with no mechanism for schedule, pricing, or resource adjustments.
• Makes it hard to prove what was actually agreed.

Suggested revision Replace with:

Contractor shall provide the services described in one or more statements of work (“SOWs”). Any material change to scope, deliverables, timeline, assumptions, or dependencies must be agreed in writing by both parties through a change order. Contractor will be entitled to equitable adjustment of fees, milestones, and delivery dates for approved changes.

Legal/business reasoning

• A contract should define consideration on both sides. If one party can unilaterally increase obligations without more pay, it becomes highly imbalanced and invites disputes.
• Written change orders create objective evidence of scope and pricing.

---

2. Payment: 90-day terms and subjective withholding

Current language

Payment is due within 90 days of invoice receipt. Client may withhold payment if deliverables are deemed "unsatisfactory" at Client's sole discretion.

Why this is dangerous

• 90 days is very long for an individual contractor/consultant.
• “Unsatisfactory” at sole discretion is completely subjective and can be used to avoid paying for work already performed.
• No acceptance procedure, no cure period, no obligation to identify defects.
• Could let client withhold all payment, even for unrelated or partially completed work.

Suggested revision Replace with:

Contractor shall be paid $150/hour, invoiced monthly, with payment due within 15 or 30 days of invoice receipt. Any disputed invoice amount must be identified in writing with reasonable detail within 10 business days; undisputed amounts shall be paid on time. Client may withhold only the disputed portion relating to a material, objectively verifiable failure to conform to agreed specifications. Contractor shall have a reasonable opportunity, not less than 10 business days, to cure any nonconformity.

Add:

Late payments shall accrue interest at the lesser of 1.0% per month or the maximum amount permitted by law.

Optional:

Contractor may suspend work for invoices more than 15 days overdue after written notice.

Legal/business reasoning

• Payment clauses should tie acceptance to objective criteria, not unilateral preference.
• Partial dispute/partial payment language prevents using one issue to block all compensation.
• Cure rights reduce opportunistic nonpayment.

---

3. IP: grabs pre-existing IP and all tools/methodologies

Current language

All work product, including any tools, libraries, or methodologies developed during the engagement, shall be the exclusive property of Client in perpetuity, including any work created using Contractor's pre-existing IP.

Why this is dangerous

• It appears to transfer the contractor’s pre-existing IP to the client.
• It may give away reusable know-how, frameworks, scripts, templates, libraries, and generalized methods.
• Could prevent the contractor from using their own tools in future projects.
• “In perpetuity” and “including any work created using Contractor’s pre-existing IP” is especially broad.

Suggested revision Replace with:

Contractor retains all right, title, and interest in and to Contractor’s pre-existing materials, tools, code, libraries, templates, know-how, methodologies, and other intellectual property developed independently of this Agreement (“Contractor IP”). To the extent Contractor IP is incorporated into deliverables, Contractor grants Client a non-exclusive, perpetual, worldwide, non-transferable (except with assignment of this Agreement), royalty-free license to use such Contractor IP solely as embedded in or necessary to use the deliverables.

And:

Upon full payment of all fees due, Contractor assigns to Client all right, title, and interest in the final deliverables specifically created for Client under an applicable SOW, excluding Contractor IP, generic know-how, residual knowledge, and third-party materials.

If open source or third-party code may be used:

Deliverables may include third-party or open-source components subject to their applicable licenses.

Legal/business reasoning

• Standard practice is: client owns custom deliverables; contractor retains background IP and grants a license as needed.
• Without this distinction, the contractor can accidentally transfer core business assets.

---

4. Non-compete: broad industry ban for 24 months

Current language

Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination.

Why this is dangerous

• Overly broad in duration, geography, and restricted activity.
• Can block the contractor from earning a living.
• In many jurisdictions, non-competes are heavily restricted or unenforceable, especially against independent contractors, but defending against them is still costly.

Suggested revision Best option:

Delete the non-compete entirely.

Replace with a narrower non-solicit/confidentiality clause:

For 12 months following termination, Contractor shall not knowingly solicit for employment any employee of Client with whom Contractor had direct material contact during the engagement, provided that general solicitations not targeted at Client employees shall not violate this provision.

And rely on confidentiality:

Contractor shall not use or disclose Client confidential information to compete unfairly.

Legal/business reasoning

• Courts are more likely to enforce reasonable confidentiality and non-solicitation clauses than sweeping industry-wide non-competes.
• “Same industry” is vague and overbroad.

---

5. Termination: one-sided notice and free handover

Current language

Client may terminate this agreement at any time without notice. Contractor must provide 60 days written notice. Upon termination, Contractor must immediately deliver all work in progress without additional compensation.

Why this is dangerous

• Client can cut off work instantly, but contractor is locked in for 60 days.
• Contractor may have reserved time and turned away other work.
• “Deliver all work in progress without additional compensation” suggests no payment for unfinished but performed work.
• No wind-down fees, no payment for committed time, no reimbursement of approved expenses.

Suggested revision Replace with:

Either party may terminate this Agreement for convenience upon 15 or 30 days’ written notice.

And:

Either party may terminate for material breach if the breach is not cured within 10 or 15 days after written notice.

Add:

Upon termination, Client shall pay Contractor for all services performed, approved expenses incurred, and any non-cancellable commitments made through the effective date of termination. Contractor shall deliver work product for which payment has been made.

Optional if you work on retainer/reserved capacity:

If Client terminates for convenience, Client shall pay for any reserved minimum commitment for the notice period.

Legal/business reasoning

• Mutual termination rights are more balanced.
• Payment should track value already provided.
• Delivery should generally correspond to paid work, not unpaid work in progress.

---

6. Liability: unlimited liability including consequential damages

Current language

Contractor assumes all liability for any bugs, security vulnerabilities, or system failures in delivered software, including consequential damages, with no cap on liability.

Why this is dangerous

• Software can never be guaranteed bug-free.
• Consequential damages can be enormous: lost profits, downtime, reputational harm, customer claims.
• No cap means personal financial ruin exposure.
• Liability for “any bugs” is much broader than negligence or breach.

Suggested revision Replace with:

Contractor’s total aggregate liability arising out of or related to this Agreement shall not exceed the total fees paid or payable to Contractor under this Agreement during the 6 or 12 months preceding the event giving rise to the claim.

Add:

In no event shall either party be liable for any indirect, incidental, special, exemplary, punitive, or consequential damages, including lost profits, lost revenue, loss of data, or business interruption, even if advised of the possibility of such damages.

Carve-outs can be negotiated:

The foregoing limitations shall not apply to liability arising from gross negligence, willful misconduct, fraud, or breach of confidentiality obligations, and only to the extent such carve-outs are required by applicable law.

Also avoid warranty overreach:

Contractor warrants that services will be performed in a professional and workmanlike manner consistent with generally accepted industry standards. Contractor does not warrant that deliverables will be error-free or uninterrupted.

Legal/business reasoning

• Limitation of liability and exclusion of consequential damages are standard risk-allocation tools.
• Tying liability to recent fees keeps risk proportional to contract value.

---

7. Indemnification: regardless of fault

Current language

Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault.

Why this is dangerous

• “Regardless of fault” means you indemnify even if the client caused the issue.
• “All claims arising from Contractor’s work” is nearly limitless.
• Could cover client modifications, misuse, specs provided by client, or combined systems.

Suggested revision Replace with:

Contractor shall indemnify Client against third-party claims to the extent arising from allegations that the deliverables, as provided by Contractor and used as permitted under this Agreement, infringe such third party’s intellectual property rights, or from Contractor’s gross negligence or willful misconduct.

Add exclusions:

Contractor shall have no indemnity obligation to the extent a claim arises from (i) Client materials, specifications, or instructions; (ii) modifications not made by Contractor; (iii) use of deliverables in combination with items not provided or approved by Contractor; (iv) use not in accordance with the Agreement or documentation.

Add procedure:

The indemnified party must promptly notify the indemnifying party of the claim, provide reasonable cooperation, and permit the indemnifying party sole control of the defense and settlement, except that no settlement admitting liability or imposing obligations on the indemnified party may be entered without its consent.

Consider mutual indemnity:

Client shall indemnify Contractor for third-party claims arising from Client-provided materials, instructions, data, or Client’s use of deliverables outside the agreed scope.

Legal/business reasoning

• Indemnities should be narrow, fault-based, and procedural.
• IP infringement indemnity is common; blanket indemnity for all claims is not.

---

8. Confidentiality: too broad, no carve-outs

Current language

Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination.

Why this is dangerous

• Covers “any information,” potentially including non-confidential facts.
• No standard exclusions for publicly known info, independently developed info, prior knowledge, or legally compelled disclosure.
• Prevents even limited disclosure to accountants, lawyers, insurers, or as required by law.
• Hiding contract terms may impair fee collection or legal enforcement.

Suggested revision Replace with:

Contractor shall keep Client’s non-public confidential information confidential and use it solely to perform services under this Agreement. “Confidential Information” does not include information that is or becomes public through no fault of Contractor, was already known to Contractor without restriction, is independently developed without use of Client confidential information, or is rightfully obtained from a third party without duty of confidentiality.

Add:

Contractor may disclose Confidential Information to its legal, tax, accounting, and insurance advisors under obligations of confidentiality, and as required by law, regulation, court order, or legal process, provided Contractor gives prompt notice where legally permitted.

Limit publicity separately if needed:

Contractor may identify Client’s name and logo in a client list only with Client’s prior written consent.

About term:

• 3 years is common for general confidential info.
• Trade secrets can be protected as long as they remain trade secrets.

Suggested term:

The confidentiality obligations shall continue for 3 years after termination, except with respect to trade secrets, which shall remain protected for so long as they qualify as trade secrets under applicable law.

Legal/business reasoning

• Confidentiality needs carve-outs to be workable and enforceable.
• Trade secret treatment is often separate from ordinary confidential information.

---

9. Dispute resolution: client’s home forum and loser pays

Current language

Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party.

Why this is dangerous

• Forces the contractor to arbitrate on the client’s turf, increasing cost and leverage.
• “Losing party pays” can deter valid claims, especially over unpaid invoices.
• No carve-out for injunctive relief or small claims.
• No rules, venue details, number of arbitrators, or governing law.

Suggested revision Replace with:

Any dispute arising under this Agreement that the parties cannot resolve informally shall be resolved by binding arbitration administered by [AAA/JAMS] under its commercial rules by a single arbitrator. The arbitration shall take place remotely or in a mutually agreed location. Each party shall bear its own attorneys’ fees and costs, except as awarded by the arbitrator under applicable law or for bad-faith conduct.

Optional:

Either party may seek temporary injunctive relief in a court of competent jurisdiction to protect confidential information or intellectual property.

And:

Either party may bring claims for unpaid invoices or other matters within the jurisdictional limit of small claims court.

Legal/business reasoning

• Neutral venue and cost allocation reduce strategic pressure.
• A small-claims carve-out is useful for collection matters.

---

Additional issues not expressly addressed

10. No acceptance criteria

There’s no objective delivery/acceptance mechanism.

Fix Add:

Deliverables shall be deemed accepted unless Client provides written notice of material nonconformity to agreed specifications within 5 business days of delivery. The notice must describe the nonconformity in reasonable detail, and Contractor shall have a reasonable opportunity to cure.

Reason

• Prevents indefinite “not accepted yet” tactics.

---

11. No expense reimbursement terms

If you incur travel, tools, cloud costs, or licenses, there’s no protection.

Fix Add:

Client shall reimburse pre-approved out-of-pocket expenses at cost, invoiced monthly with reasonable documentation.

---

12. No dependency/assumption protection

Client delays or missing inputs could be blamed on contractor.

Fix Add:

Contractor’s performance is dependent on Client’s timely provision of access, materials, approvals, decisions, and personnel reasonably required for the services. Delivery dates will be equitably extended for delays caused by Client or third parties under Client’s control.

---

13. No status clarification for independent contractor

Important for tax, benefits, and control issues.

Fix Add:

Contractor is an independent contractor and not an employee, partner, or agent of Client. Contractor is solely responsible for taxes, insurance, and statutory obligations relating to its personnel.

Reason

• Helps avoid misclassification arguments, though actual relationship matters too.

---

14. No warranty limitation around security

The current language could imply absolute security obligations.

Fix Add:

Contractor will use commercially reasonable efforts consistent with industry standards but does not guarantee that software will be free from all vulnerabilities or that operation will be uninterrupted. Security obligations, if any, shall be expressly stated in the applicable SOW.

---

15. No force majeure

You may want protection for events outside your control.

Fix Add:

Neither party shall be liable for delays or failures caused by events beyond its reasonable control, excluding payment obligations.

---

Most important redlines to insist on

If you can only negotiate a few items, prioritize these:

1. Delete unilateral scope changes without added compensation
2. Shorten payment terms to 15–30 days and remove sole-discretion withholding
3. Protect pre-existing IP and reusable tools/methods
4. Delete the non-compete
5. Make termination mutual and require payment for work performed
6. Add liability cap and exclude consequential damages
7. Narrow indemnity to IP infringement / gross negligence / willful misconduct
8. Make arbitration venue neutral and remove automatic loser-pays

---

Example of a more balanced fallback position

If the client resists, a practical compromise might be:

• Scope changes only via written change order
• Net 30 payment
• Client may dispute only specific amounts in good faith
• Client owns paid-for custom deliverables
• Contractor retains background IP, grants embedded license
• Replace non-compete with confidentiality + employee non-solicit
• Either side can terminate on 15 days’ notice
• Contractor paid for all time worked through termination
• Liability cap = fees paid in prior 12 months
• No consequential damages
• Mutual confidentiality
• Narrow, fault-based indemnities
• Arbitration remote or mutually agreed venue

If you want, I can also turn this into a line-by-line redline draft of the agreement with replacement wording for each clause.