A Client Wants You to Sign an NDA Before a Discovery Call: What to Do
- Most pre-call NDAs are boilerplate, one to two pages, and reasonable to sign as-is once you check three things: it is mutual, it has a real expiration date, and it only covers information the client actually shares, not everything you happen to know.
- Push back on three specific clause types: one-sided NDAs that only bind you, non-compete or ownership language buried inside what should be a confidentiality document, and NDAs with no end date at all.
- Never let a reasonable NDA stall the call. It should take five minutes to read and sign. Reserve real hesitation for the client who cannot explain, in one sentence, what specifically needs to stay confidential.
Why Clients Ask for an NDA Before a Call
Most of the time the reason is boring: the client is going to describe something specific, a product idea, a customer list, an internal process, and they want a basic assurance you will not repeat it before there is any relationship between you. It is a normal part of doing business with people who have something real to protect, and it says nothing about how difficult the client will be to work with.
Treat the request as neutral until you have actually read the document. The NDA itself, not the fact that one was sent, is what tells you whether this is a five-minute formality or something to slow down on.
The Three Things to Check Before You Sign Anything
- Is it mutual? A one-directional NDA that only restricts you, while leaving the client free to discuss the call with anyone, is worth a polite request to change to mutual language. Most legitimate clients will not object; the ones who do are telling you something.
- Does it have a real end date? A confidentiality obligation that runs one to three years after the engagement ends is standard. One with no expiration date at all, or one that claims to bind you indefinitely, is worth pushing back on.
- Is the scope limited to what they actually tell you? A reasonable NDA covers information the client discloses in the conversation. Watch for language broad enough to cover your own pre-existing methods, tools, or knowledge, since that would restrict you from using your own expertise on the next client.
Clauses That Do Not Belong in a Pre-Call NDA
| Clause | Belongs in a pre-call NDA? | Why |
|---|---|---|
| Confidentiality of information shared in the call | Yes | This is the actual purpose of the document |
| A defined end date on the obligation | Yes | Confidentiality that never expires is unusual to ask a stranger to sign |
| Non-compete or restriction on working with similar clients | No | That is a separate negotiation for after you are actually hired, not a condition of a first conversation |
| Ownership of ideas or IP discussed on the call | No | Ownership belongs in the project agreement once there is a scope and a price, not a pre-call confidentiality form |
| A requirement to use the client's own contractor agreement going forward | No | This is a sign the NDA is really an attempt to lock in future contract terms before you have quoted anything |
What a confidentiality agreement should and should not contain
The pattern to watch for is scope creep in the document itself, the same instinct that shows up later as [scope creep in the project](/blog/scope-of-work-that-prevents-scope-creep). An NDA that tries to do the job of a non-compete, an IP assignment, and a services agreement all at once is not really an NDA. Ask for it to be split into the piece that actually matters right now, confidentiality about this call, and tell the client the rest belongs in the engagement agreement once there is a real scope to sign.
What to Say When You Want a Change
Do not disappear into silence while you think it over, and do not sign something you are not comfortable with just to avoid an awkward exchange. A short, direct message moves this along faster than either option: 'Happy to sign this. Two small changes: can we make the confidentiality mutual, and can we cap it at two years from today? Otherwise this looks good.'
This does two things at once. It signals you read the document closely, which most people do not, and it gives the client a specific, easy yes instead of an open-ended negotiation. Most of the time you get a revised version back within the day.
When the NDA Itself Is the Warning Sign
Occasionally the document is the tell. A ten-page NDA for a single discovery call, language that tries to claim your general skills and prior work as confidential simply because you mentioned them on the call, or a refusal to send the document until after you have already described your process in detail, are all reasons to slow down before the call even happens, not just before you sign.
None of these are automatically disqualifying. Larger companies sometimes run every external conversation through the same heavyweight template regardless of the stakes involved. The distinction that matters is whether the client can explain, in one sentence, what specifically needs protecting. 'We have not announced this publicly yet' is a real reason. Vague discomfort with any conversation not covered on paper usually is not.
How This Fits the Rest of the Sales Process
An NDA request sits before [your first discovery call](/blog/your-first-discovery-call), not instead of it, and it should not change how you run the call once it is signed. Keep the same structure: understand the problem, confirm you can solve it, and [set expectations](/blog/set-client-expectations-before-a-claude-code-build) before you talk price. The NDA protects the conversation. It does not replace the actual agreement you will sign once there is a scope and a number, which is also where [who owns the finished code](/blog/who-owns-the-code-you-build-for-a-client) actually gets decided, not here.
Common Mistakes
- Signing a one-sided or open-ended NDA without asking for the two changes that take a client thirty seconds to make: mutual language and a real end date.
- Treating every NDA request as a red flag and losing a normal, well-qualified prospect over a routine formality.
- Letting an NDA's vague confidentiality language quietly restrict you from using your own general skills and methods on the next client.
- Negotiating IP ownership or non-compete terms inside the NDA itself instead of pointing that conversation to the actual project agreement, where it belongs.
Inside the Claude Code Profit Room, builders share the actual NDA language clients have sent them, the redlines that worked, and the one or two requests that were worth walking away from. It's $9 a month at https://www.skool.com/claudecodeprofitroom/about, bring the document if you have one sitting in your inbox right now.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
Should I sign an NDA before a discovery call?
In most cases, yes, once you have checked that it is mutual, has a real end date, and only covers what the client actually discloses on the call. A routine NDA is a five-minute read, not a reason to stall a normal sales process.
What if the NDA only restricts me and not the client?
Ask for it to be made mutual before you sign. Most clients will agree without pushback, since a mutual NDA protects both sides equally. A flat refusal to make a basic confidentiality document mutual is worth noting.
Can an NDA stop me from using my own skills on future clients?
It should not, but broadly written confidentiality language sometimes reaches further than it needs to. Read for language that could cover your own pre-existing methods or knowledge, not just what the client tells you in the call, and ask for it to be narrowed if it does.
Is it normal for a client to want an NDA before even describing the project?
Yes, especially if the project touches something they have not announced publicly, like a product idea or an internal process. It says nothing on its own about how the engagement will go. Read the actual document rather than reading meaning into the request.
What belongs in the NDA versus the actual project agreement?
The NDA should cover confidentiality of what is discussed on the call, nothing more. IP ownership, non-compete terms, and contractor requirements belong in the project agreement once there is a real scope and price, not in a document meant to protect one conversation.
Last reviewed August 30, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →
