Check Freelance and Client Contracts with AI

# Contract Review: Freelance Web Development Agreement ($12,000)

Short answer up front: **Do not sign this as written.** Nearly every major clause is drafted aggressively in the client's favor, and several could expose you to uncapped financial risk or result in you working for free. Below is a detailed breakdown.

---

## 1. Red Flags (Critical — Fix Before Signing)

- **IP Assignment of Pre-Existing Tools and Code** — *"Contractor assigns all intellectual property, including pre-existing tools and code, to Client upon commencement of work."*
  - **Why it matters:** This would transfer ownership of your entire code library, frameworks, snippets, and reusable tools to this one client. You'd literally be unable to use your own work on future projects without permission. "Upon commencement" is even worse — it transfers before you're paid a dime.
  - **Fix required:** You keep all pre-existing IP. Client only gets ownership of deliverables created specifically for them, and only after full payment.

- **Termination Without Cause or Payment** — *"Client may terminate at any time without cause and without payment for work in progress."*
  - **Why it matters:** The client could let you build 90% of the site, terminate the day before launch, pay nothing, and hire someone else to finish it for cheap. This is not a contract — it's an unpaid internship with extra steps.
  - **Fix required:** Termination must require payment for all work completed and in progress, plus a kill fee.

- **Uncapped Indemnification** — *"liable for any and all damages arising from the project"*
  - **Why it matters:** If the client's site goes down and they claim lost revenue, or a third party sues them over something connected to the site, you could be personally on the hook for unlimited damages — far beyond the $12,000 fee. One lawsuit could bankrupt you.
  - **Fix required:** Cap liability at the total fees paid, mutual indemnification, and exclude indirect/consequential damages.

- **Unlimited Revisions** — *"unlimited revisions until Client is satisfied"*
  - **Why it matters:** "Satisfied" is entirely subjective. A difficult client could demand endless changes and refuse to approve the project for months or years. Combined with Net 60 on *final approval*, you may never get paid.
  - **Fix required:** Cap revisions (e.g., two rounds per milestone); additional revisions billed hourly.

- **Net 60 Upon Final Approval**
  - **Why it matters:** Net 60 is already very long for a freelancer. Tied to "final approval" (subjective) plus "unlimited revisions," this means payment could be pushed out indefinitely. You could easily be 6+ months out of pocket on a $12K project.
  - **Fix required:** Milestone-based payments with a deposit up front, Net 15 or Net 30 max.

---

## 2. Yellow Flags (Negotiate)

- **Payment Structure Generally** — Even if Net 60 becomes Net 30, a single lump-sum payment on a $12K project is risky. Push for staged payments (e.g., 33% deposit / 33% midpoint / 34% on delivery).

- **"Final Client Approval" as Payment Trigger** — Subjective approval standards invite disputes. Replace with objective criteria: project meets the written specifications in the Statement of Work.

- **Scope of Work (appears to be missing)** — You didn't mention a detailed SOW. Without one, "the project" means whatever the client later claims. This is how scope creep becomes a legal obligation.

- **Confidentiality (appears one-sided or missing)** — If there's a confidentiality clause, make sure it's mutual. The client's business info is confidential, but so is your pricing, processes, and methodology.

---

## 3. Missing Protections (Add These)

- **Limitation of Liability Clause** — Cap your total liability at the fees paid under the contract. Exclude lost profits, lost data, and consequential damages.

- **Late Payment Terms** — Interest on overdue invoices (1.5% per month is standard) and the right to suspend work if payment is more than X days late.

- **Kill Fee / Early Termination Fee** — If the client terminates, you keep the deposit plus get paid for all work in progress, plus a percentage of remaining contract value.

- **Freelancer's Right to Terminate** — You should also be able to terminate for non-payment or breach.

- **License-Back of Deliverables** — Even after assigning project-specific IP, you should retain a non-exclusive right to display the work in your portfolio.

- **Force Majeure** — Protects both sides if something unexpected (illness, outages, natural disaster) prevents performance.

- **Governing Law & Dispute Resolution** — Specify your state/country's law applies, and require mediation before litigation.

- **Third-Party Assets Disclaimer** — You're not responsible for licensing fees, failures, or bugs in third-party plugins, themes, or APIs.

- **Client Responsibilities** — Client must provide content, feedback, and approvals within set timeframes. Delays on their side shift the timeline.

- **Warranty Limits** — Offer a reasonable warranty (e.g., 30 days to fix bugs) but disclaim warranties beyond that.

