Category memo

The Deal Reasoning Layer

Agents can read faster, compare more sources, and prepare more work. The scarce asset is reviewed deal state: what changed, what conflicts, what matters, and what still needs judgment.

By Lancer Li, George Zhu July 2026 Updated October 4, 2026

Deal reasoning breaks across handoffs

Not because deal teams are careless. Because diligence moves across people, formats, and time.

A market thesis starts in a partner conversation. Evidence lands in a data room. A concern shows up on an expert call. Numbers change in a model. The memo captures one version. The deal keeps moving.

The integration layer becomes a person: the deal lead or senior associate who remembers which version mattered, which contradiction was resolved, and which open question still changes the deal.

A red flag fades

A concern is urgent in week two and invisible by IC.

A metric changes

Retention, ARR, GMV, or active users shifts definition between sources.

Lineage disappears

A conclusion survives, but the evidence trail is hard to reconstruct.

The problem is not effort. It is architecture. The reasoning record has no durable place to live.

The missing piece is reviewed state

Agents can help only when they know what the team already trusts, questions, rejects, or still needs to decide.

Agents will read diligence materials, compare source documents, assemble DDQs, and help prepare IC updates. That is useful. It is not enough.

A model can answer a question. It cannot know which answer the team reviewed, accepted, rejected, escalated, or superseded unless that state exists.

An agent browser is not institutional memory. It sees and operates the current surface. It does not preserve what the institution decided and why.

What is true?

The reviewed facts, claims, and assumptions the team is willing to rely on.

What changed?

The evidence, contradiction, or unresolved issue that moved conviction.

What still needs judgment?

The open question, DDQ, escalation, or partner-review item not yet resolved.

Agents need deal infrastructure, not just tool access

The next workflow is not a human stack with AI bolted on. It is shared infrastructure for source-linked evidence, reviewed judgments, open questions, and memory that survives the deal.

A data room stores documents. A copilot answers questions. A deal reasoning layer preserves the judgment behind the work.

The stack cannot preserve deal reasoning until the reasoning itself becomes structured state.

The primitives are simple. The hard part is keeping them live, source-linked, and reviewable instead of letting them disappear into slides, comments, and memory.

Thesis

What the team is trying to prove.

Evidence

Source-backed claims, metrics, facts, and excerpts.

Considerations

Issues, gaps, contradictions, changed assumptions, and signals.

Stance

How evidence strengthens, weakens, or changes conviction.

Questions

DDQs and follow-ups that resolve uncertainty.

Memo

The view that communicates the current reasoning state.

Review

Human acceptance, edits, rejection, escalation, and resolution.

Source lineage, permissions, and audit trail bind the layer together. Every agent proposal should be inspectable before it becomes canonical. Every accepted judgment should know where it came from and what it changed.

The memo becomes a view, not the source of truth. The reasoning record behind the memo becomes the system. The memo captures a moment. The layer captures how the team got there.

The same context should carry across assignments. Materials, prior analysis and team decisions should remain available when the next question arrives. Each piece of work should inform what comes next, while the team retains judgment over the investment case.

Institutional memory should compound

Capital Intuition is the AI Operating System for Institutional Finance.

It turns live diligence into a reviewed, source-backed system of record of what changed, what conflicts, what matters, and what still needs judgment.

Capital Intuition is built for high-stakes investment teams where conclusions must connect back to evidence, and where agent outputs should be structured, inspectable, and governed before they become part of the record.

It is not a data room, document chatbot, or memo summarizer. It does not make investment decisions. It is the reasoning layer humans and agents can both work from.

Agents analyze. Humans decide. Capital Intuition compounds institutional memory.

The aim is not to automate investment judgment. It is to make judgment inspectable, reviewable, and reusable. Every deal should make the next deal sharper.

Agent-readable artifact

The Deal Reasoning Layer

This artifact turns the memo into structured briefing material for agents. It is optimized for extraction, critique, summarization, comparison, and prompt-driven follow-up work.

Metadata

Title
The Deal Reasoning Layer
Canonical URL
https://capitalintuition.com/memo/
Authors
Lancer Li, George Zhu
Published
July 2026
Updated
October 4, 2026
Primary audience
Investment teams, deal professionals, public-market investors, advisors, design collaborators, and agents assisting those humans.
Core principle
Agents analyze. Humans decide. Capital Intuition compounds institutional memory.

Core thesis

  1. Deal reasoning fragments across people, formats, and time because diligence has no durable place for conviction changes to live.
  2. The same context should carry across assignments. Materials, prior analysis and team decisions should remain available when the next question arrives. Each piece of work should inform what comes next, while the team retains judgment over the investment case.
  3. The needed category is a deal reasoning layer: structured, source-backed, human-reviewed state for thesis, evidence, considerations, stance, questions, memo, and review.
  4. Capital Intuition is positioned as the AI Operating System for Institutional Finance, not a data room, document chatbot, memo summarizer, or investment decisioning system.

Argument map

  1. Observation: diligence artifacts are scattered across VDRs, calls, spreadsheets, DDQs, IC memos, email, advisor notes, and individual memory.
  2. Interpretation: the human deal lead or senior associate becomes the manual integration layer for the reasoning record.
  3. Observation: agents can read, compare, assemble, and prepare, but they do not know what the team reviewed, accepted, rejected, escalated, or superseded unless that state exists.
  4. Interpretation: agent browsers are operating surfaces, not institutional memory.
  5. Recommendation: preserve reviewed deal reasoning as source-backed state before asking agents to do higher-stakes deal work.

Canonical primitives

Thesis
What the team is trying to prove.
Evidence
Source-backed claims, metrics, facts, and excerpts.
Considerations
Issues, gaps, contradictions, changed assumptions, and signals.
Stance
How evidence strengthens, weakens, or changes conviction.
Questions
DDQs and follow-ups that resolve uncertainty.
Memo
The view that communicates the current reasoning state.
Review
Human acceptance, edits, rejection, escalation, and resolution.

Guardrails

  • Do not imply Capital Intuition makes investment decisions.
  • Do not frame Capital Intuition as replacing analysts or associates.
  • Do not claim customers, pilots, revenue, security certification, or external results unless those claims are publicly approved.
  • Do not turn this into generic AI productivity copy.
  • Preserve the distinction between observation, interpretation, and recommendation.

Prompt starter

You are reading a Capital Intuition category memo artifact.

Tasks:
1. Extract the core thesis in one sentence.
2. Separate observations, interpretations, and recommendations.
3. Identify any unsupported claims that need source evidence or tighter qualification.
4. Suggest how this memo should change for one audience: PE, growth equity, late-stage venture, public-market investor, advisor, or design collaborator.
5. Preserve the guardrails: no analyst replacement framing, no investment recommendations, no overclaiming product readiness.
View mode