Is Mage a Harvey competitor?

Partly. Both are legal AI tools used in M&A workstreams, but the products are differently scoped. Harvey is a firm-wide assistant covering many practice areas. Mage is purpose-built for M&A diligence end-to-end (data room ingestion, risk-driven document review, amendment chain resolution, schedule and memo drafting, redline review, post-signing tracking). On M&A specifically, the comparison is about whether you want a generalist tool that touches your deal alongside other practice areas, or a specialist tool that owns the deal.

Why not just use ChatGPT for diligence?

Because ChatGPT (and Claude, Gemini, etc., used directly) hallucinate on contract analysis, cannot resolve amendment chains, have no privilege posture by default, and have no workflow. Generic LLMs are good for first-draft writing assistance and not for production diligence. Domain tools layer prompt design, validation, document handling, and accuracy infrastructure on top of the same base models that generic chat exposes raw.

What about Kira, Luminance, ContractPodAi, Legora?

Each occupies a different slice. Kira and Luminance are mature contract-extraction tools whose strength is the original generation of clause classifiers. ContractPodAi is more CLM-shaped (lifecycle management) than diligence-shaped. Legora is closest to Harvey in firm-wide-assistant scope. Mage's positioning is M&A-specific depth: doing the things M&A counsel actually do on a deal, end-to-end, without trying to be the assistant for everything else.

How should a firm actually pick?

Run the same deal in parallel through the candidate tools (with anonymized or simulated data, or a real deal under a paid pilot). Compare the issues lists, the memo drafts, the schedule output, and the time-to-deliverable against the firm's manual baseline. The right tool will be obvious within two deals; the wrong one is also obvious.

Where does M&A-specific depth actually show up?

In the things only M&A counsel deal with: amendment chain resolution, indemnity package interaction, change-of-control trigger taxonomies, MAC-out language patterns, sign-to-close interim covenants, disclosure schedule synthesis from source contracts. A firm-wide assistant can answer questions about these. A specialist tool produces partner-grade output on these as core workflow.

Legal AI vs. Harvey vs. Generic AI: How to Evaluate

The legal AI category is in a Cambrian moment. Dozens of products are in the market, and the actual quality differences between them are large. This guide is an honest attempt to draw the lines, written by people who built one of the products and have nothing to gain from a fuzzy answer.

The frame: most discussions of "legal AI" mash three different categories together. They are different in what they do, who they serve, and where they fail. Once you separate them, picking the right tool gets simpler.

Category 1: Generic LLMs (ChatGPT, Claude, Gemini, etc.)

The default starting point for any firm dabbling in AI. Cheap, familiar, immediately accessible.

What they're good at: First-draft writing assistance. Summarizing a single contract for the team. Reformulating dense legalese into client-readable language. Brainstorming arguments. Drafting a generic NDA. Proposing language for a non-controversial provision.

What they fail at:

Contract analysis at scale. Loaded with a 1,500-document data room, a generic LLM has no native concept of order, no workflow, and a strong tendency to hallucinate clause references. The fluency is the trap.
Amendment chain resolution. Off-the-shelf RAG implementations (which is what generic chat tools use) have no understanding of which version of a provision is operative. They retrieve the most semantically-similar chunks and synthesize. The result is confidently wrong on multi-amendment contracts. We expand on the failure mode in Amendment Chain Resolution.
Privilege posture. Default ChatGPT and Claude consumer products log conversations and may use them for training. Enterprise tiers are better, but the burden is on the buyer to verify; the buyer should require written DPAs covering training and retention before any privileged document touches the platform.
Workflow. A generic chat tool has no concept of "scan 1,200 contracts against 47 risk checks, group findings by severity, route the high-severity ones to senior associate review, and produce a partner-grade memo." That is what M&A diligence actually requires.

When to use them: For first-draft writing assistance on non-privileged content. Treat the output as a starting point, not a deliverable.

When not to use them: For anything that touches privileged client data and requires production-quality output.

Category 2: Firm-wide assistants (Harvey, Legora, similar)

The next layer up. These are products positioned as cross-practice AI assistants for the entire firm. They understand legal terminology, work across litigation, transactional, regulatory, and other practices, and integrate with firm document stores.

What they're good at: Cross-practice coverage. Question-answering across a firm's document corpus. First-draft writing assistance with legal grounding. Research support. Memo drafting at the level of a competent first-year associate. The firm-wide assistant pitch is real and the better tools deliver on it for general practice.

