Being An Indie Software Developer And Signing NDAs

Very frequently, I receive emails that go something like this:

“Hey Brandon, I have a killer project idea. Do you want to work on it? Please sign the NDA so we can talk.”

Early on when I first started consulting, I would have responded with something like “Sure send it over!” and signed the thing without hesitation. As of late, I have changed my view on NDAs; at least in this type of situation.

For those that don’t know, an NDA (non disclosure agreement) is a contract that is intended to protect the intellectual property of the client. They make a lot of sense, especially in the event that the deal goes sour. Say a client has some great idea for how to better take selfies that is going to revolutionize the selfie game. If he doesn’t get a developer to sign an NDA, the developer could potentially be free to discuss the idea with others, leaving the idea open to be stolen.

Why I Don’t Sign Preliminary NDAs

In the scenario I mentioned above, it would be very unwise of me to sign this NDA as I don’t have enough information about the product. This puts me as a consultant at a huge risk.

Say for example I am working on a photo/video sharing app (I get roughly 1 request a week for some spin on Instagram). Now, say the incoming project is some variant on photo sharing. If I sign the NDA, it now now puts me in a conflict of interest with my existing project.

Even if I knew that the project was a photo/video sharing application up front, I still would not sign the NDA. Much of the time (as mentioned above) clients want very similar applications. If I went around signing every single NDA that came across our desks, I would be out of business after the first client.

When I Will Sign NDAs

Well, the first thing that I do is ask for clarification on the project and tell them my NDA policy. I basically tell them that I am happy to sign the NDA if one of the following conditions are met:

There is extremely proprietary information (you can’t land a big enterprise contract without first signing an NDA) We are ready for project kickoff and all parties are aware of any potential conflicts

In addition to that, if I am currently working on a project that is of similar type, it would be worthwhile to disclose that information to the potential new client (not the proprietary info, just that there is some overlap) so that they can choose whether or not to proceed. Better to possibly lose the new client than end up in a crazy legal battle.

If the new client refuses to give you any more information, then they are not worth your time. They will most likely be too challenging to work with down the road anyway.

NDAs Are Not Set In Stone

When you do finally decide to sign the NDA, know that it is not complete until you sign it. If you see something that you don’t like or want to add any additional clauses, feel free to propose those to the client. Most clients will be very understanding.

That being said, it’s VERY IMPORTANT that you read all the way through an NDA and possibly run it by your lawyer before signing.

Suggestion If You Want Your NDA Signed

If you want a developer to sign your NDA, make sure to give him enough information about your project for him to make an educated decision. If you just say “I want a photo sharing app” and expect an NDA signed, good luck. Make sure that they know there is proprietary information involved and that you are doing something different that must be kept private.

An NDA is not required if you want to make say an “Instagram Clone For Puppies” or a “Miley Cyrus Flappy Bird Clone”. Be sensitive to the uniqueness of your idea and decide if it really warrants an NDA.

Also note that developers are not out to steal your idea. They get pitched hundreds of ideas and most of the time your idea falls into 3 categories anyway:

It’s not unique There is a technical challenge and that’s why it hasn’t been done (I get pitched a lot of ‘Map a grocery store so that my list will navigate me around’ ideas) Your idea is so niche and so unique that the general audience won’t get it and it won’t be profitable anyway

I’m not saying that every idea falls into these categories. But a good majority do. Most of them fall under #1 and that’s not necessarily a bad thing. Google fell into #1 and look where they are today. Just keep these things in mind when requiring a signed NDAs before you will give out any info.

Conclusion

There has been quite a bit of discussion lately (especially on Hacker News) about whether or not to sign NDAs. Most of the recent articles I have read are simply titled “I Will Not Sign Your NDA”. I feel that NDAs have there place, but you should sign them only with extreme caution. Examine each NDA on a case by case basis and determine how it will affect your business in the long run.

*Disclaimer: I am not a lawyer and do not claim to be giving any real legal advice. I am simply stating how I do things. Make sure to consult with a lawyer before engaging in any contracts.



