Sample Consulting Agreement Template (Free Download)

Why Most Consultants Get the Contract Wrong

I've watched talented consultants lose tens of thousands of dollars because their agreement was either nonexistent, too vague, or copy-pasted from somewhere sketchy online. Scope creep destroyed the engagement. A client ghosted after the work was delivered. IP they built got claimed by a client who paid one invoice.

Working without a solid contract isn't just risky - it's operationally naive. Research from Leapers found that nearly 40% of freelancers report significant stress after working without a contract. That stress is almost always about money or unclear expectations. A good consulting agreement eliminates both.

The difference between a sustainable consulting business and a perpetual stress machine is usually not talent. It's operational discipline. And the contract is the foundation of that discipline. If you want to skip ahead and grab a pre-built version, check out the Agency Contract Template or the One-Page Contract Template for something leaner. Otherwise, keep reading - because understanding why each clause exists is what turns a template into a real protection tool.

What a Consulting Agreement Actually Is

A consulting agreement is a legally binding contract between a consultant and a client that defines the scope of work, payment terms, confidentiality expectations, intellectual property rights, and what happens when things go sideways. It protects both parties - but if you're the consultant, you need to make sure you drafted it or at least reviewed it before signing.

One distinction worth knowing: a consulting agreement is different from a generic independent contractor agreement. A consulting agreement specifically covers expert advisory or service relationships, and typically carries more detailed clauses around IP ownership and confidentiality - because consultants see the inside of a client's business in ways that a contractor installing drywall simply doesn't.

The US management consulting industry generates hundreds of billions in annual revenue and employs close to a million professionals. At that scale, clearly documented agreements aren't optional - they're the infrastructure that keeps engagements from collapsing into disputes. Whether you're a solo consultant or running a small agency, the same logic applies to your practice.

Types of Consulting Agreements (and When You Need Each)

Not all consulting agreements are built the same. The structure of your contract should match the nature of the engagement. Here's a quick breakdown of the most common types:

Project-Based Agreement

A fixed-price contract covering a defined project with a clear start and end. Best for engagements with tight scope and predictable deliverables - like a brand audit, a competitive analysis, or a go-to-market strategy document. The scope section does most of the heavy lifting here because there's no ongoing relationship to fall back on. Define deliverables with surgical precision.

Retainer Agreement

An ongoing monthly engagement where the client pays a recurring fee for access to your expertise. Common in marketing strategy, business advisory, and fractional executive arrangements. The agreement needs to clearly spell out what's included in the retainer - how many hours, what types of services, what happens to unused time, and how scope changes get handled. Retainer agreements should also include a provision for periodic review and renegotiation, so the fee stays aligned with the actual workload.

Hourly Consulting Agreement

Best for open-ended or unpredictable engagements where the scope can't be pre-defined. Advisory calls, troubleshooting, or situations where the client isn't sure exactly what they need yet. The payment section is the critical piece here - define the rate, minimum billing increments (typically 30-minute blocks), invoicing frequency, and what documentation you'll provide to support your time records.

Performance-Based Agreement

Some engagements tie a portion of your fee to results - revenue generated, cost savings achieved, or other measurable outcomes. These can work well in the right situation, but they require extra rigor in the agreement. Define the performance metrics precisely. Define how they're measured, who measures them, and what the baseline is. A vague performance clause is worse than no performance clause, because it creates a dispute with a financial stake attached.

Master Services Agreement (MSA)

If you're doing recurring work with the same client across multiple projects, an MSA sets the overarching terms once, and then individual statements of work (SOWs) define each specific project. The MSA handles confidentiality, IP, liability, and dispute resolution at the top level. Each SOW handles scope, deliverables, timeline, and fees for that specific engagement. This structure is efficient for larger clients who do multiple projects with you over time - it eliminates renegotiating the boilerplate every time.

The Core Structure of a Consulting Agreement Template

Here's the section-by-section breakdown of what a solid agreement needs. Each section has a purpose. None of them are optional if you're doing real work with real money on the line.

1. Parties and Effective Date

Start with the basics: full legal names (or business entity names) for both sides, addresses, and the date the agreement takes effect. If you're a sole proprietor operating under an LLC, use the LLC name - not your personal name. This matters for liability reasons. Also include each party's primary point of contact for notices and communications under the agreement - this becomes important if you need to formally exercise termination rights or escalate a dispute.

2. Scope of Services

