The first time a client said, “Tell no one”
Last Thursday at 10 p.m., I was waiting for a client’s reply in a Hangzhou café. They said the project was worth discussing, but wanted me to sign an NDA first—and preferably not disclose even the process of preparing my quote. My first reaction wasn’t to refuse. I panicked a little: was I so inexperienced that even a normal quote was something to hide? Later, I realized many confidentiality requests aren’t aimed at your quote at all. They often mean the partner isn’t ready to announce the project yet.
This isn’t just an entrepreneur problem
When OpenAI outlined its approach to new data-center partnerships, it put “public representatives won’t be forced to sign NDAs” up front, emphasizing public explanation and local consultation. In plain terms: the project can stay confidential, but who owes confidentiality to whom, when it can become public, and what must stay out of the quote all need to be clear in advance.
I know Lin Xiao, who leads a small government-training team. After receiving a procurement inquiry in Suzhou, she didn’t sign an open-ended confidentiality document first. Instead, she confirmed four things: whether the client’s name could be public, whether the quote could be used as a case study, when the project would be announced, and which materials each side could use. She also learned this the hard way. Early on, she placed the entire quote behind an NDA, and the client assumed she was still talking to other suppliers. Communication slowed instead of speeding up. Now she separates a public version from an internal version and lets both sides choose.
What it costs to replicate this today
Money: 0 yuan; use the contract template you already have. Time: 30–60 minutes to define the boundaries. Technical barrier: no coding needed; knowing how to use a document is enough. First step: open the NDA you’re currently discussing and find “Confidential Information” and “Public Disclosure.” Mark whether the quote, client name, or project process is covered. If you haven’t faced any confidentiality issue, there’s no need to force this today—not every order needs a complicated process.
How I’d approach this at each stage
If I were just starting out without a stable client base, I’d first write down the quote scope, service contents, and delivery timeline, then decide whether an NDA is actually necessary. There’s no need to build a complex workflow from day one.
If I already have one or two clients, I’d add one line to our first formal conversation: “Does the quote need to stay confidential, and can we use an anonymous case study after the project ends?” I’d record the answers in an email so neither side has to rely on memory.
If I’m scaling and several people are involved, I’d create a minimal public-disclosure checklist: who inside can know about the project, what can be said externally, and when written client approval is required. It won’t eliminate every risk, but it can reduce the gap between “I thought we could mention it” and “I thought we couldn’t.”