You've had the idea. It keeps you up at night, and you're sure nobody else has thought of it. So before you tell a potential co-founder, an advisor or even a friend, you reach for the obvious protection: a non-disclosure agreement. It feels responsible. It feels like what serious founders do.

But ask an experienced investor to sign one and you'll often get a polite no. That's not because they plan to steal your idea. It's because guarding an early idea usually costs more than it protects. Let's look at why ideas are rarely stolen, what openness gives you, and the few cases where caution genuinely earns its place.

Ideas Are Cheap

Here's an uncomfortable truth: if your idea is any good, someone else has probably had a version of it already. Google wasn't the first search engine. Facebook wasn't the first social network. What set them apart wasn't the original spark. It was thousands of decisions made afterwards about what to build, what to cut, who to hire and when to change direction.

An idea is a hypothesis, not an asset. Its value only appears once you test it against real customers and learn what they'll actually pay for. Along the way, the idea almost always changes. Many successful companies end up selling something quite different from what their founders first pitched. When you protect the version in your head, you're protecting something that probably won't survive contact with the market anyway.

And consider the people you'd be telling. Investors already have dozens of ideas in front of them. Engineers have jobs. Friends have lives. To take your idea and run with it, they'd have to quit what they're doing and chase someone else's vision without your insight, your context or your motivation. Almost nobody wants to do that. The real risk isn't theft. It's indifference.

Takeaway

An idea is worth roughly what it costs to have one. The value comes from execution, the insight you gain along the way, and the persistence to keep going when the original plan breaks.

Openness Accelerates Learning

Steve Blank's core advice to founders is simple: get out of the building. Your assumptions about customers are guesses until real people confirm or contradict them. Every conversation about your idea is a chance to find out which of your guesses are wrong, before you spend months building on them.

Secrecy shuts that loop down. If every conversation requires a signature first, you'll have fewer conversations, and the ones you do have will feel formal and guarded. Openness works the other way. Describe the problem you're solving to anyone who'll listen and patterns emerge quickly. Someone points out a competitor you missed. Someone else says they have that exact problem and asks if they can try your solution. A third person knows the perfect advisor and offers an introduction.

These are the raw materials of an early startup: feedback, early customers, collaborators and connections. None of them arrive while your idea sits in a locked drawer. A practical habit is to keep a short description of your problem and proposed solution ready, then share it freely and track what you hear. Treat each conversation as an experiment, and let the responses shape your next step.

Takeaway

Every conversation you avoid to protect your idea is a lesson you don't get to learn. Early on, how fast you learn is your biggest competitive advantage.

When Discretion Makes Sense

None of this means caution is never warranted. In a few narrow cases, some discretion is sensible. Say you've developed a specific technical method, such as a novel manufacturing process, a proprietary algorithm or a chemical formulation. Those details may be genuinely valuable, especially if you're considering a patent. In many jurisdictions, disclosing an invention publicly before you file can affect your ability to patent it, so it's worth speaking to a qualified advisor first.

Regulated industries such as healthcare, finance or defence can also carry confidentiality obligations, particularly where patient data, security details or partner agreements are involved. And when you're deep in negotiations with a specific partner who'll see your internal data, a targeted agreement can make sense. Notice the pattern. These situations involve concrete, specific information, not a broad concept.

The useful skill here is separating the problem from the details. You can talk openly about the pain you're solving, who experiences it and why existing options fall short. That's what generates feedback. You keep the how to yourself: the exact technique, the source code, the specific data. Share the what and the why; protect the how. Most people only need the first part to help you.

Takeaway

Before reaching for secrecy, ask exactly what would cause harm if it were shared. Usually it's a narrow detail you can hold back while discussing everything else openly.

This week, try an experiment. Write a two-sentence description of the problem you're solving and who has it. Then share it with five people outside your usual circle. Potential customers, people in the industry and anyone likely to have an opinion are all good choices.

Note what surprises you, who offers help and which assumptions start to wobble. If something truly sensitive exists, identify it and hold back just that part. You'll likely find that openness gives you far more than secrecy ever protected.