A mid-market technology company I spoke with last quarter bought Ironclad eighteen months ago. They paid $65,000 for the first year. They went through the implementation. They trained their legal and procurement teams. They built their contract templates into the system.
Today, adoption sits at 22%. Most contracts still get signed via DocuSign and emailed around. The Ironclad portal exists, but nobody opens it.
This is not a failure of effort or intention. This is a predictable outcome from a misaligned tool selection.
The adoption problem is structural, not cultural
When CLM implementations fail, the instinct is to blame change management. "We didn't train hard enough." "Leadership didn't enforce adoption." "We needed a stronger champion."
Sometimes that's true. But most often, the problem is structural: the CLM requires behavior change that the organization never had reason to adopt, and the value delivered doesn't justify the friction of changing.
Enterprise CLMs are designed around a legal-led workflow. They assume:
- Legal is the central coordinator of all contracts
- Teams are willing to log into a new portal to submit contract requests
- There is a dedicated person (or team) to maintain the system
- The company has the volume and complexity to justify the overhead
At a Fortune 500 company with a legal operations team of 15 people, these assumptions hold. At a 300-person company where the GC also handles HR disputes and M&A diligence, they don't.
"We bought a Ferrari to drive to the grocery store. The car is great. We just don't go anywhere that requires a Ferrari."
What mid-market companies actually have
The average mid-market company — 100 to 1,000 employees, $50M to $500M in revenue — manages contracts like this:
- Contracts get signed via DocuSign or similar, then land in someone's email
- The signed PDF gets saved to a shared drive folder, if the person remembers
- Key dates get added to a personal calendar or a tab in a spreadsheet
- Contract knowledge lives in one or two people's heads
- When someone needs to find a term, they search their email or ask the person who signed it
This isn't negligence. This is a rational system for the volume and complexity these companies are managing. It works until it doesn't — until someone leaves, a renewal gets missed, or a negotiation requires cross-contract data nobody has.
The 47% barrier
Research by Gartner and others consistently shows that 47% of finance leaders identify integration complexity as the single biggest barrier to CLM adoption. Not cost. Not features. Integration.
This is the signal people miss. Integration complexity isn't a technical problem — it's a behavioral one. It means: "The system doesn't fit into how we already work, so we don't use it."
In post-implementation surveys, CLMs purchased by mid-market companies average 23–35% active adoption at the 12-month mark. The majority of contracts continue to live in email and shared drives regardless of what's in the system.
Two different problems, two different tools
The confusion comes from treating "contract management" as a single problem when it's actually two distinct ones:
Traditional CLMs spend most of their engineering on the left column. The right column is often an afterthought — a dashboard that nobody uses, a notification system nobody configures.
This is the mismatch. Mid-market companies don't have a pre-signature problem. Their legal team can handle contract creation. What they have is a post-signature problem: they don't know what they've signed, when things renew, or whether they're getting what they paid for.
What actually works for mid-market
The companies that succeed at contract management at the mid-market level don't succeed by forcing adoption of a portal. They succeed by building a system that works with the behavior that already exists.
The behavior that already exists is: people email contracts. People forward contracts. Documents live in shared drives and inboxes. That's not going to change, and trying to change it is where implementation effort disappears.
The right approach intercepts contracts where they already live — in email, in Slack, in the shared drive — and extracts the intelligence from them automatically. No new portal. No migration project. No required behavior change.
"Your team didn't fail your CLM. Your CLM failed your team. The best contract intelligence system is the one your team forgets is there — because it just works."
The implementation risk nobody talks about
Every enterprise CLM comes with a sales pitch about ROI. What doesn't make it into the pitch: implementation risk.
A 3–6 month implementation means 3–6 months before you see any value. In that period, you're paying for the tool, paying for implementation support, and still managing contracts the old way while the migration happens. If adoption fails at month 12, you've spent a year of subscription fees, $30–80K in implementation costs, and your team is no better off than they were before.
For a mid-market company without a dedicated CLM administrator, this isn't a hypothetical risk. It's the median outcome.
Nissa doesn't require migration, training, or portal adoption. Forward a contract via email or Slack. Nissa extracts the terms, tracks renewals, and surfaces risk — in the tools your team already uses. Value on day one. No implementation project.