What should I do about signing an NDA before discussing the project scope?

[NicholasT]

I’ve just had a potential client ask me to sign an NDA before we even discuss the project scope. I’m not sure if this is standard or if I should be pushing back to see the actual work details first, since it feels like I’m locking myself into confidentiality without knowing what I’m agreeing to keep secret.

[Tyler_S]

That happens a lot. I usually push for a short intro call first and offer a lightweight confidentiality document that only covers what we actually discuss. It keeps me from signing away things I don’t know I’ll be protecting.

[Gary_A]

I signed something similar before we talked scope and it slowed me down when the project pivoted. It felt like a trap, so I learned to push for scope first whenever possible.

[VioletG]

Two-step makes sense to me: first the discovery chat, then a mutual confidentiality agreement that’s limited to the topics we outline. Not perfect, but better than locking me in for everything.

[PatrickRT]

Is the real problem that they won’t share the scope unless you sign an NDA?

[KevinDP]

I once brewed too much coffee waiting for a reply and ended up just proposing a quick call with a slim confidentiality clause that only covers what we actually exchange. If the project or data changes, we renegotiate.