713 karma · joined August 22, 2008
Some of our agreements, like the NDA, are already used in other industries since they are more industry agnostic
All of our standard agreements are released under the Creative Commons CC BY 4.0 license. More details on that license here: https://creativecommons.org/licenses/by/4.0/
https://helloprenup.com/ https://hellodivorce.com/ https://www.getdynasty.com/ https://trustandwill.com/
I haven't personally used those services, but the founders are great
Our docs are free, released under creative comments, have been downloaded more than 17,000 times and used to close millions of dollars worth of deals.
If you’re not sure what kind of contract you need, this blog post might help:
There's an exhibit about the ancient city of Tenochtitlan, how it was built on top of a lake, the wild history of things that happened there, etc. It was only when I was almost done with the exhibit I realized [edit] Tenochtitlan is Mexico City, the place I had been for the past few days. It was hard to reconcile.
My main takeaway about the Aztecs from history class was that they were the victims of the Spanish conquistadores. That's true, but they have a fascinating backstory where they were the conquerors of other groups and did a variety of amazing and terrible things. I had a one-dimensional view of the region, and I had never even heard of some of the people that they had conquered.
For internal legal teams, the biggest motivator is often re-allocating their time to more strategic and/or more interesting work. They have a long list of other projects that they'd rather focus on if they can reduce their time spent on yet another NDA or routine sales contract.
While there are important differences in our approaches and focus areas, I'm a fan of more adoption of standards in general and there's a lot that we agree on.
Some companies choose Common Paper over Bonterms because we offer agreement types that they don't, including a Design Partner Agreement and Partnership Agreement. As far as I know, they only provide agreement templates and not software to manage them.
As you mentioned, there are some other efforts to create standards like oneNDA. We're sort of competitive with them, in a similar way that the Apache license is competitive with the GPL.
While there are important differences in our approaches and focus areas, I'm a fan of more adoption of standards in general and there's a lot that we agree on.
Some companies choose Common Paper over oneNDA because we offer agreement types that they don't, including a Cloud Service Agreement, Design Partner Agreement, and Professional Services Agreement. As far as I know, they only provide agreement templates and not software to manage them.
The short answer is that a subset of our team has the ability to access a user's contracts in order to provide support, fix bugs, and improve the product. We log instances when that access is used.
You're absolutely right that there are important differences between the attorney-client relationship versus the relationship with us or any other software provider. If that's not something you're comfortable with, then using the standard contracts without the software will probably be a better option.
The Cloud Service Agreement allows for a product with both on-prem and cloud-hosted components, so it might be a fit if you have a web-based control plane, for instance. However, if your product is purely on-prem, then the CSA is probably not the right fit.
While we don't offer uptime guarantees to users on our free tier, SLAs are an option for paying customers.
All of our users, free and paid, can download all of their contracts and the associated structured data from our system at any time if they'd like a backup. Our API also makes it possible to do this continuously.
Our goal for our product is to help with the entire lifecycle of the customer. From entering into the initial agreement, to getting paid, to keeping track of your obligations across customers, to upselling and renewing, to answering diligence questions when you're raising money or getting acquired.
They handle the steps of making sure it's a compliant, legally valid signature, which is great.
However, a lot of the ceremony as you called it is not required to make it a legally binding signature, it's mostly to make people feel like it's legit.
We may take this in-house at some point to streamline it, but Dropbox has been a good partner to us, and I'm grateful that they enabled us to get up and running quickly.