What Co-Flo's Live CLM inside iManage Demo Showed Legal Teams.
Most Contract Lifecycle Management pitches start with the same premise: rip out what you have and move to something new.
Our recent session took a different starting point. If your legal team already runs on iManage, adding a CLM layer closes the distance between signed agreements and daily execution, with no migration project required.
Co-Flo's CEO, Matteo Pagani, walked a live audience through a real-time demo of Co-Flo CLM, built natively on iManage, and the session made a case worth restating for any legal team already invested in the platform.
Why CLM hasn't delivered for legal teams
He opened with a question: why hasn't Contract Lifecycle Management (CLM), as a category, delivered the value it promised? His answer centered on a pattern showing up across the legal departments he has spoken with recently. Contracts get signed, then disconnected from the business activity they're supposed to govern. Post-signature ownership goes unclear. Work only resurfaces when an obligation is missed or a deadline passes.
The numbers he cited back this up. Legal departments report contract revenue erosion in the 9 to 15% range. Roughly six in ten legal teams say they lack visibility into contract status. Close to half report no standardized process for how contracts move through their organization.
The pattern points to missing infrastructure. A document management system already provides that infrastructure, if the contract layer is built to use it.
Contracts sit at the center
He framed contracts as the connective tissue between a legal entity and the four groups it deals with: suppliers, employees, regulators and customers. Every one of those relationships runs through a signed agreement, and the distance between what an agreement says and what the business actually does with it is where cost and risk build up.
His point on information architecture is worth underlining for anyone tracking the shift toward AI in legal operations. Before an AI tool can extract obligations, flag risk or automate a workflow, it needs contract data connected to the business entities it describes. Structure has to come first. IA before AI works as a sequencing argument here, and it's why a CLM layer that plugs into an existing information architecture has an advantage over one that requires building a new one from scratch.
What the demo showed
The live walkthrough followed a single contract, a software reseller addendum, from request to signature, without leaving iManage:
- Structured intake. A business user submits a request through a smart form. Fields default based on business rules, and the request routes to legal automatically, no email chain required.
- Drafting inside the document. Legal opens the generated draft directly in iManage, edits it as they would any Word document and version history tracks every change.
- Two-way status. The requester sees where the contract sits at every stage. Legal sees exactly what's in their queue and what's sitting with the business, so nobody spends time chasing status manually.
- E-signature, without leaving the system. The contract goes out for signature from within the workflow, and the signed version returns, gets converted to PDF and files itself into the correct workspace automatically.
- Dashboards that speak different languages. A commercial team wants renewal exposure by customer. A CFO wants contract value by entity. Co-Flo builds both from the same underlying data, live.
Post-signature, that same record carries the obligations forward. Renewal windows, notice periods and compliance milestones get tracked centrally instead of living in a spreadsheet someone forgets to update. During Q&A, Pagani confirmed the platform can also read existing signed contracts to extract that data retroactively, so organizations with years of agreements already in iManage aren't starting from zero.
The case for building on what you already have
The recurring theme, on-screen and in the Q&A, was integration cost. A CLM platform that requires a new repository asks a legal team to migrate years of negotiation history and accept the disruption that comes with it. A CLM layer built on the document management system already in daily use asks for none of that.
For legal teams on iManage, that's the practical argument: the contracts, the version history and the workspace structure are already there. What's been missing is the layer that connects intake, drafting, signature and post-signature tracking into a single record, instead of leaving each stage in a separate system.
The full session runs about 30 minutes and covers the demo in more detail than a recap can, including the audience questions on e-signature integrations, litigation matter tracking and bulk-importing existing contracts.