AI Trust and Safety

EQUIRE uses AI to accelerate CRE deal analysis: extracting rent roll data from documents, reasoning through DCF assumptions against market comps, drafting IC memo sections from extracted evidence, and surfacing prospecting research. AI augments the work — the acquisitions professional, underwriter, or general counsel remains accountable for every consequential decision.

Human review and initiation. The product is designed so that consequential changes to deal records, valuation models, and deliverables rely on explicit human checkpoints: extraction review and conflict resolution, assumption acceptance, IC memo section completion, and user-initiated export. Many deal-chat mutations that alter stored data run through approval prompts (allow / deny) before they execute — the same pattern described for prospecting chat on the overview page.

Not every automation in the platform is gated behind a separate click on that specific downstream action. Background jobs (for example document processing) persist extracted artifacts for review when conflicts exist or confidence is low, and opt-in notifications — such as email when processing completes or a scheduled prospecting digest that may include AI-generated narrative — are sent without requiring a separate manual "send" for each message by the recipient. Nothing in AI output signs, commits investment decisions, or transacts on a user's behalf.

What AI Does

The following capabilities are powered by AI within EQUIRE:

Data Extraction and Verification

• Document extraction — parses rent roll data, lease terms, operating statements, and property financials from PDF and XLSX documents uploaded to a deal.
• Extraction verification — runs a secondary model pass over extracted values to flag suspect data before it reaches the review surface.

Analysis and Reasoning

• Valuation reasoning — evaluates DCF assumptions (cap rates, rent growth, vacancy, expenses) against market comparables and fund benchmarks; surfaces a reasoning trace alongside each suggested value.
• Deal health analysis — performs coherence and deep-scan checks across extracted data to surface missing fields, contradictions, and diligence gaps.
• Prospecting research — enriches property and sponsor records with market data, owner path signals, and debt maturity information; summarizes findings in the daily mandate digest.

Drafting and Generation

• IC memo drafting — generates narrative sections for the Investment Committee memorandum using extracted deal data, valuation outputs, and research findings as source material.
• Deliverable generation — drafts executive summaries, risk assessments, loan packages, and comp analyses from deal data on demand.
• Deal assistant — answers deal-context questions and runs ad-hoc analysis; persisted mutations (assumptions, fields, annotations, conflict resolution paths exposed to the model) typically require acceptance in the chat approval UI or a downstream review surface rather than silently changing the ledger without human involvement.

What AI Does Not Do

• Does not sign, commit, or submit anything on behalf of a user.
• Does not initiate unsolicited outreach as an autonomous broker of email or outreach campaigns. The platform may deliver transactional or opt-in emails — for example "document processed" notices for uploads you kicked off, prospecting summaries for users who enable digests — without a distinct per-email compose action by the recipient; those channels are bounded by tenant settings and product flows, not by the model acting independently as a correspondent.
• Does not make or record an investment decision.
• Does not modify a source document after upload.
• Does not overwrite a value that a user has manually entered without surfacing a conflict for resolution.
• Does not share deal data across organizations.
• Does not retain deal content for model training.

Provenance and Citations

How Extracted Values Are Stored

Every value EQUIRE extracts from a document is stored as a source-linked record that carries the originating document, the extraction confidence, and the verification state. In the EQUIRE interface this is called a TrackedValue.

Conflict Surfacing

When two or more documents disagree on a value — for example, when an OM states a different rent than the lease abstract — EQUIRE surfaces the conflict in the Review tab with both candidates and their source documents. The system does not silently resolve the conflict or pick a winner through the canonical Review flow. The user selects the authoritative value, or enters a manual override.

Confidence Labeling

Values with low extraction confidence are labeled accordingly in the Deal Data tab. AI-generated narrative in the IC memo and deliverables carries no direct citation authority; numeric claims in that narrative must trace back to source-linked extracted values in the deal record.

Models and Providers

EQUIRE routes AI requests through the Vercel AI Gateway to Anthropic Claude family models when Gateway credentials are configured. Model versions are managed on a controlled update cadence and are not user-configurable. Deployments configured for Anthropic-only access (without the Gateway) do not attach the same Gateway-side option bundle; contractual and retention posture follows the deployment's provider path and your agreements.

Different workflows use different tiers within the Claude family: lighter models for verification and classification; more capable models for valuation reasoning, IC memo generation, and multi-step research agents.

Data Handling

Document Storage

Documents you upload to EQUIRE are stored in your organization's encrypted database. Access is scoped to your organization via row-level security enforced at the database layer — see Data Isolation for the enforcement model. If you expose an IC memo or deliverable via a public share link, anyone with that URL can view it — see the warning on Data Isolation.

AI Inference and Retention

For requests that traverse the Vercel AI Gateway with our standard providerOptions configuration, EQUIRE requests zero data retention at the Gateway layer (zeroDataRetention in application configuration — confirm against your contractual terms).

Nuances:

• Gateway options do not attach to inference that bypasses Gateway (direct provider setup).
• Embedding workloads that power search and retrieval also use Gateway models where configured; we are aligning attribution so auxiliary embedding traffic carries the same Gateway option bundle as conversational and extraction workloads. Until that rollout is uniform, treat embedding traffic as separately confirmed in diligence.

This page describes product behavior — the EQUIRE master agreement and supplier DPAs determine legal retention and processing terms.

Human Checkpoints

The following workflow steps require explicit human action before AI output lands in authoritative deal state or a final deliverable:

Extraction and Conflicts

• Conflict resolution — the Review tab surfaces extraction conflicts; a user selects the authoritative value before values are finalized in the deal schema.

Valuation

• Valuation assumption confirmation — AI-suggested assumptions appear alongside their source and confidence; a user accepts, overrides, or dismisses each before the DCF runs with them.

Memo and Deliverables

• IC memo section completion — AI-drafted memo sections advance to ready when you run generation; sections move to authoritative complete and the memo moves toward approved only through workflow rules that enforce review completeness.
• Deliverable export — generating and exporting a deliverable (executive summary, loan package, risk assessment) is a user-initiated action; EQUIRE does not email deliverables externally unless you or your org workflows initiate that separately.

No Auto-Apply Rule Summary

The design intent is summarized at the top of this page: human checkpoints plus approval-gated chat mutations wherever that pattern is enforced in code. Operational channels (cron digests, job-completion mail) operate under opt-in/product settings and are scoped in What AI does not do above.

Hallucination Handling

Extracted values that lack a source citation are marked low-confidence and flagged in the Review tab. EQUIRE does not promote unsourced values into the DCF model or IC memo without user confirmation paths appropriate to that workflow.

AI-generated narrative — IC memo sections, research summaries, advisor commentary — is advisory. It is produced from deal data and market research, but it is not verified against an external ground truth. Numeric values cited in AI narrative must correspond to source-linked extracted values in the deal record; reviewers should verify that correspondence before sharing output with an IC or counterparty.

Related

• AI Assistant Overview — where the assistant appears and day-to-day behavior
• Data Isolation — org scoping and share-link precautions