bookmark_border

Legal Technology with Justin Kan

Software Engineering Daily,

Originally posted on Software Engineering Daily

Imagine that you are a lawyer.

Your work involves managing files with dense, technical text. Your co-workers collaborate with you to accomplish a complex goal that can be broken down into smaller pieces. Your work has formal specifications, but there are degrees of freedom in how you express an idea. In all of these ways, the job of a lawyer is similar to the job of a software engineer–so why don’t lawyers use tools to improve their workflow?

As a software engineer, you have project management tools like Asana that improve collaboration. You have APIs like Stripe that reduce the time spent on a complicated implementation. You have tools like linters and source control that prevent you from making fatal errors. All of these tools save you time.

At many law firms, lawyers do not have incentive to save time. They are paid based on billable hours, not individual milestones. Historically, this hourly billing made sense–lawyers have been around since long before computers. The amount of work that might go into a legal task was hard to predict before you had computers to log data, sort documents, and standardize communications.

In contrast, a software engineer has always had the ability to automate work. That’s why (in most cases) we are not rewarded based on our time spent solving a task. We are paid based on hitting our KPIs and our milestones. With the legacy of hourly billing, lawyers can look at repetitive, administrative tasks as opportunities to make more money.

Justin Kan has been building startups for a decade, and in that time he has interacted with lots of lawyers. From incorporation to fundraising to selling his company Twitch, the interactions with lawyers consistently seemed less transparent and less efficient than would be optimal.

For an engineer like Justin, the natural inclination here was to build software and sell it to lawyers. But there would be so much resistance–you would have to convince the lawyers to change their pricing model to fixed-pricing, which would give them the incentive to buy software and work more efficiently.

Instead, Justin teamed up with a few entrepreneurial lawyers who were willing to start a new law firm from scratch, and use software on day 1. The software company is called Atrium Legal Technology Services (or Atrium LTS for short), and the law firm that uses the software is Atrium LLP. Both of these companies are very new, and were publicly announced a few months ago.

The two companies work side-by-side in undecorated office in downtown San Francisco. When I took the elevator up to see the company, the elevator doors opened and revealed two paper signs pointing to opposite ends of the office. On the Atrium LTS side of the office, engineers were writing software to extract the meaning from documents.

Today, lawyers at old law firms are paid hundreds of dollars an hour to fill in document templates by editing a text document. As the Atrium LTS software gets better, document preparation will be done through web applications, with the variable names disambiguated from the parts of the document that never change from client to client.

On the other side of the office sat Atrium LLP. The legal team was dressed a little more formally than their engineer counterparts, but there was nothing close to the formality of a traditional Silicon Valley law firm. Far from the decor of a Menlo Park law firm, the office space was actually more spartan than most well-funded startups, signaling to the employees that this is an unproven business strategy, and there is a ton of work to be done to validate it.

This sentiment was echoed in my conversation with Justin. It’s possible (even plausible) that Atrium LLP could become the biggest law firm in the world, but the road to getting there will take patience and steady execution. I enjoyed hearing Justin explain the motivation for starting Atrium LTS, and look forward to covering the company in the future.

We have done several other shows about the intersection of software engineering and law, including our show dissecting software antitrust with law professor Harry First.  To find our old episodes, you can download the free Software Engineering Daily app for iOS and for Android. In other podcast players, you can only access the most recent 100 episodes.

With these apps, we are building a new way to consume content about software engineering. They are open-sourced at github.com/softwareengineeringdaily. If you are looking for an open source project to get involved with, we would love to get your help.

Shout out to today’s featured contributor Craig Holliday. Craig has worked on the Software Engineering Daily iOS app to iron out performance issues and implement features like 2x playback. Big thanks to Craig.

Transcript

Transcript provided by We Edit Podcasts. Software Engineering Daily listeners can go to weeditpodcasts.com/sed to get 20% off the first two months of audio editing and transcription services. Thanks to We Edit Podcasts for partnering with SE Daily. Please click here to view this show’s transcript.

Sponsors


The octopus: a sea creature known for its intelligence and flexibility. Octopus Deploy: a friendly deployment automation tool for deploying applications like .NET apps, Java apps and more. Ask any developer and they’ll tell you it’s never fun pushing code at 5pm on a Friday then crossing your fingers hoping for the best. That’s where Octopus Deploy comes into the picture. Octopus Deploy is a friendly deployment automation tool, taking over where your build/CI server ends. Use Octopus to promote releases on-prem or to the cloud. Octopus integrates with your existing build pipeline–TFS and VSTS, Bamboo, TeamCity, and Jenkins. It integrates with AWS, Azure, and on-prem environments. Reliably and repeatedly deploy your .NET and Java apps and more. If you can package it, Octopus can deploy it! It’s quick and easy to install. Go to Octopus.com to trial Octopus free for 45 days. That’s Octopus.com


Auth0 makes authentication easy.  As a developer, you love building things that are fun–and authentication is not fun. Authentication is a pain. It can take hours to implement, and even once you have authentication, you have to keep all your authentication code up to date! Auth0 is the easiest and fastest way to implement real world authentication and authorization architectures into your apps and APIs. Allow your users to log in however you want–regular username and password, Facebook, Twitter, enterprise identity providers like AD and Office 365–or let them login without passwords, using an email login like Slack or phone login like WhatsApp. Getting started is easy. Just grab the Auth0 SDK for any platform you need and add a few lines of code to your project–whether you are building a mobile app, a website, or an API–they all need authentication. Sign up for Auth0 and get the free plan or try the enterprise plan for 21 days at auth0.io/sedaily. No credit card required. Auth0 is trusted by developers at Atlassian, Mozilla, and Wall Street Journal. Try it out at auth0.io/sedaily. Stop struggling with authentication–get back to building core features, with Auth0. 


Incapsula can protect your API servers and microservices from responding to unwanted requests. To try Incapsula for yourself, go to incapsula.com/2017podcasts and get a free enterprise trial of Incapsula. Incapsula’s API gives you control over the security and performance of your application–whether you have a complex microservices architecture or a WordPress site, like Software Engineering Daily. Incapsula has a global network of over 30 data centers that optimize routing and cache your content. The same network of data centers that are filtering your content for attackers are operating as a CDN, and speeding up your application. To try Incapsula today, go to incapsula.com/2017podcasts and check it out. Thanks again, Incapsula.


About the Podcast