>> law, technology, and the space between

All content by Kyle E. Mitchell, who is not your lawyer.

You can subscribe via RSS/Atom or e-mail and browse other blogs.

Standardize Commercial Software Licensingannouncing PolyForm Commercial, with a call for help

This post is part of a series, PolyForm.

At you can answer a series of questions, click a button, and download a ZIP archive with readable legal terms and an order template for a commercial software license. Trial, unlimited, or seat-based, binary or source, single version or with updates, full, enterprise-class support or none whatever—the generator supports them all. Answer the questions, download the files, fill out the order form, read it through, and go.

Lawyers have been papering software deals for decades. There is no such thing as one “standard” end-user license agreement to rule them all. But most business-to-business EULAs say mostly the same thing, with a limited number of well understood variations and add-ons. We share enough collective experience to know that a small number of choices cover the vast majority of deals. The decision tree isn’t any deep industry secret. We can write it out, automate it, and put it online.

There are only two questions in my mind:

  1. Can we kickstart a collaboration, so the terms benefit from the knowledge and experience of more developers, businesspeople, and lawyers?

  2. Can we use technology to standardize not just a fixed set of terms, not just a starting point for lawyers to finish, but a decision tree and a template for ready-to-use license packets?

The software, decision tree, and both templates for PolyForm Commercial are all on GitHub. Everyone’s welcome to e-mail me, too. If you care about commercial software licensing and want to waste less time on terms for it, run through the wizard, download a packet, look it over, have your lawyer look it over, and send thoughts my way.

Standardization is trickier. We have strong examples of standard terms without dynamic variation. Open source software licenses, for one. The other licenses from PolyForm, for another. And also outside software: Waypoint for two-way NDAs, and now Guestbook for one-way, as well. Plus several more released in the past year. But these projects aren’t so much decision trees as branded sets of terms to use once a decision—“we should sign a two-day NDA first”, “our site won’t track any personal information”—has been made.

We also see examples of standardized “starting points” for more complex transactions. The ISDA Master Agreement for swaps between companies. The NVCA model docs for venture capital financings. Dueling forms for construction projects and trucking logistics. A build-a-contract toolkit for design work. All of these provide prebaked legal terms, but require a lawyer or savvy businessperson to choose from alternatives, fill in blanks, and otherwise turn a starting point into a finished proposal.

Some industry groups publishing standard forms have tried to automate preparation of variations, often by splitting their monolithic forms into plug-and-play “addenda” and proprietary document assembly software. Even so, the output of that automation is often still an unfinished product, an input to the lawyers, rather than a ready-to-use set of docs.

The advantage of software here is clear: software people get software automation. And as automation goes, selectively concatenating strings isn’t terribly mind-bending. The tricky complexity in PolyForm Commercial isn’t in parsing and following templating instructions—that’s a solved problem—but in making sure all possible variations from a template make cohesive sense, as a set of legal terms. That’s advanced contract drafting, a really fulfilling challenge.

I think we’re up to it. And I’ve taken a first stab, with encouragement, input, and reference material from colleagues. With a few more eyeballs—legal and technical—we could massively reduce transaction costs in the market for software. We could bring the costs of selling software down toward the costs of distributing it: zero.

Your thoughts and feedback are always welcome by e-mail.

back to topedit on GitHubrevision history