This business couldn’t scale as long as its knowledge couldn’t scale with it
How a lean legal team turned decades of customer history into a searchable contract system.
👋 Hey there, I’m Hadassah. Each month, I unpack how in-house legal teams use AI to enable the business, protect against risk, and free up time for the work they enjoy most—what works, what doesn’t, and the quick wins that make all the difference.
Before we dive in, a quick note: this is just one example of a legal team solving an operational bottleneck. There are plenty of ways to approach these kinds of problems, and the right solution will always depend on your specific needs and context. My goal is to give you some food for thought as you define what that solution should be.
Problem
When this Head of Legal stepped into their role at a new company, they inherited a challenge familiar to many long-standing businesses: how to scale without structure.
After forty years in operation—much of it driven by renewals and upsells—the company had accumulated a vast but disorganised record of customer history. Information was scattered across local drives and reliant on institutional memory. A major leadership transition only widened the cracks. Without the people who “remembered how things were done,” even basic questions about a customer’s past became difficult to answer.
Then the pandemic accelerated change. Workflows were digitised almost overnight—but digitisation alone didn’t address the deeper issue. Information still wasn’t accessible or reliable.
Commercial teams lacked a clear view of what customers owned or when contracts expired. Finance couldn’t rely on CRM data from an outdated, on-premise system. Legal, meanwhile, became the default archive for everything.
Routine tasks—generating a first draft, checking a renewal date, confirming a license count—stretched from hours into days. The challenge was compounded by 12–13 hour time differences between contract administrators and customers.
The company wanted to grow without adding headcount. But the legal team quickly recognised the underlying problem: the business couldn’t scale if its knowledge couldn’t scale with it.
Solution
The legal team needed a solution that could accomplish two things at once.
First, it had to restore reliable access to decades of customer history. Second, it needed to streamline—and partially self-serve—the contract process so the business could grow without adding headcount.
Any tool they selected had to support a single, searchable repository. It also needed a workflow engine that would allow the business to quickly generate first drafts on its own.
They set a clear rule from day one: start small, deliver value quickly, and build only what the business could realistically absorb.
To do that, they narrowed the initial rollout to two high-volume templates and a single workflow with basic approval logic—the minimum viable system capable of proving what digitisation could achieve.
For the repository, Legal and IT defined straightforward criteria. They would upload contracts for all active customers, along with the past five years of documents—seven years for key accounts. Thanks to relatively strong naming hygiene, IT was able to script the extraction and flatten folder structures. Legal then uploaded files in nightly batches of about 100 documents using a simple drag-and-drop process. Keeping the work in-house preserved ownership and avoided costly outsourcing.
The team selected Ironclad as the backbone of the solution. Ironclad stood out not only for its functionality, but for its hands-on support—well aligned with the team’s level of maturity.
The vendor customised demos for the sales team, provided a generous implementation package, and trained Legal to configure workflows independently. The company didn’t just need software; it needed a partner willing to roll up its sleeves.
Ironclad delivered, and the system went live in roughly two months.
Results
The company established a centralised, fully searchable repository containing nearly 7,000 contract artefacts—replacing decades of scattered files stored across local drives.
Contract turnaround times for international customers improved dramatically. Work that had previously taken the better part of a week—largely due to 12–13 hour time-zone gaps—could now move forward in a fraction of the time.
Commercial teams gained self-service access to generate first drafts. They no longer had to wait several days for contract administrators to make even basic placeholder updates.
Legal also reduced its reliance on institutional memory. In its place, the team built a scalable digital foundation capable of supporting business growth—without increasing headcount.
Process
The rebuild began with alignment.
Legal, Sales, Finance, and IT agreed on a shared definition of success: equal access to customer history, faster contract cycles, and business growth without adding personnel. With that clarity in place, the Head of Legal approached the initiative like a classic enterprise software rollout—prioritising small, controlled deliverables that could demonstrate value early.
Legal led the build themselves. They designed workflows, tagged templates, and uploaded documents in short, focused iterations. This hands-on ownership kept costs down and built deep internal familiarity with the system, while Ironclad provided targeted support where needed.
Not everything went smoothly.
At one point, Ironclad’s OCR began misidentifying parties due to subtle template changes. Legal had to diagnose the issue and manually correct hundreds of records—a reminder that automation can accelerate work, but it doesn’t eliminate the need for oversight.
After go-live, a different challenge emerged: adoption. The sales team, already fatigued from a simultaneous Salesforce rollout, resisted logging into yet another system.
Tensions rose further when Ironclad introduced its Salesforce connector as a costly add-on—well beyond the project’s budget.
Rather than stall, IT built a custom connector. The solution allowed Sales to trigger Ironclad workflows directly within Salesforce, eliminating the need for a new login or learning curve.
That pivot changed everything. Adoption improved quickly, and Legal was repositioned as an enabler rather than an obstacle.
By keeping the MVP lean, iterating transparently, and designing around end-user behaviour—not just legal requirements—the team built a contract engine that reflects how the business actually operates.
Quick Wins
None of this success started or stopped with the purchase of a shiny new tech tool. It lived in the messy middle: the early decisions, cross-functional alignment, and workarounds that determine whether a new workflow eventually sticks. Getting something new off the ground is rarely about one big moment of success. More often, it’s about the small, practical wins that build momentum and keep a project moving forward.
For this legal team, those wins looked like:
A lean MVP accelerated the rollout. By limiting the initial launch to just two templates and basic routing logic, the team delivered a functioning workflow in under two months. The narrow scope kept executive sponsors engaged and ensured expectations stayed realistic.
The repository was scoped to what mattered most. Importing five years of contract history—and seven for key accounts—struck the right balance between completeness and practicality. The team avoided months of unnecessary cleanup while still restoring meaningful visibility into customer relationships.
Users were met where they already worked. Embedding the contract workflow directly into Salesforce removed both the psychological and operational friction of adopting a new platform. Instead of becoming a training challenge, adoption became a non-issue.
Implementation was legal-led. By configuring workflows and uploading documents themselves, the legal team built deep internal expertise and a strong sense of ownership. That foundation sustained the system long after go-live.
Now it’s your turn. If your team is dealing with something similar, I hope this story sparks a few practical ideas you can put to work.
And… if you’ve been through something similar—or solved a different operational challenge altogether—I’d love to hear your story and spotlight your win.