Several clauses are unusually one‑sided and could expose the contractor to major financial or professional risk. Below are the main issues, suggested changes, and why they matter.

1. Scope (Clause 1)

Problem
The client can modify the scope “at any time without additional compensation.” This effectively allows unlimited scope creep while the contractor remains bound to the same rate and schedule.

Suggested modification

• “Contractor shall provide software development services as mutually agreed in writing. Any material change to scope, deliverables, or timelines must be documented through a written change order and may result in adjustment of fees and schedule.”

Reasoning
Most consulting contracts include a change‑order mechanism. Without it, the client could continually expand requirements without paying more.

2. Payment Terms (Clause 2)

Problems

• 90‑day payment terms are very long for consulting.
• Client can withhold payment if work is “unsatisfactory” at its sole discretion, which is vague and subjective.
• No late fees or dispute process.

Suggested modifications

• Payment due within 15–30 days.
• Define acceptance criteria.
• Add partial payment protection and late fees.

Example language

• “Invoices are due within 30 days.”
• “Deliverables shall be deemed accepted unless Client provides written notice of material deficiencies within 10 business days.”
• “Late payments accrue interest at 1–1.5% per month.”
• “Client may only withhold payment for the specific disputed portion.”

Reasoning
Without objective acceptance standards, the client could refuse payment indefinitely.

3. Intellectual Property (Clause 3)

Problems

• Transfers ownership of all work including contractor’s pre‑existing tools or frameworks.
• “In perpetuity” and includes anything developed during engagement.

Suggested modification
Split IP into two categories.

Example language

• “Contractor retains ownership of pre‑existing materials, tools, libraries, and know‑how.”
• “Client receives a perpetual, royalty‑free license to use such materials as incorporated into deliverables.”
• “Ownership of custom deliverables created specifically for Client transfers upon full payment.”

Reasoning
Consultants must preserve ownership of reusable code and tools. Otherwise the client could claim rights over the contractor’s entire toolkit.

4. Non‑Compete (Clause 4)

Problems

• Prevents work with any company in the same industry.
• Applies for 24 months.
• Industry definition may be broad.

Suggested modification

• Replace with a limited non‑solicitation clause.

Example

• “Contractor agrees not to solicit Client’s employees or directly compete on the specific project for 6–12 months.”
  or
• Limit the non‑compete to direct competitors and shorten to 6–12 months.

Reasoning
Broad non‑competes are often unenforceable and can effectively prevent the contractor from working in their field.

5. Termination (Clause 5)

Problems

• Client can terminate immediately with no notice.
• Contractor must give 60 days notice.
• Contractor must deliver unfinished work without compensation.

Suggested modification

• Mutual notice period (e.g., 14–30 days).
• Payment for work performed through termination.

Example

• “Either party may terminate with 30 days written notice.”
• “Client shall pay for all work performed up to the termination date.”
• “Delivery of work in progress occurs after payment for such work.”

Reasoning
The current clause lets the client end the contract abruptly after receiving substantial unpaid work.

6. Liability (Clause 6)

Problems

• Unlimited liability.
• Covers consequential damages.
• Contractor responsible for all bugs or failures indefinitely.

Suggested modification
Add a liability cap and exclude consequential damages.

Example

• “Contractor’s total liability shall not exceed the total fees paid under this Agreement.”
• “Neither party shall be liable for indirect, incidental, or consequential damages.”

Reasoning
Unlimited liability is a major financial risk; a single system failure could bankrupt an individual contractor.

7. Indemnification (Clause 7)

Problems

• Contractor indemnifies client “regardless of fault.”
• Extremely broad scope.

Suggested modification

• Limit indemnification to contractor negligence or IP infringement.

Example

• “Contractor shall indemnify Client against claims arising from Contractor’s willful misconduct, negligence, or infringement of third‑party intellectual property.”

Reasoning
Without fault limitation, the contractor could be liable even if the client misuses the software.

8. Confidentiality (Clause 8)

Problems

• Prohibits even mentioning the existence or terms of the contract for 5 years.
• Could prevent legal or tax disclosure.

Suggested modification
Add standard exceptions.

Example

• Allow disclosure to legal/tax advisors.
• Permit listing Client as a portfolio reference unless otherwise agreed.
• Maintain confidentiality for trade secrets indefinitely but general terms for shorter period (2–3 years).

Reasoning
Contractors must be able to discuss contracts with accountants, lawyers, and insurers.

9. Dispute Resolution (Clause 9)

Problems

• Arbitration only in the client’s jurisdiction.
• Losing party pays all costs.

Suggested modification

• Neutral venue or contractor’s jurisdiction.
• Shared arbitration costs unless otherwise ordered by arbitrator.

Example

• “Arbitration shall occur in a mutually agreed neutral location or via remote proceedings.”

Reasoning
Travel and legal costs could be used strategically to pressure the contractor into settling.

Major overall risks

The biggest red flags are:

• Unlimited liability
• IP ownership of contractor’s existing tools
• Client’s unilateral scope changes
• Payment withholding at client’s discretion
• Immediate termination without payment protection

Those could expose the contractor to unpaid work, loss of core IP, and catastrophic financial liability.

If you want, I can also show how experienced contractors typically rewrite this agreement into a safer “consultant‑friendly” version clause‑by‑clause.