This is the most important section and the one that causes the most disputes when it's vague. Define exactly what you will deliver. Not "marketing consulting" - but "three 60-minute strategy sessions per month, one written competitive analysis per quarter, and monthly review of ad spend across Google and Meta." List what's included. More importantly, list what is explicitly not included.

Scope failures are the most common source of contractor disputes - and they almost always trace back to describing outputs instead of specifications. Vague scope definitions are one of the leading drivers of project overruns. A tight scope of services section is your first line of defense. If the client wants more than what's defined, that triggers a change order - which should also be referenced in the agreement.

One tactic that works well: include an explicit change order process in this section. Something like: "Any request for services outside the scope defined herein shall be submitted in writing and requires a signed change order before work begins. Consultant's fees for additional services will be agreed upon prior to execution of each change order." This creates friction around scope creep before it becomes a problem.

3. Deliverables and Timelines

Beyond scope, spell out specific deliverables with due dates or milestone structures. If the project has phases, list them. If delivery depends on the client providing materials or approvals, say so - and note that your timeline shifts if they're late on their end. Protect yourself from their delays becoming your failure.

Add a client responsibilities section alongside your deliverables. If you need access to their analytics platform, their brand assets, or a point of contact who can turn around approvals within 48 hours, say so in the agreement. When clients are the bottleneck and timelines slip, you need something in writing that makes clear the delay wasn't yours.

4. Payment Terms

Specify the fee structure: hourly, flat project fee, or monthly retainer. Include the payment schedule (net 15, net 30, milestone-based), accepted payment methods, and what happens if a payment is late. This is where most templates are dangerously thin.

One frequently omitted clause: a late payment interest provision. Without it, you have no contractual leverage when a client sits on an overdue invoice. Include language that adds a monthly interest rate (typically 1.5%) to unpaid balances past the due date. It's a small clause that changes client behavior significantly.

If you're on retainer, define what happens to unused hours - do they roll over, or not? Define it. Ambiguity here costs money. Most retainer agreements specify that unused hours do not roll over - the retainer buys access and availability, not a bank of hours to be drawn down indefinitely.

One more thing most consultants miss: a deposit or upfront payment clause. Require a percentage of the project fee (typically 25-50%) before you start work. Professional clients understand deposits - sophisticated businesses pay retainers to lawyers, architects, and consultants as standard practice. A client who balks at a reasonable deposit is a client who may balk at the final invoice too. Make it a standard part of your process, not a negotiation.

5. Expense Reimbursement

If your engagement involves travel, software, or other out-of-pocket costs, spell out how those get handled. Define which expense categories are reimbursable (travel, lodging, meals, specific tools), what the approval process is before you incur the expense, and how quickly reimbursement happens after you submit receipts. Without this clause, you're absorbing those costs yourself - or fighting about them at the end of the engagement.

A simple approach: "Consultant shall be reimbursed for pre-approved out-of-pocket expenses incurred in connection with the Services. Consultant shall submit expense reports with supporting documentation within [X] days of the expense. Client shall reimburse within [15] days of receipt." Add a cap or require advance written approval for any single expense above a defined threshold, like $500.

6. Independent Contractor Status

This clause confirms you are not an employee. You're responsible for your own taxes, health insurance, and benefits. The client does not withhold payroll taxes on your behalf and cannot direct exactly how you perform the work - only what outcome they need.

This is legally significant. Tax authorities look at conduct, not just contract language, to classify workers. So make sure your working relationship actually reflects independent contractor status: you set your own hours, you use your own tools, and you're not embedded in their org chart. Including this clause but then operationally behaving like an employee is a red flag that can lead to misclassification issues regardless of what the contract says.

7. Intellectual Property Ownership

This is the clause most consultants forget - and it can be catastrophic. Most clients assume that because they paid you, they own everything you created. Whether that's true depends entirely on what your contract says.

You have two options to define clearly:

• Work-for-hire arrangement: Everything you create in the scope of this engagement belongs to the client upon payment in full. Include "upon payment in full" - don't hand over IP rights before you've been paid.
• Licensed IP arrangement: You retain ownership of your underlying methodologies, frameworks, and templates. The client gets a non-exclusive license to use the deliverables. This protects your ability to reuse your own systems with other clients.

If you're a marketing consultant, a strategist, or a systems builder - you probably want the licensed IP structure. You don't want to hand over your proprietary process every time a new client pays a project fee. Decide which model fits your business before sending the agreement.

