Welcome to Ironclad!

Powering the world's contracts with products legal teams love

How to Think About Legal AI

Two years ago, Deloitte predicted that artificial intelligence (AI) would automate about ⅓ of the jobs in the legal sector in the next twenty years. ...

How to achieve broad adoption of your contract management platform

Software implementation is difficult. The list of things that could go wrong is practically endless, and includes things like office politics, technical debt, and lack of software support. But the biggest and most common hurdle is product adoption....

Introducing Blueprint with Lucy Li, Product Lead

Lucy Li is a Product Lead at Ironclad. A Carnegie Mellon-educated engineer, she led the front-end mobile web development of Salesforce's early tablet and phone product before joining Ironclad in 2015. She was the creative force behind many of Ironclad's core features, like red-line previewing and complex approvals. Most recently, she lead development of our most recent major product release, called Blueprint....

Balance Visibility and Control with Granular Access Permissions

At Ironclad, we’ve been thinking hard about how to give Legal control over their contracts without sacrificing visibility to the rest of the organization. On the one hand, Legal needs to make sure sensitive information stays within Legal. On the other, contracting requires cross-functional collaboration from business counterparts who need access to contracts information to accomplish their goals....

How Costly Are Manual Contracting Processes...Really?

There’s a light bulb moment that we’ve seen over and over at our customers--it’s when companies realize just how much money they’ve been spending on processing contracts, and why that matters. The average company spends almost $7,000 processing a low-risk contract, according to the International Association for Contract & Commercial Management (IACCM). Think about that. If your company signs a $100,000 contract, 7% of the contract value is out the window before contract fulfillment begins....

Why data is critical to your legal operations strategy

In Mad Men, Don Draper is the creative mastermind behind one of Manhattan’s elite advertising firms. His approach is nothing short of magic: clients go to him with problems, he takes a few swigs of whiskey, and out comes a brand new concept, sure to make his client millions. He’s not informed by numbers or market research or last quarter’s sales data--but this was the ‘60s, a time when it was perfectly acceptable to take a suave man at his word....

3 Ways To Get More Done For Less

  Modern legal teams are increasingly overstretched. Faced with too much work, legal departments have traditionally hired more lawyers or sought outside counsel. But what happens when spending more money isn’t an option? In a recent survey, over 50% of GCs reported that their legal departments’ budget and staffing had remained unchanged over the previous year, even as their workload and responsibilities had increased....

2 Risks Introduced By Manual Contracting Processes—And How To Eliminate Them

Minimizing risk exposure is a—if not the fundamental duty of legal departments. No other department in an organization is capable of fully understanding and then building risk-mitigating processes, and so no other department is charged with this business-critical responsibility ....

6 Must-Know Technical Concepts for the Modern Legal Professional

Even a decade ago, “legal” and “technology” were words that were generally juxtaposed oxymoronically, if at all. Today, “legal technology” is a booming industry: in the last 2 years alone, 222 legal tech companies were funded to the tune of $457 million....

Towards a better service development story: How Ironclad moved from monolith to microservices without sacrificing developer experience

Ironclad began as a monolithic Node application deployed on Heroku. For a small team without much time to devote to DevOps, Heroku was a great solution and made it very easy to automatically build and deploy from GitHub. As our team and application grew, we began to want to split portions of our application into separate services. We decided it was time to move off of Heroku, with the hope that we could keep the ease of development and deployment largely intact....