---

## 4. Suggested Redlines (Specific Language Changes)

**Intellectual Property — replace with:**
> "Contractor retains all right, title, and interest in pre-existing tools, code, frameworks, and methodologies ('Background IP'). Upon receipt of final payment, Contractor assigns to Client the deliverables created specifically for Client under this Agreement, excluding Background IP. Contractor grants Client a perpetual, non-exclusive license to use any Background IP incorporated into the deliverables. Contractor retains the right to display completed work in portfolios and marketing materials."

**Payment — replace with:**
> "Client shall pay Contractor as follows: 33% deposit upon signing (non-refundable); 33% upon completion of design approval milestone; 34% upon project delivery. All invoices are due Net 15. Overdue amounts acc

# FREELANCE CONTRACT REVIEW
## Web Developer – $12,000 Website Project

---

## 1. RED FLAGS (Critical Issues – Do Not Sign As-Is)

### A. Intellectual Property Assignment – Pre-Existing Tools & Code
**Issue:** "Contractor assigns all intellectual property, including pre-existing tools and code, to Client upon commencement of work."

**Why It Matters:**
- You're being forced to surrender ownership of tools, frameworks, libraries, templates, and code you've created before or outside this project
- This includes open-source frameworks (React, Vue, etc.), custom libraries you've built over years, and design systems
- You cannot reuse these assets on future projects or for other clients
- This destroys your ability to work efficiently and build a portfolio of reusable components
- You lose all competitive advantage and proprietary know-how

**Risk Level:** CRITICAL

**Specific Problems:**
- The phrase "pre-existing tools and code" is dangerously broad
- "Upon commencement" means transfer happens before you even start, not just for deliverables
- No carve-out for your own frameworks, libraries, or standard methodologies

**Recommended Redline:**
> "Client receives a perpetual, royalty-free license to all custom code, designs, and deliverables created specifically for this project. Contractor retains ownership of pre-existing tools, libraries, frameworks, templates, and methodologies, including but not limited to: [list your standard toolset]. Contractor grants Client a perpetual, non-exclusive license to use pre-existing components embedded in the final deliverable, but not to extract or repurpose them separately."

**Negotiation Strategy:**
- Explain that your efficiency (and thus their cost) depends on reusing standard tools
- Offer to license specific custom components exclusively to them if they pay a premium
- Suggest a tiered approach: custom IP goes to client, your frameworks/tools stay with you

---

### B. Unlimited Revisions & "Until Client is Satisfied" Payment Trigger
**Issue:** "Net 60 upon final client approval, with unlimited revisions until Client is satisfied."

**Why It Matters:**
- "Until Client is satisfied" is entirely subjective and undefined—you could work indefinitely
- Revisions eat into your profit margin with no additional compensation
- Client can withhold payment indefinitely by claiming dissatisfaction
- At $12,000, each uncapped revision could cost you $200–$500+ in uncompensated labor
- "Net 60" = 60 days before payment, meaning cash flow crisis if you have other bills

**Risk Level:** CRITICAL

**Specific Problems:**
- No definition of "final approval" or "satisfied"
- No revision limit (1st round, 2nd round, unlimited)
- No timeline for client feedback/approval
- Client pays in 60 days, but you pay contractors/tools upfront
- Revision requests could come 6 months after delivery, delaying payment indefinitely

**Real-World Example:**
Client requests: "Make the button bluer." You revise. "Actually, make it darker blue." Revise again. "That's too dark, original was better." This could repeat 50 times without extra pay.

**Recommended Redline:**
> "Payment: $12,000 due upon delivery of final deliverables, Net 30 [or upon project completion]. Client receives two (2) rounds of revisions included in the project scope. Each round includes up to five (5) revision requests. Additional revisions beyond this are billed at $150/hour. Client must provide revision feedback within 5 business days of receiving deliverables; approval is deemed granted if no feedback is provided within this timeframe. Revisions not provided within 90 days of final deliverable delivery will incur a $500 project holdover fee."

**Negotiation Strategy:**
- Push hard on revision rounds (this is a deal-breaker for most freelancers)
- Tie payment to completion, not client satisfaction (you control completion, not their mood)
- Shorten Net terms to Net 30 or payment upon delivery
- Request 50% upfront to cover your costs; rest due at delivery

---

### C. Termination Without Payment for Work in Progress
**Issue:** "Client may terminate at any time without cause and without payment for work in progress."

