One of the things I’ve noticed about legal is how much attention a contract gets right up until the moment it’s signed. Weeks of negotiation. Endless redlines. Internal debates over liability caps, service levels, payment terms and risk. Entire meetings dedicated to a single clause. Everyone involved understands exactly how important the contract is while it’s being negotiated.
Then the signatures happen, and suddenly everyone’s attention moves on. The contract gets filed away, opened only when something goes wrong or somebody needs to answer a question months later.
I’ve always found that a bit strange, and maybe it’s because I don’t come from a legal background. One of the advantages of being an outsider is that nobody tells you which parts you’re supposed to accept without questioning. You just keep asking why. Why spend months negotiating an agreement if you’re going to stop paying attention to it the moment it takes effect? Because that’s effectively what happens, more often than anyone would like to admit.
A contract doesn’t become less important because the negotiation is over. That’s when its real job begins. It now contains commitments the business has made, obligations it needs to meet, risks it’s agreed to carry, and commercial positions that might shape negotiations for years to come.
Contracts are organizational knowledge
The more time I’ve spent around legal teams, the more I’ve come around to thinking contracts aren’t really documents at all. They’re organizational knowledge. Every supplier agreement tells you something about how the business buys. Every customer contract tells you something about how it sells. Employment agreements, licences, leases, and partnership agreements all capture decisions, trade-offs, and risk positions that shape how the whole organization operates.
The mistake is thinking about contracts one at a time. Businesses don’t run on a single agreement. They run on thousands of them, all connected. A customer agreement influences the next negotiation. A supplier contract affects procurement decisions. A property lease impacts finance. Collectively they describe how an organization operates. Yet we continue to treat them as isolated files instead of a connected body of knowledge.
Where the knowledge gets lost
The problem is that knowledge has traditionally been stored in places that make it almost impossible to use. A lawyer reviewing a new contract wants to know what position the company took the last time a clause came up. So they start searching. Maybe it’s in a precedent bank. Maybe it’s in SharePoint. Maybe it’s buried in someone’s inbox, hidden inside a file called MSA_v3_final or, worse, MSA_v3_final_ACTUAL. If you’ve never lived that particular horror, count yourself lucky. At some point the search usually ends with a message to a colleague asking if they happen to remember.
We built a lot of features early on at LawVu to help solve these issues. A proper repository. Everything tagged. Any contract findable in two clicks instead of 20 minutes digging through a shared drive. It felt like real progress at the time. Except being able to find a contract quickly doesn’t mean anyone’s actually asking it anything.
We’d built a much nicer filing cabinet, but it was still a filing cabinet. A filing cabinet doesn’t make the knowledge inside it any easier to use. It just stores it more tidily.
Someone wants to know which suppliers have accepted a particular liability position. Procurement needs visibility into obligations coming due. Finance wants to understand what’s committed over the next year. The answer already exists. It’s just trapped inside hundreds or thousands of individual agreements, so somebody starts searching again.
Imagine your procurement team asks a simple question. “How many suppliers have accepted unlimited liability for data breaches?”
The answer exists. It’s sitting somewhere across hundreds of contracts negotiated over years by different lawyers. Traditionally, somebody would spend half a day opening agreements, searching PDFs and trying to piece together an answer.
From searching to asking
That’s a big part of why we built Lens as a connected part of LegalOS rather than another standalone product.
Lens doesn’t really read contracts. It turns agreements into organizational knowledge. Every commercial position, obligation, and negotiated term becomes something you can understand across your entire contract portfolio in seconds, not because AI guessed, but because your contracts are no longer trapped as individual documents.
It’s also why we now have LawVu Draft. To me they solve two halves of the same problem. Draft helps lawyers access organizational knowledge while they’re still negotiating. Instead of leaving Word to hunt for precedent language or an approved position, the context sits right alongside the document. Lens then picks up where Draft leaves off. Once agreements are signed, they don’t disappear into storage. They become connected knowledge that can be understood across every contract in the business, giving legal a view that simply wasn’t possible when every agreement lived as an isolated PDF.
None of this is really about replacing anyone’s judgment, by the way. It’s just that nobody’s memory should be the thing standing between a contract and an answer six months down the line.
The legal teams that get the most value from contracts won’t be the ones with the biggest repository. They’ll be the ones that stop thinking of contracts as documents and start treating them as organizational knowledge.
Because signing the contract shouldn’t be the finish line. It should be the starting line.
This is the third in a seven-part series looking at what sits inside a legal operating system, one capability at a time. Next up: what it takes to finally end the legal spend black box.
