iManage vs NetDocuments

iManage and NetDocuments are the two halves of the legal document management duopoly, and virtually every Am Law 200 firm files its work product into one or the other. For twenty years the choice turned on deployment model and metadata design. In 2026 it turns on something else: which one your AI will actually be allowed to read, and what that entitlement costs on the order form.

Both vendors spent the year making the same argument — that the DMS is the permission boundary legal AI has to run through, because Harvey, Legora, Litera, Definely, and DraftWise all index the repository rather than replace it. Both shipped an MCP server to prove it. That is where the feature grids stop being useful.

The parity that isn’t

“Supports MCP” is now true of both, which is exactly why it has stopped being a differentiator. What replaced it is the entitlement question: which tier carries the agent connection, and who has to hold a seat.

iManage announced its MCP Server as available on 14 May 2026. One connection replaces per-vendor API integrations, and Harvey, Legora, ChatGPT, Claude, Microsoft Copilot, or a firm’s own agents can call it; access stays authenticated, permission-bound, and logged, and nothing is bulk-exported into a vendor index. It is distributed through Anthropic’s partner ecosystem. The announcement names no AI tier — but the MCP Server surfaces Insight+, and Insight+ is licensed separately from iManage Work, so the entitlement is real even though the pricing page is silent about it.

NetDocuments splits the same capability into two products that share a name. ndConnect Standard ships to every customer and is the manual version: a person picks documents through a picker and loads them into an approved partner app. ndConnect Enterprise is the MCP tier that lets agents search and retrieve on the authenticated user’s behalf, and it is available only to ndMAX Enterprise subscribers. As of the most recent independent setup documentation, dated 18 July 2026, it also required the organization to be approved into a limited preview, and every user who connects needed an active AI 300 subscription of their own.

That last clause is the whole comparison. On the NetDocuments side, the number of lawyers who will actually use AI is the billing unit. On the iManage side it is a module license. Those two shapes price very differently at the same headcount, and neither vendor will tell you which is cheaper until you ask both.

Where iManage wins

• You have an on-premises or hybrid estate. 78% of the iManage base runs on iManage Cloud, which means the vendor still sells and supports the other 22%. NetDocuments has never shipped a server-room edition of itself. If migrating off on-prem is not in this budget cycle, this is a one-line decision and nothing below matters.
• Ethical walls are a written procurement requirement. Need-to-know enforcement at client and matter level lives in Security Policy Manager, so an AI assistant inherits the wall instead of maintaining a parallel model of who may read what.
• Incumbency is the security-committee argument. Over 1 million professionals across 4,000 organizations, including 79% of the Am Law 100, 83% of the Global 100, and 40% of the Fortune 100. For a committee that indexes on peer adoption, that count ends the discussion.
• The agent connection is generally available, not approval-gated. iManage’s MCP Server has been announced available since May; the NetDocuments equivalent was still gated behind preview approval two months later. If your pilot has a date attached, GA beats a request form.
• AI activity shows up in the audit surface. Threat Manager now surfaces AI agent activity directly in user activity reporting — useful the first time someone asks what the assistant actually read.

Where NetDocuments wins

• Implementation costs a third to a fifth as much. Quantified below. At small and mid-market scale this dwarfs the per-seat difference and is the single most under-modelled line in the comparison.
• You admit AI tools one at a time. Administrators opt in to each AI tool individually through Security Center, so enabling MCP is a per-tool decision rather than a blanket credential. That is a materially better answer to give a risk committee than “we turned on the API.”
• The DMS line is cheaper. Roughly $40–65 per user per month against iManage’s $50–75 for comparable legal-grade configurations.
• You may already be a customer without having chosen it. NetDocuments closed its acquisition of eDOCS from OpenText on 12 January 2026 for $163M in cash, after buying Worldox in 2022. If you run either product, your migration path is already a NetDocuments conversation — though the two carry opposite commitments, and that matters (see the guard below).
• Partner breadth on the connector program. Harvey, Legora, Thomson Reuters, and Vincent by Clio all connect through ndConnect, alongside Claude, ChatGPT, Perplexity, and Copilot Studio via MCP.

