How to Protect Your Startup Idea When Pitching

A bare idea cannot be protected by copyright, patent or trade secret law. What you can protect is the way the idea is expressed, an invention that meets patent requirements, and confidential information you keep secret. Investors rarely sign NDAs, so protect yourself by disclosing in stages, keeping your most sensitive details back, and keeping dated records of what you built and shared.

Startup lifecycle A to Z · Letter I · Stage: Idea

By the Revolutionary Startups editors · Reviewed 11 November 2026 · 12 min read · 2,748 words

Can you protect an idea at all?

Short answer: not in the form of a bare idea. "A marketplace for X" or "an app that does Y for Z" cannot be owned. The law protects specific things built on ideas, and the distinction is the single most useful thing a founder can understand before pitching.

Copyright, for example, protects an expression of an idea, such as the code, text, images, music or design that you actually created, but it does not protect the underlying idea, method or concept. Two people can build competing apps for the same problem and neither infringes the other's copyright, as long as neither copies the other's actual code or content. Wysebridge's free copyright guide explains this idea and expression line in more detail.

Understanding that line changes how you pitch. You stop asking "how do I stop anyone hearing my idea?" and start asking "which parts of what I have are protectable, and how do I share them without losing that protection?"

This is general information for U.S. founders, not legal advice. Rules on implied contracts and confidentiality vary by state, so check specifics with a licensed attorney.

What is protectable and what is not

What you have	Protectable?	How	Caveats
A general idea or concept	No	Nothing protects it by itself	Speed, execution and relationships are your real defence
Code, writing, designs, photos, videos	Yes	Copyright, which exists once a work is fixed in a tangible form	Registration is needed before you can sue for infringement of a U.S. work, and gives extra remedies
A new, useful, non-obvious invention	Possibly	Patent, through an application at the USPTO	Public disclosure can start deadlines and may cost rights abroad
Confidential business information with value from secrecy	Yes, while secret	Trade secret law, backed by reasonable secrecy measures	Disclosure without confidentiality can destroy it
Your brand name and logo	Yes	Trademark rights arise from use, and registration strengthens them	Applies to a name used in commerce, not to an idea for a business
A business model or strategy	Mostly no	Generally only through secrecy or contracts	Some methods can be patentable, but not simply because they are a way of doing business

Ideas versus inventions

People use "idea" loosely. In patent law, an invention is a concrete, specific solution to a technical problem, described in enough detail for someone skilled in the field to make and use it. The line between "an idea for a drone that delivers medicine" and "a drone with this particular mechanism, claimed in these specific ways" is exactly the line between unprotectable and potentially patentable. Software ideas have extra hurdles, covered in do I need a patent for my app.

Trade secrets

A trade secret is information that gains value from not being generally known, and that you take reasonable steps to keep secret. Customer lists, formulas, source code and processes can qualify. Wysebridge's free trade secret law guide covers what qualifies and how courts look at "reasonable steps." The catch for pitching: telling someone without any confidentiality arrangement can undermine the claim that you protected it. See trade secrets and NDAs for startups for a fuller treatment, and patent vs trade secret if you are choosing between them.

Why most investors will not sign an NDA

Many founders ask investors to sign a non-disclosure agreement (NDA) before a pitch, and many investors say no. That can feel like a red flag, but it is normal and usually reasonable, for reasons that have little to do with your idea.

Volume. An investor may hear from hundreds of founders. Signing an NDA with each would create a pile of legal obligations to track.
Overlap. Investors often see several companies in the same space. An NDA could, in theory, restrict them from investing in a competitor of yours, or give you grounds for a complaint if they do.
Ideas are not the product. Investors generally say they back teams and traction, not secrets, because an early idea is rarely what decides whether a company works.
Reputation. Reputable investors rely on their reputation for confidentiality. Misusing a founder's information would damage the relationships on which their deal flow depends.

That does not mean confidentiality never matters, or that no investor will ever sign one. Some corporate investors, strategic partners and later-stage investors in due diligence commonly do sign confidentiality terms. Pushing hard for an NDA at a first pitch usually signals inexperience and can slow the conversation.

What to do instead

Do not rely on an NDA for the first meeting. Design the pitch so that nothing in it, if repeated, would sink the company.
Research the investor. Ask other founders about their reputation, and pitch to people with a track record of treating founders fairly.
Ask for confidentiality later and narrowly. When you move to due diligence, request a short, mutual confidentiality agreement covering the specific materials you are sharing. Our guide NDAs for startups: when to sign goes through when they help and when they are a waste of time.

A staged disclosure approach

Staged disclosure means you share more only as the other side earns it. The idea is simple: give each audience enough to make a decision about the next step and no more.

Stage 1: The problem, the market and the team