**Why It Matters:**
- Client can fire you on day 29 of a 30-day project and pay $0
- You've invested time, software licenses, contractor costs, and mental energy with zero compensation
- "At any time" includes after 90% completion
- You have no recourse if they hire a competitor instead mid-project
- This is one-sided: you probably can't terminate without cause

**Risk Level:** CRITICAL

**Specific Problems:**
- "Without cause" means they don't need a reason (bad work, scope creep, or just changing their mind)
- "Work in progress" is undefined—does 50% complete work count? 99%?
- No payment for partially completed milestones
- No notice period required
- Contradicts payment clause (how can you deliver if they terminate?)

**Real-World Example:**
You're 3 weeks into a 4-week project. Client's new CEO decides to use an internal team instead. Contract terminated. You receive $0, even though you've completed 80% of deliverables.

**Recommended Redline:**
> "Termination: Client may terminate this Agreement with 10 business days' written notice. If terminated by Client without cause, Client shall pay: (1) 100% of fees for all completed deliverables; (2) 50% of fees for work in progress (defined as work with documented evidence of completion, such as commits, design mockups, or written progress reports); (3) all out-of-pocket expenses incurred to date (software licenses, contractors, hosting). Contractor may terminate for Client's material breach (non-payment after 15 days of invoice, scope creep exceeding 40% of original scope) with 5 days' written notice."

**Negotiation Strategy:**
- Frame this as "mutual protection": they get notice, you get paid for work done
- Propose a tiered kill-fee: 100% if terminated after 75% completion, 75% if after 50%, etc.
- Link termination to payment milestones (they can only terminate after a milestone is paid)
- Request 50% deposit upfront—if they terminate, you keep it

---

### D. Uncapped Indemnification & Liability
**Issue:** "Contractor liable for any and all damages arising from the project" with no cap.

**Why It Matters:**
- You're liable for unlimited damages—potentially 10x, 100x, or more than your contract value
- "Any and all damages" includes business losses, lost profits, reputational harm, etc.
- Client can sue you for $500K in damages even though you were paid $12K
- You'd need insurance to cover this; most general liability policies won't
- No distinction between your fault and client's misuse of the site

**Risk Level:** CRITICAL