What they're scoped not to do: M&A diligence end-to-end. None of the firm-wide assistants are built around the deal-team workflow specifically. They can answer questions about contracts in a data room. They are not the tool that runs the diligence.

Where this matters: For a firm whose M&A practice is small and whose primary AI need is firm-wide leverage, a Harvey-style tool covers the ground. For a firm whose M&A practice is core, the firm-wide assistant is complementary, not sufficient. Many firms run both.

Honest framing: We have a lot of respect for the engineering at Harvey and Legora. The reason Mage exists is not that they are bad tools; it is that the M&A workflow has specific shape that benefits from a specialist's attention. A general physician and a cardiac surgeon are both useful for different reasons. (See our Harvey alternative page for the long-form positioning.)

Category 3: M&A-specific tools (Mage, segments of Kira/Luminance, others)

The third layer is specialist tools focused on transactional work. The category is small, the differences within it are large, and Mage is the clearest example of what we mean by it.

What they're good at: Owning the deal end-to-end. Data room ingestion across providers. Risk-driven document review against partner-defined checklists. Amendment chain resolution. Disclosure schedule synthesis. Memo drafting in firm voice. Redline review. Post-signing covenant tracking. The full sequence an M&A team actually executes on a deal.

What they're not designed for: Cross-practice question-answering, broad firm-wide assistance, generic legal research. A specialist M&A tool is not the right place to ask about your firm's litigation precedents.

Where this matters: For a firm whose M&A practice is core, the specialist gives you partner-grade output on the workstreams that consume the most associate hours. The leverage is largest on the highest-volume work.

How to actually compare

The honest comparison method is to run the same deal in parallel through the candidate tools. The vendor demo will not tell you what you need to know; the demo is built to look good.

A reasonable evaluation plan:

Pick a real deal you have already closed, where you have the partner-reviewed memo, the issues list, and the disclosure schedule as ground truth.
Re-run diligence on it through the candidate tools. Use the same risk checklist, the same data room, the same time budget.
Compare against ground truth on three axes:
- Issue spotting accuracy: how many of the real issues did the tool surface, and how many false positives did it generate?
- Output quality: how much does the partner have to rewrite the memo and schedule before the firm would send them?
- Time-to-deliverable: from data room access to partner-reviewable output, how many hours of associate time?
Stress-test on the hard parts: amendment chains, custom indemnity packages, multi-jurisdiction issues, contracts in non-English languages.

The tool that wins this comparison on your deals is the right tool for your firm. The tool that loses is the right tool to pass on, regardless of brand.

Where we land on the head-to-head

We have written more pointed pages on individual head-to-head comparisons. Each is a long form analysis with feature-by-feature detail rather than marketing language.

A short-form summary, written as honestly as we can:

Generic ChatGPT/Claude/Gemini: useful for writing assistance on non-privileged content. Not appropriate for production M&A diligence. The accuracy gap, hallucination risk, and lack of workflow are not problems the buyer can solve at the prompt layer.
Harvey, Legora, similar firm-wide assistants: useful for the firm whose primary need is cross-practice leverage. M&A teams often use them for question-answering and first-draft work, then run the deal itself through a specialist tool. We do not claim Mage replaces a firm-wide assistant; we claim it is a better fit for M&A diligence specifically.
Mage: built for the M&A workflow end-to-end. The sweet spot is firms and PE shops where M&A diligence is high-volume, partners need partner-grade output, and the complexity of the work (amendment chains, custom indemnity, multi-jurisdiction, sign-to-close tracking) justifies a specialist tool.

A word on transparency

In a category this young, vendor claims are often softer than they look. We work hard to publish accuracy methodology, security posture, and limitations honestly. See:

How We Measure Accuracy — the methodology behind any accuracy number we cite.
Security & Compliance — SOC 2 Type II, no-training, isolated infrastructure, the things that should be table stakes and aren't always.
Cloud vs. On-Premise Legal AI — the architectural debate honestly framed.
The F1 Engine Problem — why infrastructure matters more than model choice.

How to start

The right move for any firm seriously considering AI for M&A is to pilot a real deal. Vendor demos are designed to win. Real deals are designed to ship. The tool that survives a real deal is the one to standardize on.

Request a demo and bring a current or recent deal. We will run end-to-end diligence on it, produce the memo and schedule, and walk you through the result against your manual workproduct. The decision after that should be obvious in either direction.

For the operational counterpart of this guide, see AI Due Diligence: An Operational Playbook. For the master hub on the category, see Legal AI for M&A. For a buyer's guide framework, see Evaluating Legal AI Tools.