At a first meeting, cover who you are, the problem, who has it, why now and what you have achieved so far. None of this is secret and none of it is the "recipe". It is also what investors actually decide on.

Stage 2: How it works, at a high level

Once there is real interest, explain the product and your approach in general terms. Show screenshots, a demo or user results. Describe what it does, not how it is built inside.

Stage 3: Specifics under confidentiality

In due diligence, share details such as architecture, unreleased features, unit economics and a data room, under a written confidentiality agreement. By this stage the other party has shown commitment, and you have good reason to ask for terms.

Stage 4: The crown jewels, only if needed

Some things you may never need to share before a deal closes: a secret formula, a model's training data, source code. If an acquirer or investor must see them, limit access, use clean rooms or supervised reviews, and ask counsel to set the terms.

Stage	Who	What you share	Protection
1	Any investor or partner	Problem, market, team, traction	None needed
2	Interested investors	Product overview, demo, high-level approach	Reputation, selective detail
3	Serious parties in diligence	Detailed plans, financials, technical documents	Written confidentiality agreement
4	Final stage parties only	Source code, formulas, sensitive data	Strict access limits, counsel-reviewed terms

What goes in a pitch deck and what stays out

A pitch deck is meant to persuade, not to teach a competitor how to rebuild your company. If you are still working on yours, see how to write a pitch deck for structure. For protection, sort every slide into one of two piles.

Safe to include

The problem, the customer and the size of the market.
Your solution in plain words and a product demo or screenshots.
Traction: users, revenue, pilots, waitlist, as long as these are true and you can back them up.
The team and why you are the right one.
Your business model and the broad shape of your go-to-market plan.
The fact that you have filed, or plan to file, IP, such as "patent pending", if that is accurate.

Keep back or share only later

Source code, detailed architecture and proprietary algorithms.
Exact formulas, recipes, parameters or manufacturing processes.
Customer lists and named contacts, unless the customer agrees.
Details of an invention you have not yet filed a patent application for.
Unreleased roadmaps that a competitor could copy quickly.
Third-party confidential information that you have no right to share.

A useful test: if this slide ended up in a competitor's inbox, would it change what they could build next month? If yes, hold it back or move it to a later stage. If it only shows them that you are good at what you do, it can stay.

Mark the deck, but do not rely on the mark

Adding a footer such as "Confidential" or a copyright notice is a good habit. It signals that you care and can help a later argument that you took reasonable steps. It does not create a binding duty of confidence on its own, so treat it as a courtesy and not a lock.

Keep dated records and file before you disclose

Dated records

If a dispute ever arises about who created what and when, contemporaneous records are your best evidence. Keep:

Version control history for code and design files.
Dated notes, sketches or invention disclosure documents that describe what you created.
A simple log of who you pitched, when, what you shared and whether any confidentiality terms applied.
Copies of what you sent, with the date, for example the exact deck version emailed.
Signed assignment and confidentiality agreements from co-founders and collaborators. See employee and contractor IP agreements and IP assignment agreements for startups.

Records do not create rights by themselves, but they make it far easier to prove your story.

Patent timing at a general level

If you may want a patent, disclosure timing matters. In the U.S., there is generally a one-year grace period after the inventor's own public disclosure within which an application can still be filed, but many other countries have no grace period or a much narrower one, so a public disclosure before filing can end your chance for foreign rights. Pitching in private to one investor is different from presenting on stage, posting online or selling the product, but the exact line depends on facts. The conservative path is to file at least a provisional application before any public disclosure, which provisional patents for startups explains. Wysebridge's free guide to U.S. patent law covers disclosure and novelty rules more fully. For a calendar view of the dates, see your year of IP deadlines.

Pitching is not only investors. You may need to explain your idea to a freelance developer, a design agency, a manufacturer or a potential partner. The risks differ from an investor pitch because these people may build the thing.

Do these things first

Sign a written agreement before work begins. It should say what you are asking them to build, that the work product belongs to you, and that they keep your information confidential.
Get ownership in writing. Without a written transfer, the person who writes the code or creates the design may own the copyright by default, even though you paid. This is one of the most common problems in early-stage startups and is covered in employee and contractor IP agreements.
Share on a need-to-know basis. Give them the pieces required to do the job, not the full roadmap.
Check what they bring with them. An agency may use its own tools, templates or open source code, which can carry their own terms. Open source licenses for startups explains why this matters.

When the other party is a larger business, a different set of issues arises over who owns what you build together. Those are covered in joint development and partnership IP.

How idea submission policies work

Large companies receive unsolicited ideas all the time, from the public, from inventors and sometimes from startups. Many of them publish a policy that says they do not accept unsolicited ideas, or accept them only on stated terms. These policies exist for a simple reason: the company is probably already working on many things and does not want a dispute if a later product resembles what an outsider sent in.

