Docs
AI Assistant

AI Assistant Overview

How the EQUIRE AI assistant works, what it can do, and where it appears in the deal workflow.

This page summarizes where AI surfaces appear and how they behave. For human-in-the-loop controls and safeguards, see AI Trust and Safety. Deeper technical references for the platform are expanded over time alongside the product.

The EQUIRE AI assistant is a deal-context-aware analyst embedded throughout the platform. It is powered by Anthropic's Claude models via the Vercel AI Gateway.

Where the Assistant Appears

SurfacePurpose
Deal chat (every tab)Answer deal-specific questions, run comparisons against the pipeline (searchAcrossDeals, compareDealMetrics), draft text
Prospect advisorStructured mandate-fit review on origination workflows (distinct from conversational chat)
Prospecting chatConversational assistant in the prospecting workspace with prospecting-focused tools
Valuation analystMulti-step pipeline to infer DCF assumptions from extracted data and market benchmarks
IC memo generationDraft all 12 memo sections from deal data via streaming section endpoints
Document processing pipelineBackground extraction and verification of uploaded documents (not the same UX as floating chat; feeds deal data that other surfaces consume)

What the Assistant Can Do

Deal Analysis and Q & A

  • Answer questions about your deal's data: "What is the in-place rent vs market?"
  • Run portfolio comparisons from deal chat: "How does this deal's cap rate compare to others in the pipeline?"
  • Flag missing data and suggest next steps
  • Explain the Review queue from the same canonical categories shown in the Review tab: data conflict items, source review items, and field check items.
  • Navigate valuation work by reading the current DCF first, then making approval-gated updates to assumptions, OpEx, purchase/SF parameters, or the structured capital stack when you ask it to change underwriting inputs.
  • In deal chat, search processed documents for the current deal (searchDocuments); when you @-mention a document, the assistant is guided to search that file. Portfolio and prospecting chat do not expose per-deal document chunk search—they use other org- or mandate-scoped tools instead.

Drafting and Generation

  • Draft IC memo sections and deliverables from deal data
  • Produce executive summaries, risk assessments, and research narratives on demand

Deal and Institutional Memory

EQUIRE memory is governed product state, not hidden model memory. The assistant reads compact memory summaries in the prompt and retrieves raw history through tools when it needs provenance.

Deal Memory

Each deal can have a durable notebook of source-linked entries: facts, decisions, assumption changes, risks, diligence findings, task updates, agent runs, human notes, open questions, lessons, and outcomes. The assistant uses a compact deal memory brief before acting so it can see the current thesis, validated facts, prior decisions, blockers, next actions, data-release state, and recent changes without loading the entire history into every message.

When you ask "what have we already done?" or "why did we make that decision?", the assistant can read the deal brief first, then search the notebook for supporting entries.

Institutional Memory

Institutional memory captures reviewed cross-deal patterns for your organization: preferences, decision rules, recurring risk patterns, underwriting variance, diligence sensitivities, IC feedback, market precedents, and memo-style lessons. These patterns help the assistant compare a new deal against what the firm has learned from prior deals.

Historical pre-EQUIRE deals can be imported from reviewed IC memos and underwriting models. Those imports create deal outcomes, notebook entries, and draft institutional patterns for human review. Reviewed memory can influence future analysis; draft memory stays visible only when explicitly requested or during review workflows.

What the Assistant Cannot Do

Boundaries by Design

  • Access data outside your organization's deals
  • Submit offers, sign documents, or transact on your behalf
  • Reach live web sources or certain external APIs unless you enable the corresponding tool categories in the chat UI (for example web search or market-data toggles)—defaults may vary by surface

Approval-Gated Actions

Explicit Confirmation Required

Certain AI actions require explicit approval before execution (AI SDK tool approval flows: Allow / Deny). Examples include adding a prospect tag and snoozing a prospect from prospecting chat. The assistant prompts for confirmation; no mutation occurs without a user action. Many deal-level write tools in deal chat follow the same pattern.

Review-item actions in deal chat use the same Review queue contract as the UI. The assistant reads getReviewQueue before stating counts, then uses approval-gated actOnReviewItem for source review and field check items. Data conflicts still route through conflict-resolution tools, and direct corrections route through field-update tools.

Valuation mutations are also approval-gated. For financing structure changes, the assistant should inspect getValuation first and then use updateCapitalStack for all-cash, senior debt, bridge or construction future funding, mezzanine debt, preferred equity, and custom multi-layer capital stacks.

Web Search, Research Toggles, and External Integrations

In deal, portfolio, and prospecting chat, optional tools (such as web search, market data, academic paper search when the research category is on, and comparable-property discovery where applicable) are controlled by in-chat category toggles the user enables; enabled tools appear in that chat UI.

The EQUIRE MCP connector (for external clients) is separate from these in-app chat tools—it exposes connector-scoped capabilities such as excerpt search (documents:search) rather than duplicate the floating chat toolbox. Corbis MCP / deep research-agent flows are library capabilities that are not currently wired into the standard chat endpoints.

Edit on GitHub

Last updated on

On this page