NDA For Product Demo: What Startups Should Include

Maya has built a workflow tool that automates a painful admin task for healthcare clinics. Before her first enterprise demo, the potential customer asks for screenshots, wants to record the call, and says three people from its product team may join.

That's exciting, but it also feels a little exposed. You want to show enough to win the deal without giving away your unreleased features, pricing strategy, roadmap, or technical know-how.

An NDA for a product demo can help set the rules before you share anything sensitive. It doesn't have to be complicated, but it does need to be clear about what the other side can do with your information during and after the demo.

Do I Need An NDA Before A Product Demo?

Yes, if you're showing non-public technology, product plans, pricing, customer data, security materials, or anything else that could hurt your business if it were shared or copied.

An NDA, also called a confidentiality agreement, is a contract. It sets out what information is confidential, who can see it, what they can use it for, and what happens when the discussion ends.

For software and product demos, an NDA is especially useful when you're showing:

• Unreleased features or an early prototype
• Architecture diagrams, API documentation, data flows, or security documents
• Product roadmap details or launch timelines
• Commercial pricing, discounting, or customer pipeline information
• Training materials, pitch decks, or demo environments that aren't public
• Customer lists, usage metrics, or analytics

At the federal level, your trade secrets may be protected under the Defend Trade Secrets Act if you take reasonable steps to keep them secret and the information has independent economic value because it isn't generally known. A written NDA can be one of those reasonable steps.

Copyright can also help protect software code, designs, documents, screenshots, and other original works under the Copyright Act. But copyright doesn't stop someone from learning your business idea or building their own version using information you freely shared. That's where confidentiality terms matter.

State contract law also affects how NDAs are interpreted and enforced, so the wording should fit your business and the state law that governs the agreement.

What Should A Product Demo NDA Cover?

A product demo NDA should cover the information you're sharing, the purpose of the demo, who can access the information, and what the recipient isn't allowed to do with it.

A good software demo confidentiality agreement usually includes these core parts:

• The parties: Name your company and the customer, investor, partner, consultant, or vendor receiving the information.
• The purpose: Say the information can only be used to evaluate a possible business relationship, purchase, investment, pilot, partnership, or integration.
• Confidential information: Cover spoken, written, visual, electronic, and demonstrated information, including the demo itself.
• Exclusions: Information shouldn't be confidential if it was already public, already known to the recipient, independently developed without using your information, or lawfully received from someone else.
• Use restrictions: The recipient shouldn't copy, reverse engineer, benchmark, publish, share, or use your information to build a competing product.
• Permitted disclosures: Limit sharing to employees, contractors, advisors, or affiliates who genuinely need to know and are bound by employee confidentiality or invention assignment obligations.
• Return or deletion: Set out what happens to notes, recordings, screenshots, documents, and access credentials when the evaluation ends.
• Duration: Use a sensible confidentiality period, and treat trade secrets as confidential for as long as they remain trade secrets.

For a demo, the purpose clause is doing a lot of work. If it just says business discussions, the recipient may argue they had broad permission to use the information internally. A tighter clause might say the information can only be used to evaluate whether to buy your product after a demo on a specified date.

Also think about the direction of information flow. If you're only sharing your information, a one-way NDA may be enough. If both sides will share sensitive information, such as security requirements, customer workflows, or integration data, you may need a mutual NDA.

How Should The NDA Handle Screenshots, Recordings And Feedback?

Your NDA should deal with screenshots, recordings, and feedback directly, because those are the places where demo confidentiality often gets messy.

Screenshots And Copies

If you don't want screenshots, say so. If you're comfortable with limited screenshots for internal evaluation, say who can take them, where they can be stored, and when they must be deleted.

For example, you might allow the recipient to keep up to five screenshots in an internal evaluation memo for 60 days, but not allow public posting, sharing with competitors, or use in training data, marketing materials, or product design documents.

Recordings

Call recordings can be helpful, but they can also preserve your entire demo, roadmap discussion, and Q&A in a file you no longer control. Your NDA can say the demo may not be recorded unless you approve it in writing first.

If you do allow recording, consider adding limits such as:

• The recording can only be used to evaluate your product
• Access is limited to named teams or approved personnel
• The recording can't be downloaded to personal devices
• The recording must be deleted after a set period, such as 30, 60, or 90 days
• The recipient must confirm deletion if you request it

Feedback And Suggestions

Feedback can be valuable, but it can create awkward ownership questions if the customer suggests a feature you later build. Your NDA should say what happens to feedback, comments, ideas, and suggestions given during the demo.

Many startups prefer a clause saying they can use feedback without owing compensation, as long as they don't disclose the recipient's confidential information. If you're demoing to a strategic partner or enterprise customer, this may need careful drafting because the customer may want limits too.

Say Maya allows a 45-minute recorded demo for a hospital software buyer. Her NDA says the recording can be viewed by the buyer's procurement and IT security teams for 60 days, can't be shared with vendors, and must be deleted if the buyer doesn't proceed. That gives the buyer enough room to evaluate the tool while keeping Maya's unreleased workflow engine under control.

Should Customers And Investors Sign The Same NDA?

