Do I need an NDA? Here is when it matters.

Founders often ask for an NDA before telling anyone about an idea. Others share a formula, supplier list or unreleased design and only think about confidentiality afterwards. Neither approach starts with the most useful question: What information am I about to disclose, to whom, and why?

An NDA, or non-disclosure agreement, is a contract that sets rules for confidential information. It can restrict disclosure and use outside an agreed purpose. It is useful when the other person needs access to something genuinely sensitive to evaluate or perform a project. The document should fit the conversation, not serve as a reflex before every introductory meeting.

When should you consider an NDA?

Before sending a manufacturer detailed information. An initial enquiry can describe the product at a high level. Once you share an unreleased design, technical specification, custom pattern, formula, process or sourcing information, consider confidentiality terms first. If the manufacturer will use a subcontractor, decide whether and how that information may reach them.

Before giving an agency or freelancer access to your plans. A designer, packaging studio, developer or marketing partner may see launch plans, customer data, pricing, supplier terms or unpublished creative work. A confidentiality clause in the services agreement may be enough; a separate NDA can help when you need to share information before the main contract is ready.

During serious discussions with a commercial partner. A prospective distributor, collaborator, buyer or business partner may need commercially sensitive information to assess the deal. Start with what they need to know, then use appropriate terms before sharing detailed data. Investors may have their own process and may decline a broad NDA at an early pitch stage; use a staged approach to disclosure rather than assuming every conversation will begin with a signature.

When you are exploring something you may want to protect formally. If you plan to seek patent or design protection, public disclosure can affect your position in some jurisdictions. Get advice on the relevant filing strategy before sharing or publishing technical details. An NDA may be part of that strategy, but it is not a substitute for it.

When might you not need a separate NDA?

If you are discussing only a broad concept already visible in the market, there may be little confidential information to protect. If an existing employment, services or supplier contract has suitable confidentiality obligations, another document may add little. The real question is whether the existing clause covers the people, information, purpose and period involved.

You also do not have to reveal everything in the first meeting. A short non-confidential introduction can establish interest before you disclose the commercially important details.

What should the NDA actually say?

A useful NDA should identify the parties and the reason information is being shared. It should explain what is confidential, who may receive it, how it may be used, how long obligations last, what happens when discussions end and how documents or copies will be handled. Consider ordinary exclusions for information already public, already lawfully known or independently developed. The right approach depends on the transaction and applicable law.

Pay particular attention to use, not just disclosure. A founder may care less about a factory telling someone else the idea than about the factory using the design or information to develop a competing product. The permitted purpose and restrictions should reflect the actual risk. A one-way NDA may fit when only you disclose sensitive information; mutual terms make sense when both sides do.

What an NDA does not do

An NDA does not automatically transfer ownership of designs, formulas, code, patterns or other intellectual property. It does not say who owns new work created together. It does not guarantee that an idea is unique, register a trade mark, replace a manufacturing or services agreement, or prevent all possible misuse. Its practical value depends on clear terms, evidence of what was shared and the law and jurisdiction relevant to the relationship.

If a manufacturer is developing your product, the later manufacturing agreement should address ownership and use of existing and newly created work, samples, specifications, quality, price, timing, defects and termination. The confidentiality obligations should continue appropriately into that relationship. If an agency is creating your brand, its services agreement should address deliverables and ownership of the work you pay for.

A simple decision test

Before sharing information, ask yourself:

• —Is this information non-public and valuable to the business?
• —Does this person need the detail now, or can I begin with a general brief?
• —What exactly may they do with it, and who else may see it?
• —Is confidentiality already covered by a suitable contract?
• —Will this relationship create new work that needs separate ownership and commercial terms?

If the information matters and it needs to be shared, put the right terms in place before disclosure. Then keep a record of what you provided. The objective is to move the business forward while protecting the parts that give it value.

Mother's view

You do not need an NDA for every conversation. You need to know what you are sharing, why you are sharing it and which agreement protects the relationship that follows.