This agreement is heavily client-favored. Every numbered clause has language that could be used against the contractor.
Short version: I would not sign it without major redlines to Clauses 1–9, especially 2, 3, 4, 5, 6, and 7.
Below is a clause-by-clause review. This is general contract/business analysis, not jurisdiction-specific legal advice; enforceability varies a lot by state/country, especially for non-competes, IP, and arbitration.
1. Scope
Problem language
“Contractor shall provide software development services as directed by Client. Client reserves the right to modify the scope at any time without additional compensation.”
Why this is exploitable
- Unlimited scope creep. Client can keep adding work.
- No objective statement of work. “As directed by Client” is vague.
- “Without additional compensation” is especially dangerous: it can be read as requiring extra work at the same total price.
- It also suggests Client controls the manner of work, which can create independent-contractor misclassification risk in some jurisdictions.
Suggested replacement
Contractor shall perform the services and deliverables described in each mutually executed Statement of Work (“SOW”). Any material change to scope, deliverables, assumptions, dependencies, timeline, or acceptance criteria must be set forth in a written change order signed by both parties. Contractor is not obligated to perform out-of-scope work unless and until the parties agree in writing on any related fees and schedule adjustments. Contractor shall control the means and methods of performing the services, subject to the requirements of the applicable SOW.
Legal reasoning
Contracts work best when scope is definite. A unilateral scope-change right gives the client leverage to demand more work while disputing payment. A written change-order process creates clear mutual assent and reduces later disputes.
2. Payment
Problem language
“Contractor shall be paid $150/hour, invoiced monthly. 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 exploitable
- Net 90 is harsh for an independent contractor.
- “Unsatisfactory” at Client’s sole discretion lets Client avoid payment arbitrarily.
- For an hourly contract, payment should generally be for time worked, not entirely contingent on unilateral acceptance of deliverables.
- No acceptance process, no cure period, no duty to pay undisputed amounts, no late fee, no right to suspend work for nonpayment.
Suggested replacement
Contractor shall be paid at the rate of $150 per hour and shall invoice monthly. Undisputed amounts are due within 15 days [or 30 days] of invoice receipt. Any disputed amount must be identified in writing within 10 business days of invoice receipt, with reasonable detail describing the basis for the dispute. Client shall timely pay all undisputed amounts. Late payments shall accrue interest at 1.0% per month (or the maximum rate permitted by law, if lower). Contractor may suspend services upon 5 business days’ written notice if undisputed amounts remain unpaid after the due date.
If any deliverable is subject to acceptance, Client must notify Contractor in writing within 10 business days of delivery of any material nonconformity with the written specifications in the applicable SOW. Contractor shall have a reasonable opportunity to cure. Acceptance shall not be unreasonably withheld, conditioned, or delayed, and deliverables will be deemed accepted if Client does not timely reject them in writing.
Legal reasoning
A client should not be able to create an illusory payment obligation by reserving sole discretion to call work unsatisfactory. Even where courts imply a duty of good faith, it is safer to state objective acceptance criteria and require payment of the undisputed portion.
3. Intellectual Property
Problem 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 exploitable
- It appears to transfer:
- the contractor’s pre-existing IP
- reusable tools/libraries/templates
- general methods/know-how
- improvements to the contractor’s internal toolkit
- If contractor uses a pre-existing framework or codebase, Client could claim ownership of it.
- No tie between IP transfer and payment.
- Could conflict with third-party/open-source license obligations.
Suggested replacement
Contractor retains all right, title, and interest in and to any pre-existing materials, software, tools, libraries, frameworks, templates, documentation, know-how, methodologies, and other intellectual property owned or developed by Contractor independently of this Agreement (“Background IP”).
Upon Client’s full payment of all amounts due for the applicable services, Contractor assigns to Client all right, title, and interest in the custom deliverables specifically identified in the applicable SOW and created by Contractor exclusively for Client under this Agreement (“Deliverables”), excluding any Background IP.
To the extent any Background IP is incorporated into the Deliverables, Contractor grants Client a perpetual, worldwide, non-exclusive, non-transferable (except with the Deliverables), royalty-free license to use such Background IP solely as incorporated in and necessary to use the Deliverables.
Nothing in this Agreement transfers ownership of Contractor’s Background IP, general skills, ideas, concepts, processes, or know-how. Open-source software and other third-party materials remain subject to their applicable license terms.
Legal reasoning
This is the standard distinction between:
- foreground IP: custom deliverables created for the client, and
- background IP: the contractor’s existing toolbox and general know-how.
Without that carve-out, the contractor may accidentally assign the core assets of their business.
4. Non-Compete
Problem 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 exploitable
- Extremely broad:
- “similar services” is vague
- “same industry” may cover a huge segment
- 24 months is long
- no geography limit
- For an independent contractor, this can effectively block future livelihood.
- In many jurisdictions, non-competes are disfavored, restricted, or unenforceable, especially broad ones. But even unenforceable clauses can still be used to threaten litigation.
Best modification
Delete it entirely.
If Client insists, replace with a narrow non-solicit
During the term of this Agreement and for 12 months thereafter, Contractor shall not knowingly solicit for employment any employee of Client with whom Contractor had direct material contact during the engagement, except through general solicitations not targeted at Client personnel. Contractor’s obligations under the confidentiality provisions shall protect Client’s legitimate business interests, and no other post-termination restriction on Contractor’s ability to provide services shall apply.
Legal reasoning
Courts generally only enforce post-termination restraints to the extent they are reasonable and necessary to protect legitimate interests such as confidential information or goodwill. A broad industry-wide ban is often overkill. Confidentiality + narrow non-solicit is much more defensible.
5. Termination
Problem 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 exploitable
- One-sided termination rights.
- Client can fire contractor immediately, but contractor is locked in for 60 days.
- Client can terminate and demand work in progress while avoiding full payment.
- “Without additional compensation” can be used to demand unpaid transition work.
- No obligation to pay for approved expenses or non-cancellable commitments.
Suggested replacement
Either party may terminate this Agreement for convenience upon 15 days’ written notice. Either party may terminate immediately upon written notice if the other party materially breaches this Agreement and fails to cure such breach within 10 days after receiving notice.
Upon termination, Client shall pay Contractor for all services performed through the effective date of termination, all accepted deliverables, all work in progress performed at Client’s request, all approved reimbursable expenses, and any non-cancellable commitments incurred on Client’s behalf. Contractor shall deliver to Client the completed and paid-for Deliverables and, upon Client’s request, reasonable transition assistance at Contractor’s then-current hourly rates.
Legal reasoning
A balanced termination clause avoids forfeiture and unjust enrichment. The client should not receive the benefit of partially completed work without paying for it. Also, delivery of source code/work product should generally be conditioned on payment.
6. Liability
Problem 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 exploitable
- Unlimited liability can bankrupt a small contractor.
- Software almost always contains bugs; this makes the contractor a guarantor of all outcomes.
- Consequential damages can include lost profits, business interruption, reputational harm, data loss, etc. Those numbers can dwarf the contract value.
- No distinction between contractor-caused issues and issues caused by:
- client specs
- client infrastructure
- third-party dependencies
- later modifications
- misuse
Suggested replacement
Contractor warrants that the services will be performed in a professional and workmanlike manner consistent with generally accepted industry standards. Contractor does not warrant that the Deliverables will be error-free or operate uninterrupted.
Contractor’s sole obligation and Client’s exclusive remedy for any breach of the foregoing warranty shall be, at Contractor’s option, re-performance of the nonconforming services or refund of the fees paid for the nonconforming services.
Except for liability arising from a party’s fraud, willful misconduct, or breach of confidentiality, each party’s aggregate liability arising out of or relating to this Agreement shall not exceed the total fees paid or payable to Contractor under the applicable SOW during the 12 months preceding the event giving rise to the claim [or 2x fees, if negotiated].
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 business opportunity, or loss/corruption of data, even if advised of the possibility of such damages.
Legal reasoning
Limitation-of-liability clauses are standard because they allocate risk proportionally to contract value. A contractor charging hourly fees should not be underwriting the client’s entire business risk.
7. Indemnification
Problem language
“Contractor shall indemnify Client against all claims arising from Contractor’s work, including claims by third parties, regardless of fault.”
Why this is exploitable
- It makes the contractor responsible even when the contractor did nothing wrong.
- Could force contractor to pay for claims caused by:
- client specifications
- client modifications
- client deployment decisions
- third-party systems
- client misuse
- No procedural protections: notice, defense control, settlement consent.
Suggested replacement
Contractor shall indemnify, defend, and hold harmless Client from third-party claims to the extent arising from (a) Contractor’s gross negligence or willful misconduct, or (b) allegations that Deliverables created solely by Contractor under this Agreement infringe such third party’s intellectual property rights, excluding claims arising from Client materials, Client specifications, modifications not made by Contractor, combination with items not provided by Contractor, or use outside the documentation or intended purpose.
Client shall indemnify, defend, and hold harmless Contractor from third-party claims arising from Client’s materials, specifications, data, instructions, modifications, deployment decisions, or use of the Deliverables in combination with other systems not provided by Contractor.
The indemnified party shall promptly notify the indemnifying party of any claim, provide reasonable cooperation, and allow the indemnifying party to control the defense and settlement, provided that no settlement imposing liability or obligations on the indemnified party may be entered without its prior written consent.
Legal reasoning
Indemnity should track fault and control. Broad indemnities “regardless of fault” are extremely dangerous because they transfer risks the contractor cannot manage.
8. Confidentiality
Problem language
“Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination.”
Why this is exploitable
- Overbroad: “any information about this engagement” could include even harmless facts.
- No standard exceptions for information that is:
- public
- already known
- independently developed
- lawfully obtained from others
- No carve-out for disclosures to:
- lawyers
- accountants
- insurers
- tax advisors
- subcontractors under NDA
- courts/regulators if legally required
- Ban on sharing the agreement terms can interfere with getting advice or enforcing payment rights.
Suggested replacement
“Confidential Information” means non-public information disclosed by Client that is marked confidential or that a reasonable person would understand to be confidential under the circumstances. Confidential Information does not include information that: (a) is or becomes public through no fault of Contractor; (b) was already known to Contractor without restriction; (c) is independently developed without use of Client’s Confidential Information; or (d) is lawfully received from a third party without restriction.
Contractor may disclose Confidential Information to its employees, subcontractors, attorneys, accountants, tax advisors, insurers, and financing sources who have a need to know and are bound by confidentiality obligations at least as protective as those set forth herein. Contractor may also disclose Confidential Information to the extent required by law, regulation, subpoena, or court order, provided Contractor gives prompt notice where legally permitted.
The confidentiality obligations shall continue for 3 years after termination; provided that trade secrets shall remain protected for so long as they remain trade secrets under applicable law.
Nothing herein prohibits Contractor from disclosing the terms of this Agreement as reasonably necessary to enforce its rights, obtain professional advice, comply with law, or collect amounts due.
Legal reasoning
Confidentiality clauses are normal, but they need standard carve-outs and compelled-disclosure rights. Otherwise they can be used to block the contractor from getting help, collecting payment, or defending itself.
9. Dispute Resolution
Problem language
“Any disputes shall be resolved through binding arbitration in Client’s home jurisdiction, with costs borne by the losing party.”
Why this is exploitable
- Forces the contractor to fight on the client’s home turf.
- Travel and local counsel costs create settlement pressure.
- “Losing party pays” can deter even valid claims, especially invoice collection claims.
- Arbitration also limits appeal rights and can be expensive.
Suggested replacement
Any dispute arising out of or relating to this Agreement shall be resolved by binding arbitration administered by AAA [or JAMS] under its commercial arbitration rules. The arbitration shall take place remotely or in a mutually agreed neutral location. Each party shall initially bear its own attorneys’ fees and costs and share the arbitrator’s fees equally, subject to any reallocation by the arbitrator as required by applicable law or in cases of bad-faith conduct.
Either party may seek temporary injunctive relief in any court of competent jurisdiction to protect confidential information or intellectual property. Either party may bring claims for unpaid invoices in small claims court or another court of competent jurisdiction if the amount falls within that court’s limits.
Legal reasoning
A neutral forum reduces leverage abuse. One-sided venue and fee-shifting provisions can make practical enforcement impossible for the smaller party.
Clauses to push hardest on
If you want to prioritize, these are the biggest red flags:
- Clause 3 (IP) – could transfer your entire codebase/toolkit.
- Clause 6 (Liability) – unlimited liability + consequential damages.
- Clause 7 (Indemnity) – indemnity regardless of fault.
- Clause 4 (Non-compete) – could block your livelihood.
- Clause 2 (Payment) – net 90 + sole-discretion withholding.
- Clause 5 (Termination) – client can terminate and still take unpaid work.
Other contractor protections missing from the agreement
Even beyond the bad clauses, a fair consulting contract usually also includes:
-
Independent contractor status
Contractor controls means/methods; no benefits; responsible for own taxes.
-
Detailed SOW / deliverables / milestones
So scope and acceptance are clear.
-
Expense reimbursement
Pre-approved expenses reimbursed within a set time.
-
Right to use subcontractors
Subject to confidentiality and contractor responsibility.
-
Support / maintenance boundaries
Bug fixes, warranty period, and ongoing support should be defined and separately priced.
-
Client responsibilities
Access, feedback deadlines, approvals, infrastructure, decision-maker availability.
-
Open-source / third-party software treatment
So the client cannot later claim you breached by using standard dependencies.
-
Ownership transfer only upon full payment
This is very important.
Bottom line
This draft is not merely “client-friendly”; it is structurally risky for the contractor. The major themes are:
- unlimited work
- delayed and discretionary payment
- loss of pre-existing IP
- post-engagement work restrictions
- one-sided termination
- catastrophic liability exposure
- fault-free indemnity
- overbroad secrecy
- home-court dispute mechanics
If you want, I can turn this into a fully revised contractor-friendly version of the agreement with the clauses rewritten in legal contract language.