Also include a clause that pre-existing IP you bring to the engagement - your templates, your frameworks, your prior work product - remains yours regardless of the work-for-hire language. This is sometimes called a "pre-existing IP carveout" and it's critical if you're building custom deliverables that incorporate your proprietary systems.

8. Confidentiality

Consultants see things: financials, internal strategies, personnel issues, customer data. A confidentiality clause ensures you cannot disclose any non-public information about the client's business. This is standard and non-negotiable from the client's perspective. Make it mutual - you disclose confidential information too, especially about your methods and pricing. Confidentiality obligations should survive termination of the agreement, typically for two to three years.

In the current environment, if you use AI tools in your work, this section needs an addendum. Specify whether you use AI tools in your process, confirm that you won't input client confidential data into public AI systems without anonymizing it first, and clarify how AI-assisted deliverables will be disclosed. This is increasingly expected by sophisticated clients and protects you if a client later claims you mishandled their data.

9. Non-Solicitation

A non-solicitation clause prevents either party from poaching the other's employees or contractors who were involved in the engagement, typically for six to twelve months after termination. This is standard in B2B consulting relationships. Note the difference between non-solicitation (can't recruit their team) and non-compete (can't work with competitors). Non-competes are increasingly unenforceable in many U.S. states, so be careful about including broad non-compete language - it may not hold up and may scare away good clients. A narrow, time-limited non-solicitation clause addresses the legitimate concern without the legal baggage of a non-compete.

10. Termination Clause

Define how either party can end the agreement. Standard is 30 days written notice. Specify what happens to work in progress and any fees owed at termination. If you want a kill fee for projects cancelled mid-stream, include it here - a percentage of the remaining contract value due upon early termination. This protects you from a client pulling the plug after you've already allocated significant time.

Also define what constitutes termination "for cause" versus "without cause." Termination for cause (material breach, non-payment) might trigger different consequences than termination without cause. If a client terminates without cause, they should still owe you for all work completed to date plus the kill fee. If you terminate for cause due to non-payment, you should be able to walk away immediately and retain all fees owed.

11. Indemnification

An indemnification clause is different from limitation of liability - though both belong in the same agreement. Indemnification means one party agrees to compensate the other for specific types of losses. From a consultant's perspective, you want two things here:

First, the client should indemnify you from third-party claims arising from their business, decisions made based on your advice that they chose to implement, or information they provided to you that turned out to be inaccurate. Second, you should indemnify the client from claims arising from your own negligence or breach of the agreement - but limit that indemnity to your actual negligence, not blanket liability for anything that goes wrong.

Consultants can negotiate to limit their indemnification obligations to their own gross negligence, cap liability, or exclude indirect damages. Push back on any indemnification language that would make you responsible for losses that stem from the client's own implementation decisions rather than your advice itself.

12. Limitation of Liability

Cap your liability at the total fees paid under the agreement. This prevents a client from suing you for damages that far exceed what they paid you. Include language excluding consequential, incidental, and punitive damages. Without this clause, a bad outcome on a $5,000 engagement could theoretically expose you to a six-figure lawsuit.

13. Dispute Resolution

If there's a conflict, how do you handle it? Most consulting agreements specify mediation first, then arbitration, rather than going straight to litigation. Arbitration is faster and cheaper than court. Also specify governing law - which state's laws apply to the agreement. Use your home state. This matters because if you and your client are in different states, the applicable laws around things like non-competes and contractor classification vary significantly.

14. Entire Agreement and Amendments

This boilerplate clause states that the written agreement supersedes all prior verbal discussions, emails, and promises. It also specifies that changes must be made in writing and signed by both parties. This is what protects you when a client says "but you said on the call that you'd do X." If it's not in the agreement, it doesn't count. While many contract negotiations happen via email over multiple threads, those emails do not automatically become part of the agreement unless explicitly incorporated.

Sample Language for the Tricky Clauses

Here are plain-English versions of the clauses consultants most often get wrong. These aren't attorney-drafted and you should have a lawyer review your final agreement - but they'll get you to a working first draft faster.

Late Payment Interest

"Invoices unpaid after [30] days from the invoice date shall accrue interest at a rate of 1.5% per month (18% per annum) on the outstanding balance until paid in full. Consultant reserves the right to suspend services for any account more than [15] days past due until the balance is resolved."

IP Ownership (Licensed Model)

"Consultant retains ownership of all pre-existing methodologies, frameworks, templates, and tools ('Consultant IP'). Client receives a non-exclusive, non-transferable license to use deliverables incorporating Consultant IP for internal business purposes during the term of this Agreement. All custom deliverables created specifically for Client become Client's property upon receipt of full payment."

Kill Fee

"In the event Client terminates this Agreement prior to project completion without cause, Client shall pay Consultant a cancellation fee equal to [25-50%] of the remaining unbilled project fees as liquidated damages, in addition to full payment for all services rendered to the date of termination."

Limitation of Liability

"Consultant's total liability under this Agreement shall not exceed the total fees paid by Client in the three months preceding the claim. In no event shall either party be liable for indirect, incidental, consequential, or punitive damages, regardless of the cause of action or the theory of liability."

Change Order Process

"Any services requested by Client beyond the scope defined in Section 2 of this Agreement require a written change order signed by both parties prior to commencement. Consultant shall provide a written quote for additional services within [5] business days of receiving Client's request. Work on the change order shall begin only upon Client's written approval."

Deposit and Payment Schedule

"Client shall pay a non-refundable deposit of [X]% of the total project fee upon execution of this Agreement. The remaining balance shall be paid according to the following schedule: [milestone 1 - X%], [milestone 2 - X%], [final delivery - X%]. Consultant shall not be obligated to commence work until the deposit is received."

Confidentiality (Mutual)

"Each party agrees to hold in strict confidence all Confidential Information received from the other party and to use such information solely for purposes of this Agreement. This obligation of confidentiality shall survive termination of this Agreement for a period of two (2) years. 'Confidential Information' means all non-public information disclosed by one party to the other that is designated as confidential or should reasonably be understood to be confidential given the nature of the information."

How to Customize Your Agreement by Consulting Niche

The twelve sections above give you the universal skeleton. But different consulting niches have specific issues that your agreement needs to address directly. A template that works for a management consultant won't necessarily cover everything an IT consultant or marketing consultant needs.

Marketing Consultants

Marketing engagements generate a lot of IP: ad creative, copy, brand guidelines, strategic plans, campaign structures. Your agreement needs to be explicit about what the client owns versus what's licensed. If you're creating ad creative, clarify whether the client owns it outright or has a limited license. Specify the exact campaigns, advertising channels, and performance metrics you're responsible for - things like conversion rates, traffic targets, or engagement benchmarks. Also clarify whether you're responsible for strategy only, or also execution. "Marketing consulting" could mean anything. Make it mean something specific in your contract.

IT and Technology Consultants

Software development or implementation engagements have unique IP considerations. If you're building or customizing software, include warranties around software performance, what happens with bugs discovered post-delivery, and whether you'll provide maintenance or support after the project closes. Define who owns the source code - especially if you're using proprietary frameworks or reusable components. A work-for-hire clause that transfers all code to the client sounds reasonable until you realize you've also transferred a library you use across a dozen other client projects.

Financial Consultants

Financial consulting agreements need to draw a hard line between analysis and implementation. Your contract should define whether you provide analysis and recommendations only, or whether you're also involved in executing changes. This matters legally - there are licensing requirements for certain types of financial advice, and your contract language can either inadvertently imply you're providing regulated services or clearly position you as an advisor only. Make it explicit. Also include language on the client's obligation to verify information and make independent decisions based on your analysis.

HR and People Consultants

HR engagements touch sensitive employee data. Your confidentiality clause needs to explicitly cover employee records, compensation data, and personnel information. Include a section on data handling that specifies how you'll store client personnel data, when it will be destroyed, and what happens to that data at termination. If you're operating in states with robust data privacy laws, this isn't optional - it's a legal exposure question for you as the consultant.

Strategy and Management Consultants

Long-term strategy engagements often involve deep access to competitive intelligence, board-level discussions, and future business plans. Make sure your confidentiality clause covers oral disclosures as well as written ones. Strategy consultants often get roped into ongoing implementation work that wasn't in the original scope - make your change order process clear and reference it explicitly so there's no ambiguity about what's covered under the original fee.

Common Mistakes That Cost Consultants Real Money

Beyond the missing clauses above, here are the patterns I see most often - and each one has a specific fix.

• Starting work before the contract is signed. Never begin a project without a signed contract. Not even "a few hours of discovery" or a "quick kickoff call where we get into the work." The moment you start delivering value, your leverage disappears. Get the contract signed and the deposit cleared first.
• No kill fee. You block out six weeks for a project. Client cancels two weeks in. Without a kill fee, you just ate the opportunity cost of that blocked calendar. A 25-50% cancellation fee for early termination without cause is standard and reasonable - don't apologize for including it.
• Fuzzy deliverables. "Strategic recommendations" is not a deliverable. A 20-page competitive analysis delivered by the 15th of each month is a deliverable. The more specific, the better. If it can't be measured or verified as complete, it's not a deliverable - it's a vague commitment.
• IP transferred before payment. Don't hand over final deliverables or assign IP rights until the invoice is paid. State this explicitly in the agreement. "Ownership of all deliverables transfers to Client upon receipt of full payment" - seven words that protect you from doing all the work and then fighting to collect.
• Treating yourself like an employee while calling yourself a contractor. If you're operating on the client's systems, working their hours, and embedded in their org chart, the IRS may agree with them that you're an employee - regardless of what your contract says. Your conduct has to match your classification.
• No governing law clause. If you're in Texas and the client is in New York, which state's laws apply when there's a dispute? You need to specify this upfront. Use your home state.
• Accepting the client's contract without redlining. When a client sends you their own agreement, read it. Clients - especially larger companies - send boilerplate that assigns them all IP, limits your ability to do similar work for others, and exposes you to unlimited liability. You have the right to redline. In fact, sending back a thoughtfully redlined agreement signals professionalism, not difficulty.
• Overcomplicating the agreement with unnecessary jargon. Dense legal language that neither party can parse is almost as bad as no contract at all. Keep it readable. If you can't explain what a clause does in plain English, either simplify it or get a lawyer to explain it to you before you send it.

The Deposit Question: How Much to Ask For and When

Most consultants who get burned on payment issues have one thing in common: they started work before money moved. Requiring a deposit before you begin is standard operating procedure in professional services, and any pushback on it is itself a signal worth paying attention to.

For project-based work, a 25-50% upfront deposit is the standard range. For shorter projects under a few thousand dollars, 50% upfront is completely reasonable. For longer, higher-value engagements, 25-33% upfront with milestone-based payments for the remainder is common.

For retainer relationships, require the first month upfront before you begin, then invoice in advance each month. Retainers that invoice in arrears are cash flow traps - you're always working with unbilled time sitting out there. Invoice for the current month at the start of the month. If the client doesn't pay, you don't work that month. Simple.

For hourly engagements, consider requiring a pre-paid block of hours - say, ten hours minimum upfront - and replenishing that block before it hits zero. This keeps you from having to chase invoices after every billing period.

One-Page vs. Full Agreement: When to Use Each

For smaller projects - under $5,000 or short-term engagements - a simplified agreement is often more practical and easier for clients to sign without involving their legal team. The One-Page Contract Template is built for exactly this: fast, clean, enforceable.

For larger retainers, multi-month engagements, or any situation where IP ownership is significant, use a full agreement with all the sections above. The longer format gives you room to be specific about deliverables, change orders, client responsibilities, and the nuanced IP questions that shorter templates can't fully address.

A general rule: the complexity of your agreement should scale with the complexity and dollar value of the engagement. A $1,500 one-time project doesn't need a 15-page MSA. A $10,000/month ongoing retainer with access to sensitive strategic information absolutely does.

You can also use the How to Write a Contract guide to understand how to customize clauses for your specific consulting niche, and the Proposal AI Templates to build the front-end document that gets clients to the agreement stage in the first place.

How to Handle the Negotiation

Most consultants treat sending a contract as a formality. It's not. The negotiation that happens after you send the agreement is a signal about what the client relationship will look like. Here's what I've seen work:

Send the contract with the proposal, not after. Clients who see the terms upfront are more likely to sign quickly - it signals professionalism and confidence. Waiting until after verbal agreement to introduce the contract feels like a bait-and-switch to some clients and slows the close.

Don't pre-apologize for your terms. Some consultants send their agreement with language like "I know this is long, sorry, just standard stuff." Don't do this. Your terms are your terms. Present them with confidence. If a client wants to negotiate specific clauses, discuss those clauses on their merits.

Know your non-negotiables in advance. IP ownership, the kill fee, and the limitation of liability are usually worth holding firm on. Payment terms and expense reimbursement policies might have more flex depending on the client. Know before you get into the conversation which items you'll hold and which you'll move on - otherwise you end up giving away more than you planned under pressure.

Redlines in writing only. If a client wants to change something, get it in writing. Don't accept verbal agreements to modify contract terms. Email threads can work if both parties acknowledge the changes clearly - but the safest approach is to run a redlined version through a shared document and get both parties to sign the final version.

If a client refuses to sign any contract, that's a red flag. A client who won't sign anything is a client telling you they want the flexibility to dispute everything later. Walk away. The deal that looks good without a contract is the deal most likely to turn into an unpaid invoice.

Getting the Signature Without the Delay

The agreement is only useful if it gets signed. A few practical notes on reducing friction:

Use e-signature tools. DocuSign, HelloSign (now Dropbox Sign), and similar platforms make this a one-click process for clients. The easier you make it to sign, the faster it happens. PDF attachments that need to be printed, signed, scanned, and emailed back are a conversion killer in the modern world.

Set a signature deadline. When you send the agreement, note in your cover email that you're holding the start date and blocking time pending execution. "I'm holding [date] to begin onboarding - please sign by [X] to confirm." Deadlines create action. An open-ended "let me know if you have questions" sits in a client's inbox forever.

Follow up on day three if you haven't heard back. One polite check-in is appropriate. Two is fine. If a client hasn't signed by day seven with no explanation, that's a conversation worth having - find out if there's a legal review process, a concern about a specific clause, or whether they've simply gone cold on the project.

Protecting the Deal You Have While Building the Next One

A consulting agreement protects the deal you already have. But the harder problem for most consultants is getting enough deals in the pipeline to fill. If you're still manually prospecting or relying entirely on referrals, I cover outbound prospecting strategy in depth inside Galadon Gold.

And when you're ready to build a prospect list for outreach - whether you're targeting companies by industry, title, company size, or location - ScraperCity's B2B email database lets you filter and export contact lists without the per-lead costs you'd pay on most platforms. If you're doing phone-based outreach alongside your email campaigns, the mobile finder tool can pull direct dial numbers for the contacts you're targeting.

The contract matters. But so does having enough conversations to put that contract in front of people. Build both sides of the operation and you have an actual consulting business - not just a good template sitting in a folder.

FAQs: Consulting Agreement Template

Does a verbal consulting agreement hold up legally?

A verbal contract can technically be binding, but it's extremely hard to prove what the terms were. If there's a dispute over scope, payment, or deliverables, you have nothing to point to. Even a simple email thread or a one-page document is better than a verbal agreement. Always get it in writing before work starts.

Can I use the same consulting agreement template for every client?

Yes - a master template is exactly the right approach. You'll want to customize the scope of services, deliverables, timelines, and fees for each engagement, and potentially adjust clauses based on client industry or size. But the legal framework - IP, confidentiality, limitation of liability, dispute resolution - can stay consistent across engagements. That's the value of having a solid template: you're not rebuilding from scratch every time, just customizing the relevant pieces.

What's the difference between a consulting agreement and a statement of work?

A consulting agreement (or master services agreement) sets the legal and operational framework for the relationship: IP ownership, confidentiality, limitation of liability, dispute resolution, and how the parties work together. A statement of work (SOW) is the project-specific document that defines scope, deliverables, timeline, and fees for a particular engagement. When you're doing repeat work with a client, an MSA plus individual SOWs is usually more efficient than re-signing a full agreement every time.

Do I need a lawyer to review my consulting agreement?

For a standard agreement, a good template reviewed once by a local attorney is usually sufficient. The one-time investment on a template you'll use across every client engagement is one of the highest-ROI legal expenses you can make early in your consulting career. Where you definitely want legal review: any agreement that involves significant IP transfer, unusual indemnification language, or high-value engagements where the liability exposure is meaningful.

What should I do if a client sends me their own consulting agreement?

Read it carefully before signing anything. Large clients frequently send agreements that assign all IP to them automatically, include broad indemnification that exposes you to unlimited liability, or contain non-compete language that would restrict your ability to work with other clients. Redline whatever doesn't work for you, explain your reasoning professionally, and negotiate. Sending back a thoughtful set of redlines signals you're a serious professional, not someone who signs anything put in front of them.

How do I handle a client who wants to change the scope mid-project?

This is exactly what your change order clause is for. When a client asks for something outside the defined scope, acknowledge the request, note that it falls outside the current agreement, and offer to provide a change order quote. Keep the conversation professional and positive - "I'd love to help with that, let me put together a change order" - but don't start the work until the change order is signed. The moment you do work outside the contract without documentation, you've opened the door to a dispute about whether it was ever included in the original fee.