In general, such a policy may say that:

The company does not accept or review unsolicited ideas, and any that arrive may be deleted or returned unread.
If it does accept submissions, the sender must agree to terms first, such as that no confidential relationship exists and no payment is owed unless a separate written agreement is signed.
The company may already be developing similar work and owes nothing for that.
Submitting does not create a contract or any obligation to pay.

Under U.S. law, some states recognise claims based on implied contracts or breach of confidence when someone submits an idea in expectation of payment and the recipient uses it. How such claims work varies by state and depends heavily on the facts, and the terms of a submission policy can limit them. That is why it matters to read a policy before sending anything, and why you should not send an unsolicited idea to a large company without first talking to a lawyer if the stakes are high.

The practical alternative for most startups is to approach a company through a business development contact or a formal partnership program, get a written agreement in place before sharing technical details, and be ready to show what is protectable, such as a patent filing or a prototype, before disclosure.

Where this fits in the startup lifecycle

Protecting your idea while pitching belongs to the Idea stage of the series, and it comes back at Raise and again when you meet partners. Before this, how to validate a startup idea helps you decide whether the idea deserves protection at all. After this, NDAs for startups goes into the agreement most people reach for first, and protecting IP before fundraising covers what investors look at later.

The whole sequence is laid out in the startup lifecycle A to Z. For founders who want to learn how all four main IP types work together, Wysebridge's 20-chapter IP law course is a structured way to do that. For anything specific to your facts, especially disclosure before a patent filing, ask a licensed attorney or registered patent practitioner.

Frequently asked questions

Can you protect a startup idea?

Not a bare idea. Copyright protects your expression of it, such as code, text and designs, but not the concept. Patents can protect a specific invention that meets legal requirements. Trade secret law protects confidential information while you keep it secret. For everything else, your protection is speed, execution and the contracts you sign.

Should I ask investors to sign an NDA before I pitch?

Usually not for a first pitch. Most investors decline because they see many pitches and overlapping companies, and pushing for one can look inexperienced. Design the first pitch so nothing shared would sink you, and request a narrow, mutual confidentiality agreement later, when you share sensitive materials in diligence.

Does copyright protect my business idea?

No. Copyright covers the specific way you express something, such as your code, writing, images or design, and not the underlying idea, method or concept. A competitor can build a similar product for the same problem as long as they do not copy your actual code or content.

What is an unsolicited idea submission policy?

It is a company's stated rule about ideas sent in by people it has no relationship with. Often it says the company does not accept them, or accepts them only on terms that create no confidentiality and no duty to pay. Read it before sending anything, because submitting usually means you agree to it.

How do I share my idea with a developer or agency safely?

Sign a written agreement first that covers confidentiality and states that you own the work product. Without a written transfer, the creator may own the copyright by default. Share only what they need, and check any open source code or tools they bring, since those can carry their own license terms.

Will pitching to investors affect my ability to get a patent?

It can, depending on how public the disclosure is and where you want protection. The U.S. generally gives a grace period after your own public disclosure, but many other countries do not. If you may want a patent, speak to a registered practitioner and consider filing, at least provisionally, before any public disclosure.

Key terms on this page

NDA for Startups: When to Sign and When to Skip GuideNDA for startups explained: clause by clause, when to ask for one, when not to, who to ask, mutual vs one-way, how long it should last, and a decision table.
Pitch Deck Outline: What to Include, Slide by Slide GuideA pitch deck outline for first-time founders: what goes on each slide, how to order them, seed pitch deck tips and the mistakes that sink an investor deck.
IP Due Diligence for Startups Before Fundraising IP guideIP due diligence for startups: what investors ask about IP, a practical checklist, and why founder IP assignment should come before funding.
Trade Secrets for Startups: NDAs and Secrecy Steps IP guideTrade secrets for startups: what qualifies, what reasonable secrecy measures look like, when to use an NDA, and whether investors will sign one.
How to Validate a Startup Idea Before You Build GuideHow to validate a startup idea before you build it: customer interviews, a question bank, landing page tests, and a checklist for deciding whether to go ahead.

Learn more from Wysebridge

Wysebridge owns, operates and sponsors Revolutionary Startups, so these are links to its own free resources and directories. Read the disclosure.

Wysebridge trade secret law guideFree guide to trade secrets: what qualifies, the DTSA and UTSA, NDAs and misappropriation.
Wysebridge copyright law guideFree guide to what copyright protects, registration, fair use, work made for hire and the DMCA.
Wysebridge patent law guideFree guide to U.S. patent law: provisional and non-provisional applications, claims, patentability and USPTO prosecution.

Part of Protecting Your Startup · All guides · Glossary

Sources

General information, not legal, tax or financial advice. Reviewed 11 November 2026.