How to Negotiate an NDA as a Freelancer (Word-for-Word Scripts)
Most freelancers read an NDA, feel vaguely uncomfortable, and sign it anyway. Not because they're reckless — because they don't know what to say. Asking a client to change a legal document feels presumptuous, especially early in a relationship. So they swallow the discomfort and hope for the best.
Here's what those freelancers are missing: NDAs are not final offers. They're opening positions. Clients draft them broadly because that's what the template says — not because every clause represents a firm requirement. When you respond with a clear, professional request and specific counter-language, most clients engage. The conversation happens. Terms get adjusted. The relationship survives and usually improves, because you've signaled that you're someone who reads what they sign.
This post is built around five email scripts — one for each of the most common NDA negotiation scenarios. Use them word-for-word, or adapt them to match your voice. The framing that matters most is the same across all five: collaborative, specific, professional.
For a broader view of what to look for before you start negotiating, NDA Red Flags covers the full list of clauses worth scrutinizing.
Yes, You Can Negotiate (Even With Big Companies)
The belief that you can't negotiate with a large client is one of the most persistent myths in freelancing. It's not true.
Big companies have legal teams whose job is to draft NDAs that favor the company — that's expected. But those same legal teams are pragmatic. A contractor who identifies a specific concern and proposes a specific fix is easy to deal with. A contractor who just says "I'm not comfortable with this" is harder. Specificity signals that you know what you're talking about, which makes you less of a risk and easier to say yes to.
The threshold for pushback varies. A Fortune 500 company with a rigid standard NDA template may have less flexibility on core confidentiality terms but more flexibility than you'd expect on ancillary clauses like non-competes, IP carve-outs, and indemnification caps. Startups and mid-size companies often have no idea what's in their NDA template and will accept reasonable changes without a second thought.
The ceiling for what's negotiable is higher than most freelancers assume. Worst case: they say no, and you decide whether to sign or walk. But that conversation happens less often than the anxiety around it suggests.
The Right Framing: Collaborative, Not Adversarial
The goal of every NDA negotiation email is to communicate three things: you've read the document carefully, you understand why the clause is there, and you want to find language that works for both parties.
What you're not doing: accusing the client of bad intent, demanding they remove the clause entirely, or treating the negotiation as a confrontation.
This framing isn't just strategic politeness — it reflects something true. Most clients don't intend the harshest possible reading of their NDA. They drafted it broadly because that's what the template said, and no one has ever pushed back. When you say "here's a concern, here's a fix that addresses your underlying interest while protecting me," you're doing the work their legal team didn't.
The scripts below are written in this register: specific, professional, focused on mutual workability. The one adjustment you may want to make is matching the formality level to the relationship. An email to a startup founder you've been trading messages with can be slightly warmer. An email to an enterprise procurement contact should be more formal.
Script 1 — General Opener: "I Have a Few Suggested Changes"
Use this when you have multiple small concerns across the NDA and want to open the conversation without diving into clause-by-clause details in the first email.
Subject: NDA — Suggested Revisions Before I Sign
Hi [Name],
Thanks for sending the NDA. I've reviewed it carefully and I'm happy to move forward — I just have a few suggested revisions before I sign.
Nothing substantial: I've attached a redline with tracked changes and brief comments explaining each one. Most are fairly minor adjustments to bring a few clauses more in line with standard contractor terms. The core confidentiality obligations are completely fine.
Happy to jump on a quick call if it's easier to discuss any of them directly, or feel free to accept, reject, or counter in the document.
Looking forward to the project.
[Your name]
A few things this script does deliberately. It leads with a positive — you're happy to move forward — before mentioning any issue. It characterizes the changes as "suggested revisions," not demands. It reassures the client that the confidentiality obligations (the thing they actually care most about) are fine. And it offers a call as an alternative to email back-and-forth, which reduces friction.
If you don't have a redline ready, you can substitute "I've outlined my comments below" and list the specific points in the body of the email.
Script 2 — Negotiating a Non-Compete Clause
Non-compete clauses in freelance NDAs are often the most consequential terms in the document. A clause that's too broad can lock you out of your primary market for years. For a full breakdown of how to assess the four risk dimensions of any non-compete, read NDA Non-Compete Clause: What It Means and When to Push Back.
Use this script when the non-compete is too long, too broad geographically, or defines "competitor" too loosely.
Subject: NDA — Non-Compete Clause, Section [X]
Hi [Name],
I've reviewed the NDA and I'm comfortable with the confidentiality terms. Before I sign, I'd like to discuss Section [X], the non-compete provision.
As drafted, the clause restricts me from working with "any company in [Client's] industry" globally for [duration]. I want to be able to commit to this agreement fully, which means I need language I can realistically comply with while still maintaining my freelance practice.
I'd like to propose the following replacement for Section [X]:
"For a period of twelve (12) months following the termination of this Agreement, Contractor agrees not to provide services directly to the companies listed in Exhibit A (Direct Competitors). This restriction applies only within the geographic markets where Client operates as of the termination date. Nothing in this section prevents Contractor from working with entities not listed in Exhibit A, including other companies in Client's general industry."
If you'd prefer not to use a named-competitor list, I'm also open to narrowing the industry definition and reducing the duration to twelve months. Happy to discuss either approach.
[Your name]
The key move here is offering two paths: a named-competitor list (the cleaner solution) or a narrowed industry definition. Giving the client a choice makes it easier for them to say yes to something.
Script 3 — Adding a Pre-Existing IP Carve-Out
Without a carve-out for pre-existing intellectual property, an NDA can inadvertently assign work you've done before the engagement to the client. This matters most for freelancers who work across multiple clients using the same frameworks, code libraries, design systems, or methodologies.
For a detailed explanation of how IP clauses work in NDAs, read NDA IP Clause: What Freelancers Need to Know.
Subject: NDA — Pre-Existing IP, Section [X]
Hi [Name],
I've gone through the NDA and I'm on board with the confidentiality terms. One thing I'd like to address before signing is the IP section.
As currently written, Section [X] assigns all work product created during the engagement to [Client]. I want to make sure we're aligned that this applies to work I create specifically for this project — not to tools, frameworks, or methodologies I've developed independently and use across client engagements.
I'd like to add the following carve-out language:
"The assignment in this section applies only to work product created specifically for Client under this Agreement. It does not apply to any tools, frameworks, code libraries, or methodologies developed by Contractor prior to or independently of this engagement ('Pre-Existing IP'). Contractor retains all rights to Pre-Existing IP. To the extent any deliverable incorporates Pre-Existing IP, Contractor grants Client a non-exclusive, royalty-free license to use such Pre-Existing IP solely as incorporated in the deliverables."
This is standard language in contractor agreements. It doesn't affect your ownership of anything created for your project — it just preserves my ability to continue using my own tools with other clients.
[Your name]
The last paragraph does important work: it makes clear that the carve-out doesn't diminish the client's ownership of the actual deliverables. That's usually the reassurance clients need.
Script 4 — Reducing Confidentiality Duration
Perpetual confidentiality clauses — "the obligations under this Agreement shall survive indefinitely" — are common in template NDAs and often unnecessary. Market standard for most business information is three to five years. Trade secrets and genuinely sensitive technical information may warrant longer, but generic business confidentiality obligations don't need to run forever.
Subject: NDA — Confidentiality Duration, Section [X]
Hi [Name],
Thanks for the NDA. I'm comfortable with the confidentiality terms in substance. Before signing, I'd like to raise one point about duration.
Section [X] sets confidentiality obligations that survive "indefinitely" (or "in perpetuity"). I understand the intent — you want to make sure sensitive information stays protected — and I'm fully committed to that. My concern is committing to an obligation with no defined end date.
I'd like to propose the following revision to Section [X]:
"Confidentiality obligations under this Agreement shall remain in effect for a period of five (5) years following the termination of this Agreement, except that obligations with respect to trade secrets shall continue for as long as the information qualifies as a trade secret under applicable law."
This gives you strong protection for the information that actually needs it — trade secrets are covered for as long as they remain secret — while setting a defined endpoint for general business confidentiality.
Happy to adjust the duration if five years doesn't feel sufficient for your use case.
[Your name]
The trade secret carve-out is the piece most clients need to see before they'll agree to a duration cap. It signals that you understand the difference between generic business information and genuinely sensitive IP, and that you're not trying to undermine protection for the latter.
Script 5 — Pushing Back on Unlimited Indemnification
Indemnification clauses that hold you liable for any claim arising from your work — with no cap — are a serious risk for freelancers. You're typically not carrying the same insurance as a large agency, and an uncapped indemnification clause can expose you to liability far exceeding the value of the contract.
Subject: NDA — Indemnification Clause, Section [X]
Hi [Name],
I've reviewed the NDA and there's one section I'd like to discuss before signing: the indemnification clause in Section [X].
As written, I'm indemnifying [Client] against any and all claims arising from my work with no limitation on liability. I take my obligations seriously, but I can't responsibly accept unlimited financial exposure — particularly on a project where my fee is [amount].
I'd like to propose capping the indemnification at the total fees paid under this Agreement, which is a standard approach in contractor NDAs:
"Contractor's total liability to Client under this Agreement, including under any indemnification obligation, shall not exceed the total fees paid by Client to Contractor in the twelve (12) months immediately preceding the claim giving rise to liability. This limitation shall not apply to liability arising from Contractor's gross negligence or willful misconduct."
The carve-out for gross negligence and willful misconduct is intentional — I'm not trying to limit accountability for serious failures, only to make the liability proportionate to the engagement value.
Happy to discuss.
[Your name]
The gross negligence carve-out is important to include because it makes the proposal more credible. A freelancer who says "I want unlimited protection from liability" sounds like they're planning to do bad work. A freelancer who says "cap it at the contract value, except for serious misconduct" sounds like someone with a sensible understanding of proportionality.
What to Do If the Client Says No
A client saying no to a negotiation request isn't the end of the conversation — it's information. How you respond depends on which clause they're refusing to change and what the stakes are.
Option 1: Accept the term as-is. This makes sense when the practical risk is low. A global non-compete from a startup with no legal budget and a two-month project timeline is a different risk than the same clause from a well-resourced enterprise. Assess the actual likelihood of enforcement before walking away from a good engagement.
Option 2: Counter again with a smaller ask. If they reject your full proposal, offer a more limited version. On a duration issue, if they won't move from three years, try eighteen months. On a non-compete scope issue, if they won't use a named-competitor list, try a narrower industry definition. Each round of counter narrows the gap and often produces a middle ground neither party initially proposed.
Option 3: Ask for a written confirmation of intent. If a client tells you verbally or informally that they "would never enforce it that way," ask them to confirm in an email. It's not the same as a modified contract, but it creates a record that may be useful if the clause is later invoked. Some clients are more willing to send an email than they are to formally revise the document.
Option 4: Walk away. Some clauses are worth walking away over, and some clients won't move on them. That's a legitimate outcome. The fact that you tried to negotiate and they refused tells you something about how they approach legal relationships — and how they'll behave when something goes wrong mid-project.
The right choice depends on the clause, the client, and the value of the engagement. But having this decision framework before the conversation starts means you're not improvising under pressure.
Red Lines — Clauses Worth Walking Away Over
Not every NDA concern justifies walking away. But some clauses represent exposure serious enough that no engagement value justifies accepting them without modification. These are the terms where "they said no" should usually end the conversation.
Unlimited, uncapped indemnification with no liability floor. If you're personally responsible for any claim of any size with no ceiling, a single dispute can exceed the value of every project you've ever worked on. This is especially dangerous for solo freelancers without corporate protection.
A non-compete that covers your entire primary market, globally, for more than two years. A clause this broad isn't protecting a legitimate client interest — it's restricting your ability to earn a living. For a detailed breakdown of what makes a non-compete dangerous, see NDA Non-Compete Clause.
IP assignment with no pre-existing work carve-out. If your entire methodology, framework, or body of tools could be claimed by the client, you may be signing away your core professional asset. See NDA IP Clause for the full analysis.
Automatic injunction rights with no cure period. Some NDAs give the client the right to seek an emergency court order the moment they believe a breach has occurred — no notice, no opportunity to remedy. These clauses are designed for situations involving genuine irreplaceable harm, not routine contractor disputes, and they shift far too much power to the client.
One-sided governing law in an unfamiliar jurisdiction. A contract governed by the laws of a state or country where you have no presence and no access to affordable legal counsel is a practical one-sidedness even if the substantive terms are fine. It's not always a deal-breaker, but it's worth flagging.
FAQ
How do I bring up NDA changes without damaging the relationship?
Lead with your commitment to the project and your understanding of the client's confidentiality interest. Frame your ask as ensuring you can commit to what you're signing, not as distrust of the client. The scripts in this post are written in that register. Most clients who receive a professional, specific negotiation request respond positively — it signals that you're careful and thorough, which is usually what they hired you for.
Do I need a lawyer to negotiate an NDA?
Not for routine requests. The scripts in this post cover the most common situations and are designed to be used without legal counsel. You should involve a lawyer when the contract value is high, when the clause involves unusual or novel terms you don't recognize, or when a dispute is already in progress. For a standard freelance NDA with the usual clause types, a clear understanding of the terms and professional framing is usually sufficient.
What if they send me a new version with even worse terms?
This is rare but happens. If a client responds to your negotiation request by adding restrictions rather than adjusting existing ones, treat it as a meaningful data point about how they approach the relationship. You can address specific new additions the same way you addressed the original issues. If the dynamic feels adversarial rather than collaborative at this stage, pay attention to that signal.
Should I use redline markup or just list my requests in an email?
Either works, and the right choice depends on the client. For clients with active legal teams, a redline in Word or Google Docs is faster for them to process — they're accustomed to tracked changes. For startup founders or small business clients, a clear email listing specific sections and proposed replacement language is often easier to engage with. If in doubt, do both: send the email with the explanation and attach a redlined document.
Can I negotiate an NDA after I've already started working?
You can try, but your leverage decreases significantly once you've begun delivering work. The strongest position to negotiate from is before you sign and before the project starts. If you've already started, you can still raise concerns — frame it as wanting to ensure the agreement reflects the actual scope of the relationship — but the client has less incentive to make changes. If you're already working without a signed NDA, getting a fair agreement signed is still worth pursuing.
The Conversation Most Freelancers Never Have
Most NDA negotiations don't happen because freelancers assume the conversation will go badly. The client will be annoyed. The project will fall through. The relationship will start on a sour note.
In practice, the opposite is more common. Clients who receive a professional, specific negotiation email often come away with a higher opinion of the contractor — someone who reads carefully, communicates clearly, and knows what they're agreeing to. That's the kind of person you want to hire.
The five scripts above give you everything you need to start the conversation. If you want to know what to look for in the NDA before you start negotiating, NDA Red Flags covers the full list. If the non-compete section is the main concern, NDA Non-Compete Clause goes deep on how to assess and counter it. And if you want a faster path through the whole document, NDA Guard flags problem clauses automatically — risk-scored, in plain English, with counter-language ready to adapt.
Read before you sign. Ask for what you need. Most clients say yes.