Redline
Sign in
← All articles

What to Do When a Client Won't Sign an NDA

August 22, 20265 min read

You ask your new client to sign an NDA before you start discussing their project. They refuse. Maybe they say their legal team won't approve it. Maybe they say they don't sign NDAs on principle. Maybe they just ghost you for two days and come back pretending you never asked.

This happens more often than you'd think. Here's how to handle it without losing the deal or exposing yourself.

When an NDA Actually Matters

Not every project needs an NDA. If a client is hiring you to build a public-facing marketing website, there's likely nothing confidential involved. But if you're working with proprietary data, internal tools, trade secrets, or unreleased products, an NDA makes sense.

Ask yourself: "If I accidentally mentioned this project's details to someone, could it harm the client?" If yes, an NDA is warranted.

Why Clients Refuse

Understanding the refusal helps you respond appropriately:

Legal overhead: Small businesses without in-house counsel see every legal document as a cost. Their lawyer charges $300/hr to review your NDA.

Bad experiences: They've had a freelancer use an NDA as leverage in a dispute.

Principle: Some founders believe in radical transparency and refuse NDAs categorically.

Red flag: They plan to share your ideas with cheaper competitors. This is the scenario you're trying to protect against.

Alternatives to a Formal NDA

If the client won't sign a standalone NDA, you have options:

Confidentiality clause in your contract: Add a section to your main service agreement that covers confidentiality. Most clients who resist a separate NDA will accept this since they're already signing a contract anyway.

Email acknowledgment: Send an email that says "I'll treat all project information as confidential and expect the same regarding my processes and deliverables." Ask them to confirm. This creates a basic written record.

Limit what you share: Don't reveal your full strategy or proprietary methods in the proposal phase. Share enough to demonstrate competence, but keep the detailed execution plan for after the contract is signed.

When to Walk Away

If the project involves genuinely sensitive information — financial data, health records, security systems, proprietary algorithms — and the client refuses any form of confidentiality protection, that's a warning sign. A client who won't protect their own sensitive data is unlikely to respect yours.

The Practical Approach

For most freelance projects, a confidentiality clause within your service contract is sufficient. Save the standalone NDA for projects where you're handling genuinely sensitive information. And always put something in writing — even a brief email — before you start discussing specifics.

Want to check your own contract?

Paste it into Redline and get a risk analysis in under 30 seconds.

Review a contract free