**Specific Problems:**
- No damage cap (e.g., "capped at contract value")
- No exclusion for client's negligence or misuse
- No exclusion for indirect/consequential damages (lost profits, business interruption)
- No requirement that you be at fault (strict liability)
- Could include damages caused by client's actions after delivery (poor hosting, security practices)
- No insurance requirement on client (they can cause damage, you're liable)

**Real-World Example:**
Your site has a security vulnerability (hypothetically your fault). Hackers steal customer data. Client sues for $2M in customer settlements. You owe $2M, not $12K.

**Recommended Redline:**
> "Limitation of Liability: Contractor's total liability for any breach, negligence, or claim arising from this Agreement shall not exceed the total fees paid under this Agreement ($12,000). CONTRACTOR IS NOT LIABLE FOR: (1) indirect, incidental, consequential, special, or punitive damages, including lost profits, lost revenue, or business interruption; (2) damages caused by Client's failure to follow Contractor's instructions or security recommendations; (3) damages caused by third-party hosting, plugins, or services not provided by Contractor; (4) security breaches resulting from Client's weak passwords, failure to update software, or failure to implement recommended security measures; (5) damages caused by Client's actions or omissions after project delivery."

**Negotiation Strategy:**
- Propose capping liability at contract value (very standard in tech contracts)
- Carve out damages for your gross negligence (which is unavoidable) but exclude ordinary negligence
- Request that client carry cyber liability insurance
- Require client to notify you of issues within 30 days of discovery (limits exposure)

---

## 2. YELLOW FLAGS (Important Issues to Negotiate)

### A

## (1) Red Flags — fix before signing

- **IP assignment is far too broad**
  - **Clause:** “**Contractor assigns all intellectual property, including pre-existing tools and code, to Client upon commencement of work.**”
  - **Why this is a problem:**  
    This gives away not just the website deliverables, but also your existing code, frameworks, templates, snippets, methods, utilities, and anything you bring to the project. It could stop you from reusing your own tools for future clients.
  - **Why it matters:**  
    As a freelance web developer, your reusable code and processes are part of your business. Giving them away can damage your ability to work efficiently and earn money later.
  - **What to push for:**  
    Client should only own the **final custom deliverables** created specifically for this project, and only **after full payment**. Your pre-existing tools/code should remain yours, with a limited license granted to the client if needed.

- **Payment term is very freelancer-unfriendly**
  - **Clause:** “**Net 60 upon final client approval**”
  - **Why this is a problem:**  
    You may wait months to get paid, especially because payment depends on “final client approval,” which is subjective and can be delayed.
  - **Why it matters:**  
    You are financing the entire project out of pocket. Net 60 is long even for larger vendors, and tying payment to approval makes it worse.
  - **What to push for:**  
    Require an upfront deposit and milestone payments. Final payment should be due on delivery or within 7–15 days, not 60 days after vague approval.

- **Unlimited revisions = unlimited unpaid work**
  - **Clause:** “**with unlimited revisions until Client is satisfied**”
  - **Why this is a problem:**  
    This creates no endpoint. The client can keep asking for changes forever, even if they keep changing their mind.
  - **Why it matters:**  
    This can destroy your profit on a fixed-fee project and lead to scope creep.
  - **What to push for:**  
    Limit revisions to a set number of rounds tied to agreed deliverables. Anything beyond that should be billed at your hourly rate.

- **Termination without payment for work already done**
  - **Clause:** “**Client may terminate at any time without cause and without payment for work in progress.**”
  - **Why this is a problem:**  
    The client can use your time, concepts, partial builds, and labor, then walk away without paying.
  - **Why it matters:**  
    This is one of the most dangerous clauses in the contract. It puts all risk on you.
  - **What to push for:**  
    If the client terminates for convenience, they must pay for all work performed up to the termination date, plus any committed non-cancelable costs.

- **Unlimited liability / indemnity**
  - **Clause:** “**liable for any and all damages arising from the project**”
  - **Why this is a problem:**  
    This could make you responsible for losses far beyond the $12,000 project fee, including business losses, third-party claims, lost profits, security issues, content issues, or client misuse.
  - **Why it matters:**  
    One dispute could wipe out far more than you earn from the project.
  - **What to push for:**  
    Limit liability to the amount paid under the contract, exclude indirect/consequential damages, and narrow indemnity to your actual breach, infringement in your original work, or willful misconduct.

## (2) Yellow Flags — negotiate

- **“Final client approval” is too subjective**
  - **Clause:** “**upon final client approval**”
  - **Why this is a problem:**  
    Approval is undefined. The client can delay approval based on personal taste, internal politics, or unrelated business changes.
  - **Negotiation point:**  
    Add objective acceptance criteria and a review period. If the client does not reject with specific reasons within a set number of business days, the work is deemed accepted.

- **No milestone structure for a $12,000 project**
  - **Clause affected:** Payment clause generally
  - **Why this is a problem:**  
    For a project of this size, one payment at the end leaves you carrying all delivery risk.
  - **Negotiation point:**  
    Split into deposit + milestones, for example:
    - 40% upfront
    - 30% at design/dev approval
    - 30% before launch or on final delivery

- **No scope definition**
  - **Clause affected:** Revision and project description language
  - **Why this is a problem:**  
    If the contract does not clearly define pages, features, integrations, content responsibilities, browser support, SEO scope, testing, hosting, and post-launch support, the client can claim almost anything is included.
  - **Negotiation point:**  
    Add a detailed statement of work with deliverables, assumptions, exclusions, and change-order process.

- **Ownership starts “upon commencement of work”**
  - **Clause:** “**assigns all intellectual property… upon commencement of work**”
  - **Why this is a problem:**  
    You lose leverage before being paid. If things go wrong, the client may claim ownership even if they owe you money.
  - **Negotiation point:**  
    Ownership transfer should happen only after all amounts are paid in full.

- **No late fee / collection cost language**
  - **Clause affected:** Payment clause
  - **Why this is a problem:**  
    If they pay late, there is no consequence.
  - **Negotiation point:**  
    Add late fees, interest, and recovery of collection costs.

- **No pause rights if client delays**
  - **Clause affected:** Project timing and payment
  - **Why this is a problem:**  
    You may be blamed for missed deadlines caused by the client failing to provide content, feedback, access, or approvals.
  - **Negotiation point:**  
    Add client dependency language and a right to pause the project if inputs are delayed.

- **No limit on warranty/support**
  - **Clause affected:** not stated, but likely omitted
  - **Why this is a problem:**  
    Without clear support limits, clients often assume bug fixes and maintenance are included forever.
  - **Negotiation point:**  
    Add a short warranty for defects in your work and separate paid maintenance/support for anything beyond that.

- **No confidentiality details**
  - **Clause affected:** confidentiality not mentioned
  - **Why this is a problem:**  
    If you receive client data, logins, business info, or user information, expectations should be clear. Also, you should be allowed to show the finished project in your portfolio unless they have a valid confidentiality need.
  - **Negotiation point:**  
    Add mutual confidentiality, but preserve your right to list the client and showcase non-confidential work.

## (3) Missing Protections — should be added

- **Deposit / retainer**
  - **What’s missing:**  
    A non-refundable upfront payment before work starts.
  - **Why it matters:**  
    Protects your time and confirms the client is serious.
  - **Suggested addition:**  
    “Work will begin once Contractor receives a non-refundable deposit of 40%.”

- **Milestone billing**
  - **What’s missing:**  
    Progress payments tied to defined stages.
  - **Why it matters:**  
    Reduces cash-flow risk and prevents you from doing all work before payment.
  - **Suggested addition:**  
    Milestones tied to discovery, design approval, development completion, and launch.

- **Defined scope of work**
  - **What’s missing:**  
    Specific deliverables and exclusions.
  - **Why it matters:**  
    Prevents arguments over what is included in the fixed fee.
  - **Suggested addition:**  
    Number of page templates, revisions included, integrations, CMS features, responsive design, testing, launch assistance, training, and post-launch support.

- **Change-order process**
  - **What’s missing:**  
    A way to handle extra requests.
  - **Why it matters:**  
    Stops “can you just also…” requests from eating your margin.
  - **Suggested addition:**  
    Any work outside scope requires written approval and is billed at $X/hour or quoted separately.

- **Acceptance procedure**
  - **What’s missing:**  
    A clear review and signoff process.
  - **Why it matters:**  
    Without this, “not satisfied” can last forever.
  - **Suggested addition:**  
    Client must review within 5 business days and either accept or give one written list of material issues. If no response, deliverables are deemed accepted.

- **Kill fee / payment on termination**
  - **What’s missing:**  
    Protection if the client ends the project early.
  - **Why it matters:**  
    You need to be paid for reserved time and work completed.
  - **Suggested addition:**  
    Client pays for all work completed through termination, all approved expenses, and a kill fee or the next milestone if termination occurs after work has begun.

- **IP carve-out for pre-existing materials**
  - **What’s missing:**  
    Protection for your background technology.
  - **Why it matters:**  
    Keeps your toolkit yours.
  - **Suggested addition:**  
    Pre-existing code, libraries, frameworks, know-how, and generic routines remain your property.

- **Limited license for your tools**
  - **What’s missing:**  
    A license allowing the client to use embedded tools without owning them.
  - **Why it matters:**  
    Lets the website function while protecting your reusable assets.
  - **Suggested addition:**  
    Client gets a non-exclusive license to

Of course. As an experienced contract lawyer and business advisor, I can review this agreement for you.

Based on the clauses you've shared, this contract is extremely one-sided in favor of the client and carries significant, unacceptable risks for you as a freelancer. Do not sign it in its current form.

Here is a detailed breakdown following your instructions.

---

### **Contract Review for Freelance Web Developer**

#### **(1) Red Flags (Critical Issues to Fix Before Signing)**

These are deal-breaker clauses that expose you to immense financial and professional risk. They must be changed, or you should walk away from the project.

*   **Intellectual Property Assignment (Clause: "Contractor assigns all intellectual property, including pre-existing tools and code, to Client upon commencement of work.")**
    *   **The Risk:** This is the most dangerous clause in the agreement. It means the client would own not just the custom website I build for them, but also any proprietary code, tools, plugins, or frameworks you have developed in the past and use for this project. This is your "toolkit" and the foundation of your business. Giving it away for $12,000 is professionally catastrophic. You would be unable to legally use your own code for any future client. The timing, "upon commencement," means they own it before you've even been paid.
    *   **Why it Matters:** You need to retain ownership of your pre-existing tools and grant the client a license to use them as part of the final website. The client should only own the final, unique "deliverable" you create for them.

*   **Termination for Convenience (Clause: "Client may terminate at any time without cause and without payment for work in progress.")**
    *   **The Risk:**

### 1. Red Flags (critical issues to fix before signing)
These are deal-breakers that heavily favor the client and expose you to major financial or legal risks. Do not sign without major changes.

- **IP Assignment clause ('Contractor assigns all intellectual property, including pre-existing tools and code, to Client upon commencement of work')**: This forces you to give away ownership of *any* code or tools you already own (like reusable templates or libraries), even if unrelated to this project. Why it matters: You could lose rights to your own work forever, limiting future jobs. Fix: Limit to deliverables only.
  
- **Termination clause ('Client may terminate at any time without cause and without payment for work in progress')**: Client can fire you anytime, even mid-project, and owe nothing for your time/effort. Why it matters: You're unpaid for potentially weeks of work on a $12k project. Fix: Require payment for completed work.

- **Indemnification clause (making you liable for 'any and all damages arising from the project' with no cap)**: You're on the hook for unlimited losses if anything goes wrong (e.g., client sues over a bug). Why it matters: One lawsuit could bankrupt you. Fix: Cap liability and make it mutual.

- **Payment terms with unlimited revisions ('Net 60 upon final client approval, with unlimited revisions until Client is satisfied')**: No limit on changes means client can demand endless tweaks without extra pay; payment 60 days after they finally approve. Why it matters: Project drags on forever, cash flow killed. Fix: Cap revisions and add milestones.

### 2. Yellow Flags (clauses to negotiate)
These aren't immediate no-gos but tilt toward the client and need tweaking for fairness.

- **Payment terms (Net 60)**: 60 days is too long for freelancers needing steady income. Why it matters: Ties up your money for 2+ months. Negotiate: Net 30 or milestones (e.g., 30% upfront, 40% on draft, 30% on final).

- **Scope of work (not explicitly defined in provided clauses)**: No clear description of what's included (e.g., pages, features, timeline). Why it matters: Client can claim anything extra is "in scope," leading to disputes. Negotiate: Add detailed scope with change order process for extras.

- **Lack of timeline or deadlines**: No project end date. Why it matters: Ties into unlimited revisions; project could last indefinitely. Negotiate: Set 60-90 day timeline with penalties for client delays.

### 3. Missing Protections (what should be added)
The contract lacks basics to protect freelancers. Push to insert these.

- **Payment milestones**: Break $12k into chunks (e.g., 25% deposit, 25% design approval, 25% development, 25% launch). Why: Ensures steady pay and motivation.

- **Defined scope of work**: List exact deliverables (e.g., "5-page responsive site with contact form, blog, no e-commerce"). Include process for changes (extra fee/time).

- **Revision limits**: E.g., "3 rounds of revisions included; additional at $100/hour." Why: Prevents scope creep.

- **Kill fee/termination pay**: If client cancels, pay for 50-100% of completed work. Why: Compensates your time.

- **Mutual confidentiality**: Protect your business info (e.g., other clients). Why: Client might misuse your methods.

- **Warranties and disclaimers**: You warrant work is original; disclaim others (e.g., no guarantee site is hack-proof). Why: Limits liability.

- **Dispute resolution**: Mediation/arbitration before court, in your state. Why: Cheaper/faster than lawsuits.

- **Non-exclusive license for background IP**: You retain rights to pre-existing tools; client gets license only. Why: Protects your reusable assets.

### 4. Suggested Redlines (specific wording changes)
Here are exact replacement phrases to propose via tracked changes or email.

- **IP Assignment**: Change to: "Contractor grants Client a perpetual, worldwide, non-exclusive license to use deliverables created specifically for this project. Contractor retains all rights to pre-existing tools, code, or background IP."

- **Termination**: Change to: "Client may terminate with 7 days' notice. Client pays for all work completed and accepted up to termination date, plus a 20% kill fee on remaining balance."

- **Indemnification**: Change to: "Each party indemnifies the other for damages caused by its own gross negligence or willful misconduct, capped at the total project fee ($12,000)."

- **Payment/Revisions**: Change to: "Payment: 30% deposit due signing; 40% on design approval; 30% on launch. Net 15 terms. Includes 3 rounds of revisions on major deliverables; additional revisions at $100/hour. Project completes in 90 days unless delayed by Client."

- **Add Scope section**: "Scope: Build 5-page website (home, about, services, portfolio, contact) with responsive design, CMS integration, and SEO basics. Changes outside scope require written change order with adjusted fee/timeline."

### Go/No-Go Recommendation
**NO-GO**. This contract is freelancer-hostile and could cost you time, money, and IP. Negotiate fixes to all Red Flags first—send a marked-up version. If client won't budge, walk away; plenty of better clients exist.