Usually, no. Customers and investors often need different NDA wording because they're looking at your business for different reasons.

Customer Demos

For customers, your NDA should focus on product use, evaluation, screenshots, recordings, security materials, and access to demo environments. If you're offering a pilot, trial, or bundled product, the NDA may sit alongside a trial agreement, terms of service, data processing terms, or a master services agreement.

Customer demo NDAs often need practical operational clauses, such as:

• No reverse engineering or testing beyond the approved demo use
• No sharing login details or demo links outside the approved team
• No scraping, copying, or exporting demo content
• No public comments, press, or social media posts about unreleased features
• No use of your information to build, train, or improve competing products

Investor Demos

Investors can be more complicated. Some investors refuse to sign NDAs at the early pitch stage because they see many similar businesses and don't want restrictions that could create conflicts later.

That doesn't mean you have to reveal everything. You can structure the process in stages. For example:

1. Share a high-level deck without your deepest technical details.
2. Hold back sensitive code, formulas, algorithms, customer data, and detailed roadmap items.
3. Ask for an NDA before sharing a data room, technical demo, founders agreement, shareholder agreement, key customer contracts, or sensitive financial materials.

If an investor won't sign an NDA, decide what you're comfortable sharing without one. For patentable technology, speak with a licensed attorney before public disclosure, because patent rights can be affected by timing and public disclosure rules.

If you're using the same startup NDA template for every audience, pause before you send it. A template may be fine as a starting point, but demo terms work best when they reflect who is receiving the information and what they'll actually see.

NDA For Product Demo Template: What To Include

A product demo NDA template should give you a sensible structure, but a lawyer should tailor it before you use it with customers, investors, partners, or enterprise buyers.

Here is a practical outline you can use to brief your attorney or review a draft:

1. Title And Date: Call it a confidentiality agreement or NDA and include the date it takes effect.
2. Parties: Insert the full legal names of your company and the recipient, not just trading names or email domains.
3. Background: Explain that you're discussing a possible demo, pilot, investment, partnership, integration, or commercial arrangement.
4. Purpose: State the narrow reason the recipient can use the information, such as evaluating your product after a demo.
5. Confidential Information: Include oral, visual, written, electronic, technical, commercial, and demo-based information.
6. Demo-Specific Materials: Mention screenshots, recordings, login credentials, test accounts, screen shares, decks, recordings, and sandbox data.
7. Recipient Obligations: Require the recipient to protect the information, limit access, and use at least reasonable care.
8. Restrictions: Ban unauthorized copying, reverse engineering, public disclosure, competitive use, and training of internal or external tools unless approved.
9. Permitted Disclosures: List who may receive the information and require those people to keep it confidential.
10. Required Disclosures: If the recipient is legally required to disclose information, require prompt notice where legally allowed and limit the disclosure as much as possible.
11. Feedback: Say whether you can use feedback and suggestions without payment, and protect any confidential information included in that feedback.
12. Return And Deletion: Set out when materials, copies, recordings, and access credentials must be returned, deleted, or disabled.
13. Term: Set a confidentiality period, such as two or three years for general business information, with trade secrets protected while they remain trade secrets.
14. Remedies: Include the right to seek court orders if confidentiality is breached, while remembering that court processes and remedies vary.
15. Governing Law And Signatures: Choose the governing law and allow electronic signatures, which are generally recognized under the federal E-SIGN Act and state electronic signature laws.

This outline isn't a finished legal document. The right wording depends on your product, bargaining position, audience, industry, and the information you're sharing.

Frequently Asked Questions

Can I Use A Free Startup NDA Template?

Yes, you can use a free template as a starting point, but it may miss demo-specific issues like recordings, screenshots, feedback, sandbox access, and permitted internal sharing. Before using it, make sure the document reflects how your demo actually works.

How Long Should A Demo NDA Last?

It depends on the information. Many businesses use two or three years for general commercial information, but trade secrets should usually stay confidential for as long as they remain trade secrets.

Can I Ask For An NDA After The Demo?

You can, but it's much better to have the NDA signed before the demo. If you've already disclosed sensitive information without restrictions, it can be harder to control how the recipient uses it later.

What If Someone Shares My Demo Without Permission?

First, save the evidence, including emails, screenshots, access logs, recordings, and public posts. Then check what the NDA says about notice, deletion, and remedies, and get tailored help if the leak could affect your customers, IP, fundraising, or launch plans.

Key Takeaways

• An NDA for a product demo helps protect unreleased technology, product plans, pricing, roadmap details, and other sensitive business information.
• Your NDA should clearly limit the recipient's use of your information to evaluating the demo or proposed deal.
• Demo-specific clauses should cover screenshots, recordings, access credentials, sandbox data, and feedback.
• Customers, investors, partners, and enterprise buyers may need different confidentiality terms.
• Federal laws like the Defend Trade Secrets Act, the Copyright Act, and the E-SIGN Act may be relevant, but state contract law can still affect the result.
• Templates can be useful, but the safest NDA is one tailored to your product, demo process, and audience.

If you'd like help with your product demo confidentiality agreements, customer and investor NDAs, or demo terms for unreleased software, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.