I’ve lost count of how many times I’ve sat across from a passionate founder—whether in a Lagos coffee shop or on a Zoom call spanning continents—and watched a familiar ritual unfold. Before the real conversation can begin, before the problem they want to solve is even articulated, a document slides across the table: the Non-Disclosure Agreement (NDA).
“I have this idea,” they say, lowering their voice. “But I need you to sign this before I can share it.”
I almost always decline.
I don’t do this out of arrogance, and it certainly isn’t because I have any desire to steal their concept. I decline because, over my years of building products and leading ParallelScore, I’ve realized this ritual is built on a fundamental misunderstanding of how value is created in modern software development. It relies on the philosophical fallacy that an idea, in its infancy, is a fragile treasure that must be hoarded.
In reality, an idea is just a hypothesis. And in the early days of building a product, secrecy is not a moat; it is a liability.
The Myth of the Idea Moat
I understand where founders are coming from. The compulsion to use an NDA stems from the belief that the “secret concept” is their ultimate competitive advantage. But history, and the graveyard of failed startups I’ve witnessed, tell a different story.
Ideas are remarkably cheap and highly abundant. At any given moment, a dozen teams around the world are likely having your exact same “revolutionary” thought. What separates the one that succeeds from the eleven that fail is rarely the secrecy of the premise. It is the execution.
When a founder demands an NDA to protect an early-stage concept, they are protecting the wrong thing. They are aggressively guarding the 1% inspiration while completely ignoring the 99% perspiration required to make it real. A raw idea is not a moat; it is merely a puddle. It evaporates the moment it meets the heat of the real market.
The True Moats of Modern Business
If the idea isn’t the moat, what is?
Through our work at ParallelScore, designing human-centric solutions across healthcare, civic tech, and logistics, I have learned that actual moats are built through motion, not stasis. True competitive advantages cannot be summarized in a legal document or stolen over a cup of coffee. They include:
- Deep User Empathy: You cannot steal an intimate understanding of a user’s pain points. A competitor might copy a feature list, but if they haven’t sat through the product design workshops, the user journey mapping, and the raw usability testing, their clone will lack the soul and nuance that retains users.
- Velocity and Agility: The ability to learn faster than anyone else is the ultimate advantage. A team executing in tight, two-week sprints, integrating continuous feedback, and pivoting without ego will always outpace a team hiding behind closed doors trying to build a “perfect” v1.0.
- Team Cohesion and Trust: The alchemy of a dedicated, small team working alongside a visionary client is incredibly difficult to replicate. At ParallelScore, we view ourselves as partners, not vendors. You cannot reverse-engineer the trust that allows a team to scrap a bad feature and pivot on a dime.
I constantly remind founders of this simple truth: The moats worth protecting protect themselves. You cannot steal lived experience. You cannot sign a contract to suddenly acquire a team’s hard-won synergy or their intimate understanding of a customer’s workflow. If someone can hear your idea in a 30-minute meeting and successfully beat you to market, the idea was never your moat to begin with. You lost on execution.
The Cost of Friction
Beyond the philosophical disconnect, I reject early-stage NDAs because they introduce immediate, tangible friction.
Innovation thrives on cross-pollination. It requires open dialogue, the rapid bouncing of ideas, and the freedom to say, “What if we looked at this healthcare problem through the lens of a logistics platform?” NDAs stifle this. They introduce legal paranoia into what should be a creative, uninhibited product discovery phase.
Furthermore, an NDA establishes a relationship based on mutual distrust before a single line of code is written. Great software is built on transparency. Starting a relationship with the threat of litigation is entirely counterproductive to the collaborative spirit required to build something truly impactful.
The Pragmatist’s View: When You Actually Need an NDA
I am not naive, and I don’t operate in a utopia where legal protection doesn’t matter. NDAs absolutely have a place in business, but their utility is found later in the lifecycle, protecting actual assets rather than abstract thoughts.
Here is the framework I use when advising founders on where to draw the line:
When You DON’T Need an NDA:
- Pitching a high-level concept: If you are explaining what your app does (e.g., “It’s Uber for dog walking”), you don’t need an NDA.
- Sharing a pitch deck or business plan: Investors and development studios see hundreds of these a month. An NDA here just makes you look inexperienced.
- Discussing user pain points: Talking about the market problem you want to solve should be broadcasted loudly to anyone who will listen.
When You DO Need an NDA:
- Sharing access to sensitive user data: When my team built MyCareAI, dealing with FHIR compliance and sensitive health information (PII/PHI) for companies like NewWave and Onyx, strict security protocols and NDAs were paramount. You must protect your users.
- Exposing proprietary algorithms or source code: If you have spent two years developing a highly novel, patent-pending AI model or a complex data transposition script, an NDA is appropriate before opening the repository.
- Entering formal Due Diligence: If you are sharing unreleased financial records, user acquisition costs, or M&A details, legal protection is standard and necessary.
NDAs are designed to protect data—proprietary code, patient records, internal financial structures, and established trade secrets. They exist to protect the realities of your users and the tangible assets of your business. They were never meant to protect a daydream.
Solve Local, Build Global (With Open Hands)
I built ParallelScore on a very specific ethos: “Solve Local, Build Global.” You cannot solve real human problems by hiding from the humans who can help you build the solution.
The greatest founders I have had the privilege of working with don’t fear their ideas being stolen; they fear their ideas remaining untested. They understand that by sharing their vision openly, they attract the right talent, the right feedback, and the right partners to execute it.
So, keep your ideas open. Build your moats through relentless user-centered design, rapid development, and unyielding empathy. When you focus entirely on execution, you’ll find you never needed the NDA in the first place.