Company brain for M&A: what to capture before, during, and after the deal

Deal teams already run on judgment scattered across Slack, counsel inboxes, and the one associate who remembers the last carve-out. Company Brain for M&A makes that judgment queryable, with sources, confidence scores, and human confirm on every decision.

This post is for corp dev, legal ops, and integration leads who want to know how Company Brain for M&A differs from a virtual data room or a sell-side prep sprint.

Company brain for M&A vs a data room

Data rooms answer retrieval: where is the contract, who signed, what changed in v3. Company Brain for M&A answers decision memory: why Morrison approved the 18-month portfolio overlap lookback, what IC flagged on Coastal Freight, who owns billing after the rate-deal exception.

Both matter. They are not substitutes. Ignius sits in the decision layer, often before anything becomes a polished memo. Company brain vs data room AI goes deeper on where each tool fits in diligence.

Before the deal: conflicts and counsel precedents

Most M&A friction starts before the CIM. Outside counsel has intake SLAs. Conflicts partners want prior matter IDs cited. Fee caps from the last engagement become the default for the next one, unless someone remembers to renegotiate.

On the Horizon Logistics demo, the Partner group holds this kind of memory. Morrison & Kerr gives Horizon's relationships team four business hours to respond on PE conflict checks. If there is no portfolio overlap in the last 18 months, the conflicts partner signs off the same day. Carve-out docs need a prior matter ID and the lookback window cited before approval.

That pattern showed up again on Coastal Freight. The conflicts memo cited an 18-month portfolio overlap lookback and a prior matter ID from an earlier PE rollup. Without a decision someone confirmed at the time, the next associate rebuilds the precedent from email threads and SharePoint folders named something like "conflicts-memo-FINAL-v3."

Capture at decision time, not in a post-mortem wiki sprint.

During diligence: judgment that never makes the CIM

Data rooms excel at documents. They struggle with the Slack thread where partners agreed the conflicts memo could cite a prior matter ID, or the IC dissent arguing Gulf Coast churn might have been overstated.

Horizon's Portfolios group holds IC-style judgment from the Coastal Freight rollup vote in Q1 2025. IC voted no, 4-2. Coastal Freight's top three shippers exceeded Horizon's 45% concentration threshold. The capex cycle did not fit Summit's asset-light thesis. Hub consolidation claims had no third-party logistics audit behind them.

Two dissent votes argued churn might have been overstated. Customer concentration still hit the automatic pass trigger. Six months later another acquirer paid 2.1x EBITDA. The post-mortem in #investment-committee noted the dissent on churn was partly right. IC now requires a third-party logistics audit on hub consolidation claims before the next rollup vote.

None of that lives cleanly in a data room keyword search. It lives in threads, meeting notes, and the memory of whoever ran the diligence sync.

Company Brain for M&A captures those decisions when someone confirms them: exceptions that never made the CIM, red flags IC tracked, follow-ups owners accepted, dissent arguments worth revisiting on the next deal.

After close: integration memory

Integration playbooks fail for the same reason wikis fail: the handoff corp dev promised finance gets documented six months late, if at all. Which systems stay separate on purpose. Which escalation paths survived day 100. Who owns billing after the rate-deal exception.

These are process decisions, not contract PDFs. They belong in scoped folders in your Company Brain so legal Ask does not pull unrelated ops threads. Partner and Operator groups in the Horizon demo show how different baskets keep retrieval precise.

For the full capture model, see What is a company brain?. For storage policy, see What a company brain captures.

Why search fails M&A teams

Keyword search over a data room returns chunks. It does not return the Slack thread where partners agreed on a carve-out template. It does not return confidence that the answer is current, or who confirmed it.

Company Brain for M&A adds human confirm before anything becomes permanent memory, context groups so legal retrieval does not pull unrelated ops threads, and citations to Slack, email, and tickets rather than paraphrase over everything.

Enterprise search still matters for finding the contract. Memory creation matters for finding the judgment. Glean searches memory. Ignius creates it. explains the split.

What belongs in Company Brain for M&A workflows

Use "company brain for ma" as shorthand for mergers-and-acquisitions memory, not a generic AI folder:

Conflicts and legal precedents: carve-out templates, outside counsel fee caps, matter IDs cited in prior PE rollups.

Diligence judgment: exceptions that never made the CIM, red flags IC tracked, follow-ups owners accepted.

Thesis and IC memory: why the team passed, what would reopen the deal, how thesis changed post-close.

Integration playbooks: handoffs corp dev promised finance, systems kept separate on purpose, escalation paths that survived day 100.

Try it on sample M&A data

The Horizon Logistics demo includes Partner with conflicts precedents and Portfolios with IC-style judgment. Ask "What blocked Horizon from acquiring Coastal Freight Partners?" or "When has Morrison used a carve-out for an already-representable portco?" and the answers cite confirmed decisions with source links.

For the product layer, see Company Brain for teams and the dedicated Company brain for M&A use case.

FAQ

Does a company brain replace a data room?

No. Data rooms handle document retrieval: contracts, signatures, version history. Company Brain for M&A handles decision memory: why counsel approved a lookback window, what IC flagged, who owns an integration handoff. Most deal teams need both. See Company brain vs data room AI.

Who confirms decisions on the deal team?

Whoever was in the room or thread when the judgment happened. Corp dev confirms IC decisions. Legal ops or the conflicts associate confirms counsel precedents. Integration leads confirm handoff decisions. Nothing saves silently. If nobody confirms, the candidate stays in the capture inbox or disappears.

Can we use this during live diligence?

Yes. That is the point. Connect Office, GitHub, and Xero as read-only signals. Capture candidates surface while diligence is running. Confirming a decision takes seconds. The alternative is rebuilding precedent from email at 11pm before the IC memo is due.

How is this different from sell-side prep tools?

Sell-side prep tools help produce documentation before a process starts. Company Brain for M&A preserves judgment across deals: why you passed on Coastal Freight, what Morrison's fee cap precedent is, what the dissent argued. The value compounds deal to deal.

What about confidentiality and wall-crossing?

Context groups keep retrieval scoped. Partner does not share a retrieval space with Operator unless someone publishes upward. Private groups stay private until deliberately shared. Connect integrations are read-only signals; nothing becomes permanent without human confirm.

Where does Ignius fit vs enterprise search on a deal team?

Search finds the doc in the data room or SharePoint. Company Brain finds the decision about the doc: who signed off, what exception applied, what would change the answer today. Ignius vs Glean lays out the broader comparison.

Request early access to run Company Brain on your deal team's connected tools.