I always thought a good way to go would be to build a standard set of "debugged" contracts, that can be filled out "mad libs" style. The terms of service on al

I always thought a good way to go would be to build a standard set of "debugged" contracts, that can be filled out "mad libs" style. The terms of service on almost every app could be 90% built from a short list of common components, mosttypical employment contracts are pretty much identical. When one of those contracts hits the court, almost all the technical details have been thoroughly discussed, leaving loads of precedent to stand on. The consumers know there's no surprises in it, and the businesses know they're going to have a quick and predictable time if there's a dispute. Eventually, people would start to look at you very suspiciously if you didn't want to use a standard contract-- what scam are you trying to work on? The concept of "let's let anyone write arbitrary contracts and sort it out later" feels strangely 19th-century-quaint today. It relies on nicities of a different era: The two parties probably had reasonably equal access to legal support and knowledge, the negotiations were being done in good faith rather than as a land grab for maximum indemnity/payout, there was a full opportunity to negotiate instead of take-it-or-leave-it clickthroughs.