Thank you! My number one priority right now is getting more companies to sign up as users on the website. Even small, unheard of companies can make a huge dif

Thank you! My number one priority right now is getting more companies to sign up as users on the website. Even small, unheard of companies can make a huge difference at this stage! I'm not sure quite what you mean by "design patterns". The NDA form itself is very orthodox in its language. I wrote it, intentionally, to be as little-surprising and easy to review, knee-jerk, as possible. In other work, I'm fanatical about plain language, clean structure, and the reuse of components of language. The latter comes through in my open source project, Common Form, which essentially ports various software development tools---editor, linter, compiler, package manager---to contract drafting: https://commonform.github.io/ https://commonform.github.io/ I've also released some "open" forms in my preferred style: https://forms.kemitchell.com/ https://forms.kemitchell.com/ For example, here's my form contract for developers doing a mix of open and closed projects for clients: https://commonform.org/switchmode/switchmode/2e1u https://commonform.org/switchmode/switchmode/2e1u Or perhaps you mean "design patterns" more to do with the "viral" nature of the Canting Tribe NDA, a kind of voluntary, Internet-enabled standardization. I do have high hopes for that model. I'd love to see it work for NDAs, and reuse it for other kinds of transactions, including some with more inevitable terms variability. SaaS agreements, for example.