Pricing reality

Neither vendor publishes a price for anything, and neither publishes a price for AI. This is worth stating plainly because the opposite is widely repeated: NetDocuments’ own ndMAX product page returns Custom Pricing in its structured data, and the $15–25 per user per month figure attached to ndMAX in circulation comes from resellers, consultants, and comparison sites — never from NetDocuments. Treat it as a negotiating anchor, not a rate card. iManage publishes nothing at all.

What reseller and consultant reporting current as of August 2026 supports:

• DMS licensing. iManage lands at roughly $50–75 per user per month on an approximately 10-seat minimum; NetDocuments at roughly $40–65 for a legal-grade configuration, with entry editions quoted nearer $20. Call it a 15–20% gap in NetDocuments’ favor on the license line.
• Implementation, where the real delta is. iManage runs about $10–15K at 10–25 users, $15–25K at 25–50, and $25K+ above 51 seats. NetDocuments commonly runs $1–5K for small and mid-sized firms and $5–20K+ for enterprise migrations. At 15 seats that is a 3–5x ratio, and it lands entirely in year one.
• A 15-seat worked example. iManage’s realistic first year is roughly $22–27K all in against about $11.7K of licensing — meaning implementation is close to half the year-one invoice. The same firm on NetDocuments pays a lower license line and a fraction of the setup.

The AI tier is quotable but not published on either side, so make both vendors quote it as its own per-user line at the number of people who will actually connect — not at total headcount. In a two-vendor market, cross-quoting is the only pricing pressure that exists.

The context-layer question

On 14 May 2026 — the same day iManage’s MCP Server went out — NetDocuments announced Context Graph, a map of how every matter, document, and communication connects across hundreds of millions of records while respecting existing permissions and ethical walls. Private preview opened that day, with broader rollout “in the coming months.” iManage spent ConnectLive 2026 framing its own direction as a context fabric over content, relationships, and live activity.

Two vendors pitching the same architectural story on the same day, both partly in preview, is not a reason to pick either. Buy the DMS you need and the AI tier you can turn on this quarter, and treat the context layer as something to hold the renewal against.

Verdict

• Pick iManage when you have an on-premises or hybrid estate you are not migrating this cycle; when matter-level ethical walls in Security Policy Manager are a written procurement requirement rather than a preference; when a security committee needs named peer adoption at Am Law scale; or when your AI pilot has a date on it and you need the agent connection generally available rather than approval-gated.
• Pick NetDocuments when you are starting clean with no on-premises estate to carry; when implementation budget rather than per-seat license cost is the binding constraint; when per-tool administrator opt-in through Security Center is the governance story your risk committee wants to hear; or when you already run eDOCS or Worldox and the migration conversation is happening anyway.
• Pick neither when matter volume is low, you already pay for Microsoft E3 or E5, and nobody is asking you to prove need-to-know access at the matter level — SharePoint will do, and what you give up is the legal metadata model and ethical-wall enforcement. And if the real problem is search across DMS, email, intranet, and client portals rather than filing, add DeepJudge alongside whichever DMS you keep instead of re-running this decision.

Default pick when you genuinely cannot decide: NetDocuments. The cannot-decide case is by definition one where neither an on-prem estate nor an ethical-wall mandate is forcing the answer, and with those two removed the implementation delta decides it — a 3–5x gap landing in year one beats a 15–20% license gap spread across the term. The condition that flips it is specific and you will know if it applies: an on-premises deployment you cannot retire, or outside-counsel guidelines that name matter-level wall enforcement.

Two guards to carry into either negotiation. First, get the AI entitlement written into the order form as its own line with the seat basis spelled out — “ndMAX Enterprise” and “Insight+” are the words that decide whether MCP works, and neither appears on a DMS quote by default. Second, if you run Worldox or eDOCS, get the support horizon into the renewal document: Worldox on-premises reaches end of life on 31 December 2026, while NetDocuments has said eDOCS on-premises has no end of life planned. A press-release commitment is not a contractual term, and the Worldox timeline shows what the other outcome looks like.