A Vendor Wants Me to Sign an NDA Before a Sales Demo. What's Too Much?

Why vendors ask

Vendors show roadmaps, pricing, unreleased features and sometimes security details during sales cycles. They want to stop that reaching competitors. That is a fair concern, and a short NDA is a normal way to address it. The issue is usually not whether to sign, but whether the NDA stays proportionate.

Make it mutual

During a demo or trial, you often share information too: your processes, data, security requirements, budget and plans. Many vendor NDAs are one-way, protecting only the vendor. Ask for a mutual NDA, or add a clause protecting your information. This matters more if you are giving the vendor sample data or access to your systems for a proof of concept.

Feedback clauses

Vendor NDAs frequently give the vendor a perpetual, royalty-free right to use any feedback or suggestions you provide. That is common and usually acceptable, as long as feedback does not include your confidential information and the vendor does not identify you. Make sure the clause says so.

Restrictions on evaluation

Some NDAs restrict benchmarking, publishing comparisons or sharing information with other vendors. It is reasonable not to disclose the vendor's non-public information to competitors. It is not reasonable to prevent you from comparing products, discussing features with your advisers or sharing pricing internally. Make sure you can share information with your employees, advisers and consultants who need it for the evaluation.

No-hire and non-solicit clauses

A demo NDA has no business including a no-hire covering the vendor's staff. Remove it, or narrow it to a non-solicit of people you actually met, for a short period.

Duration and scope

For a sales evaluation, one to three years is typical. The definition should cover non-public information marked or identified as confidential, not everything the vendor says, including marketing claims already on its website. Standard exclusions should apply.

When a trial agreement replaces the NDA

If the demo turns into a free trial or proof of concept, you will usually sign trial terms or click through the vendor's terms of service. Those terms may include data use, liability and auto-renewal provisions. Read them separately. The NDA does not govern what the vendor may do with the data you load into a trial.

A worked example

A logistics company evaluates route-planning software and signs the vendor's one-way NDA. During a pilot, it uploads real delivery data. The NDA protects the vendor's information but not the company's data, and the trial terms allow the vendor to use customer data to improve its models. A mutual NDA and a data-use restriction in the pilot terms would have protected the company's data.

Sample wording you can propose

"This Agreement is mutual. Each party may disclose the other's Confidential Information to its employees, advisers and contractors who need to know it for the Purpose and are bound by confidentiality. Feedback may be used by Vendor without restriction, provided it does not include Customer's Confidential Information or identify Customer. This Agreement does not restrict either party from hiring any person."

Common mistakes

• Signing a one-way NDA and then sharing your own data.
• Accepting restrictions on comparing products or consulting advisers.
• Missing no-hire clauses.
• Treating the NDA as covering data uploaded in a trial.
• Accepting a definition that covers public marketing information.

Quick checklist

• Is it mutual?
• Can you share information with advisers and internal teams?
• Does the feedback clause exclude your confidential information?
• Is there a no-hire or non-solicit?
• How long does it last?
• Do separate trial terms govern your data?

Key terms explained

These terms appear in most sales-stage NDAs.

• Mutual NDA: both parties' information is protected.
• Feedback clause: permission for the vendor to use suggestions you provide.
• Proof of concept: a limited trial to test whether a product meets your needs.
• Benchmarking restriction: a ban on testing or publishing product comparisons.
• Need-to-know: disclosure limited to people who require the information.

Security reviews and questionnaires

Vendors often share security documents, such as penetration test summaries and audit reports, under an NDA during procurement. That is reasonable, and your team may need to review them in detail. Make sure the NDA allows your security, legal and procurement staff, and any outside advisers, to see them.

Your side may also complete the vendor's questionnaires or share your security requirements. Those can reveal weaknesses in your systems, so they deserve protection under a mutual NDA.

Pricing confidentiality

Some vendors ask you to keep their pricing confidential, including from other vendors. Keeping a formal quote confidential is common. But you should be able to share pricing internally, with advisers and, where your organisation requires it, in procurement processes. Public-sector buyers may be subject to public records laws that override confidentiality, and the NDA should acknowledge that.

Standard exclusions

Check that the NDA contains the usual exclusions: information that is public, already known to you, independently developed or received from someone else without restriction. A missing independent development exclusion is a particular risk for a buyer with its own engineering team, which may later build something similar.

Governing law and remedies

Sales-stage NDAs usually choose the vendor's home state. That is rarely a problem for a short evaluation NDA, but watch for one-sided remedies, such as a right for the vendor to injunctive relief without a matching right for you, or attorney's fees only in the vendor's favour.

Sample email to a vendor

"Thanks for sending the NDA. We are happy to sign a short evaluation NDA. We would like it to be mutual, since we will share details of our environment, and to remove clause 9's no-hire. We also need to be able to share materials with our advisers and internal teams. Let us know if you would like our suggested wording."

When you do not need to sign

If the demo shows only public features, many vendors will proceed without an NDA. It is reasonable to ask whether an NDA is needed for an initial overview, and to sign one only when you move to detailed technical or pricing discussions.

Check the signatory

Make sure the person signing for your organisation has authority to do so. Many companies restrict who may sign contracts, including NDAs, and a sales-stage NDA signed by the wrong person can create internal problems even if the vendor treats it as binding.

Questions to ask the vendor

The answers tell you how much the NDA really matters and where to focus your review.

• What information will you share that is not already public?
• Will you need access to our data or systems during a trial?
• Can the NDA be mutual and limited to the evaluation?
• Which clauses are fixed by your legal team, and which can change?
• Will separate trial or pilot terms apply, and can we see them now?

Keep the NDA proportionate

A sales NDA should protect product secrets, not restrict your buying decision. Upload a vendor NDA or trial agreement to see which clauses go further than a demo requires.