Skip to content
Fynch AI
CRE Underwriting Intelligence Workspace

Underwrite CRE deals from a single cited source of truth.

Define the underwriting facts, documents, and diligence standards your company cares about. Fynch AI collects borrower materials through controlled intake, turns each property package into structured deal data, flags gaps, enriches the file with outside sources, and helps teams review, ask, and generate from verified evidence.

Borrower portal intake Document extraction Company field dictionary Missing-data detection External data enrichment Review queues Cited chat & credit memo drafts
Sources
Offering Memo
Rent Roll
Appraisal
Census FEMA BLS Vendor
Evidence Engine
OCRExtractCross-checkCite
Property Knowledge Base
Company-defined · cited
Decisions
Review Queues
Cited AI Chat
Credit Memo
evidence in · decisions out
The problem

The deal file is fragmented before underwriting even starts.

Analysts retype numbers from PDFs, reviewers chase source pages, and outside research lives in browser tabs instead of the deal file. Teams need more than storage. They need a controlled evidence workflow.

Raw borrower PDFs
Offering memos, rent rolls, appraisals, and operating statements arrive as inconsistent PDFs.
Spreadsheet copies
Analysts retype key numbers into spreadsheets with no durable citation back to the source.
External data lookups
Flood, demographics, assessments, and market data get checked in a dozen separate tabs.
Untracked decisions
What was approved, by whom, and why lives in inboxes and tribal memory.
scattered inputs One cited source of truth
The product

Define the standard once. Apply it to every property.

Fynch AI starts with your underwriting model: the fields, documents, required checks, synonyms, and output expectations your team cares about. Every property workspace then applies that standard to the package it receives.

01 · You define
Your underwriting standard
Field dictionary, required documents, and internal output templates: the model your team already underwrites by.
02 · Fynch AI structures
A cited Knowledge Base
Borrower submissions, documents, public data, and vendor reports are extracted, enriched, and cross-checked into evidence-backed facts.
03 · Your team uses
Confident decisions
Resolve exceptions in review, ask cited questions, and draft credit memos from reviewed facts.
Borrower portal

Collect borrower materials without losing control.

Fynch AI gives borrowers and sponsors a request-specific portal for the items your team needs. Underwriters can assign setup sections, ask for documents or fact responses, and keep every submission tied to the property record, package checklist, and review workflow.

01

Invite the right counterparty

Create borrower-side records, assign setup sections, and send a secure portal invitation from the property workspace.

02

Ask for exact missing items

Request documents, facts, notes, and follow-up items as separate borrower actions instead of loose email threads.

03

Attach submissions to the deal file

Borrower uploads and responses return to the property record with request status, source category, and review context intact.

Borrower request
Harborview Apartments
2/5 complete

Upload borrower financial statement

PDF or spreadsheet, assigned to the borrower financials request.

Required
Drop file here or choose file
Submissions attach to the property workspace.
Access
Email sign-in link
Portal access stays limited to the assigned request.
Routing
Package + review queues
Received items update the deal package and reviewer context.
Sample deal walkthrough

Follow one deal from package request to memo draft.

Harborview Apartments shows how Fynch AI turns a live borrower package into a reviewable underwriting record. The story is not another feature list: it is the path from requested materials to cited facts to a committee-ready draft.

01

The borrower request opens

portal request · 5 items

Harborview Apartments starts with assigned portal requests for the rent roll, T12, borrower financials, and sponsor context.

02

The package becomes a readiness map

package status · 2 blockers

Submitted files, missing borrower items, fetched public data, and ordered reports roll into one checklist for screening and quote readiness.

03

Facts are reviewed against evidence

review queue · 4 facts

NOI, occupancy, units, sponsor liquidity, and loan terms move into the Knowledge Base with page-level source references and reviewer state.

04

The memo drafts from approved facts

credit memo · ready

Once the required facts are approved, the memo draft pulls from reviewed deal data instead of unverified summaries or copied spreadsheet values.

Harborview Apartments
184-unit multifamily acquisition
sample deal
Package readiness
4 source items
Rent roll Received
T12 operating statement Parsed
Borrower financials Requested
Appraisal Ordered
Reviewed fact
T12 Net Operating Income
Approved
$1,284,000
Operating statement · p.12 Reviewer: A. Chen
Credit memo draft
Ready
Transaction summary uses approved property and loan facts.
Financials cite reviewed T12 evidence and reviewer decisions.
Open blockers stay visible before committee materials go out.
End to end

From intake to credit memo without losing the source.

Borrower intake  ·  one connected line  ·  committee-ready memo
Feature pillars

Nine connected capabilities, one evidence model.

01 · Company standards

Define what your underwriting team cares about.

Companies define the facts, documents, synonyms, sections, and output requirements they care about. The system uses that structure to classify documents, extract fields, detect missing data, route review, answer chat, and generate internal documents.

Workspace field dictionary: labels, keys, data types, units, synonyms
Required fields and deal-package requirements
Schema candidates when a document holds an unmapped label
Field dictionary
fin.noi currency required
val.cap_rate percent required
physical.units number optional
amenities.ev_charging candidate
Submitted
Rent Roll
Present
Fetched
HUD FMR
Failed
Ordered
Appraisal
Processing
Submitted
Borrower PFS
Missing
Ordered
ESA Phase I
Blocking
Output
Credit Memo
Ready
02 · Deal package

Find out what is missing immediately.

The deal package turns a messy intake into a readiness map. Borrower portal submissions, direct uploads, fetched data, ordered reports, generated analyses, and final outputs roll into one view, so the team can see what is present, missing, blocked, or ready to use.

Borrower portalBorrower submittedMachine fetchedThird-party orderedInternally generatedFinal output
03 · Extraction

Turn borrower PDFs into structured underwriting facts.

Upload package PDFs once. Fynch AI classifies each document, parses pages and tables, extracts facts into your field dictionary, and verifies every value against its source page. Reprocessing never overwrites approved facts.

PDF-only · 50 MB limit · 39 document types · user-correctable classification
PDF Classify OCR + Parse
Pages + Tables Extract Verify cite
Knowledge Base + schema candidates
In-place NOI fin.noi
$2,940,000
Citation verified · 0.96 Awaiting approval
Operating Statement · p.62 Open PDF
Approve Reject Edit
04 · Knowledge Base

Every property fact is referenced and cross-checkable.

The Knowledge Base organizes company-defined facts by section, shows value status, source, page, and last update, and opens every fact into an evidence drawer with citation, approval, alternate values, and audit trail. Citation verification stays separate from human approval.

18 sections · search & filter · PDF / API / manual / computed / generated evidence
05 · Review queues

Keep humans in control of the numbers that matter.

Fourteen review queues turn machine output into a controlled workflow. Reviewers see what needs attention, open the supporting evidence, choose a resolution, and write a decision reason into the audit trail.

conflicts · missing critical · unverified citations · stale data · entity resolution · +9
NOI conflict
$2.94M (appraisal) vs $3.01M (offering memo)
Use currentDifferent basisReject both
Missing Appraisal
required diligence document
Mark N/A
FRED macro skipped
app-level key not configured
requires key
Census GeocoderFEMA FloodBLS UnemploymentProperty AssessmentCounty Permits HUD FMR · keyFRED · key CoStar · vendorTitle · vendorPhase I ESA · vendor
implemented requires key vendor scaffold
06 · External data

Research the deal from outside sources automatically.

Fynch AI plans, runs, retries, and audits external data adapters. Public sources and vendor scaffolds attach to the deal file the same way uploaded documents do, so research stops living in browser tabs. Absent provider keys are app-level configuration, not company blockers.

See the data provider network →
07 · Cited chat

Ask the property Knowledge Base. Get answers with citations.

Chat answers from structured property data first, then falls back to document evidence when needed. Every citation opens into the same evidence drawer used across the workspace.

structured data first · document evidence fallback · every answer cited
What supports the NOI?
Answered from approved facts
In-place NOI is $2,940,000 on a trailing-12 basis, supported by the operating statement and corroborated by the appraisal.
Operating Statement · p.12 Appraisal · p.41
Credit Memo Ready to generate
Depends on
Term SheetRent RollOperating StatementAppraisal
Generate Credit Memo
08 · Generated outputs

Draft credit memos from approved, citation-verified facts.

Generate credit memo drafts from approved, citation-verified facts. Additional output types are dependency-gated, so teams can see what is ready, blocked, or still missing before any work product is created.

credit memo drafts live today · 7 more output types dependency-gated
09 · Operations

Built for auditable pipelines, not black-box demos.

The Developer view exposes pipeline state without leaking secrets. Operators can inspect dictionary configuration, document artifacts, extraction runs, vector chunks, enrichment runs, and environment presence booleans.

artifacts · runs · vector index · env presence (no secret values)
developer · run_a1f9c2 · env live
r2://parcel/p1/h1/
  ├─ source.pdf
  ├─ parsed/markdown.md
  ├─ parsed/tables.json
  └─ facts.json  (40 facts)
run_a1f9c2parsed
run_b73e10needs_review
enrich_hudskipped_requires_key
Data provider network

Connect the sources that shape a CRE underwriting decision.

Borrower portal submissions, documents, public data, and vendor reports flow into one evidence engine, then out to review, chat, and generated work product.

Property Knowledge Base
evidence engine
Borrower portal + package
Portal requestOffering MemoRent RollOperating Stmt
Term sheet
Sources & Uses · Sponsor PFS
Public data
CensusFEMABLSPermits
Vendor / ordered
CoStarTitlePCAPhase I
Key-gated
HUD FMR · FRED · Census ACS
Decisions
ReviewChatCredit Memo
cited facts → work product
Use cases

What underwriting teams do with Fynch AI.

01

Define what the company cares about

Set the fields, document types, diligence checks, synonyms, and output expectations every property workspace then follows.

Field dictionaryPackage templateSchema
02

Collect a new acquisition package

Send borrower portal requests, receive the OM, rent roll, operating statement, term sheet, appraisal, and sponsor materials, then watch readiness fill in.

Borrower portalExtractionPackage
03

Prepare for quote committee

Open package blockers, missing critical fields, and unapproved facts, resolve exceptions, and draft a memo outline.

Missing dataReviewCredit memo
04

Replace manual fact checking

Open any fact and see source document, page, excerpt, citation match, approval state, alternates, and audit trail.

EvidenceCitationsAudit
05

Bring public data into the deal file

Run Census, FEMA, BLS, assessment, permits, HUD, and FRED adapters; results become cited facts alongside PDF extractions.

EnrichmentAPI evidenceFreshness
06

Ask a cited question

“What supports the NOI?” or “Show the package blockers.” Answers route to facts, package state, metrics, or document search.

Chat routesCitationsVector search
07

Standardize the underwriting data model

Map extracted labels to a canonical field model; unmapped labels become schema candidates instead of disappearing.

SynonymsSchema candidatesSections
Trust & control

AI where it helps. Human approval where it matters.

The system separates citation verification from reviewer approval. A fact can be extracted and source-matched without being approved. Reviewers approve, reject, edit, resolve conflicts, and log reasons directly against the evidence. Every decision is captured in the audit trail.

Machine
Citation verified
Human
Awaiting approval
Reviewer actions are logged with who, when, prior value, and reason.
Approve Reject Edit
Compliance, governance & data

Built for reviewable CRE underwriting in regulated financial institutions.

Fynch helps lending teams collect borrower materials, extract cited facts, route human review, and generate credit work products from an auditable evidence base. Your institution retains credit policy, approval authority, and model governance.

No customer-data training.

Fynch does not use customer data to train foundation models or enrich other customers' workspaces. Customer workspaces default to zero-retention model logging where supported by the selected model provider. Audit trails are retained in the customer trust portal to support customer review, security monitoring, and compliance workflows.

Human-controlled AI

Fynch supports underwriting teams without making autonomous credit decisions. Reviewers approve, edit, reject, or escalate extracted facts before they are used in credit work products.

  • Reviewer queues for conflicts and missing critical facts
  • Approvals, edits, overrides, and decision reasons
  • Generated outputs based on reviewed evidence

Evidence lineage

Every material fact can point back to source evidence, reviewer action, and downstream use in a generated memo or credit package.

  • Page-level citations for borrower and vendor documents
  • Audit logs stored in the customer trust portal
  • Standard 30-day retention, with 365-day options for selected records

Data protection

Customer materials, extracted facts, and generated outputs stay isolated from other customer workspaces and are not reused across customers.

  • Tenant-isolated workspaces with per-tenant keys
  • Encrypted in transit and at rest
  • No cross-customer training or data reuse

Enterprise access

Fynch aligns platform access with enterprise identity, access-management, and least-privilege policies.

  • SSO via SAML or OIDC
  • MFA, SCIM, and JIT provisioning
  • Role-based permissions and access logs

Deployment flexibility

Different institutions have different policies for model execution, data residency, and hosted services.

  • Cloud-provided LLMs or on-premises open-source models
  • Enterprise isolated deployments up to on-premises hosting
  • Customer-selected model and provider configuration

Operational readiness

Fynch maintains security and operational processes intended to support financial-institution vendor-risk reviews.

  • Incident-response plan
  • 99.9% uptime target and 3-hour response-time option
  • Continuous penetration testing
Bank concern
Fynch response
Vendor-risk review
Diligence package, security overview, data-flow diagram, external dependency inventory
AI governance
Human review, cited facts, output limitations, approval trail
Data confidentiality
Tenant isolation, per-tenant keys, encryption, no cross-customer data reuse
Explainability
Page-level citations and evidence lineage
Auditability
Customer trust portal stores audit logs, approvals, edits, overrides, and workflow history
Access control
SAML, OIDC, MFA, SCIM, JIT provisioning, RBAC, least-privilege permissions
Incident response
Incident-response plan, 99.9% uptime target, 3-hour response option, penetration testing
SOC 2
SOC 2 readiness in process; interim materials available under NDA

Important limitation: Fynch outputs are assistive work products. Final underwriting, credit, compliance, and approval decisions remain with the financial institution.

Platform

Built to be inspected, not taken on faith.

Fynch AI is built around persisted artifacts, typed workflows, audit trails, encrypted storage, and workspace-level isolation. Every document run, enrichment, fact, review action, and generated output is traceable.

Elastic scale
Spikes in uploads and extraction scale out automatically. No capacity planning.
Encrypted & isolated
Documents and facts are encrypted in transit and at rest, isolated per workspace.
Always-on reliability
Managed, redundant infrastructure keeps deal files available when you need them.
Auditable by default
Every fact, run, and review decision is persisted and traceable end to end.
SOC 2-aligned practicesEncryption in transit & at restRole-based accessFull audit logging
Product surface today
18
Knowledge Base sections
14
Review queues
19
Enrichment adapters
39
Document types
8
Generated output types
5
Package source categories
FAQ

Answers for underwriting teams evaluating Fynch AI.

What is Fynch AI?

Fynch AI is a CRE underwriting intelligence workspace. Companies define their underwriting standard once — fields, required documents, synonyms, and outputs — and Fynch AI applies it to every property package. Every fact is extracted from documents or external data with a verifiable citation back to the source.

What does Fynch AI do that storage and spreadsheets can't?

Fynch AI is a controlled evidence workflow, not a file store. It classifies documents, extracts fields into your dictionary, runs public and vendor enrichment, detects gaps and conflicts, routes exceptions to reviewers, and generates credit memo drafts — all anchored to citations and an audit trail.

What document types does Fynch AI support?

Fynch AI supports 39 document types across borrower-submitted PDFs (offering memos, rent rolls, operating statements, appraisals, term sheets, sponsor PFS), third-party reports (appraisal, Phase I ESA, PCA, title), and internally generated artifacts. PDF uploads are capped at 50 MB and document classification is user-correctable.

Does Fynch AI include a borrower portal?

Yes. Fynch AI includes a borrower portal for request-specific intake. Teams can invite borrowers or sponsors, assign setup sections, request documents or fact responses, and route submissions back into the property workspace, deal package, and review workflow.

How does the citation system work?

Every extracted fact stores its source document, page, excerpt, and citation confidence. Citation verification is performed by the system; reviewer approval is a separate human action. A fact can be source-matched without being approved, and reviewers can approve, reject, edit, or resolve conflicts directly against the evidence.

Which external data sources are connected?

Public-data adapters cover Census Geocoder, FEMA Flood, BLS Unemployment, property assessment, and county permits. HUD FMR, FRED, and Census ACS are app-level key-gated. Vendor scaffolds exist for CoStar, title, Phase I ESA, and PCA. Nineteen enrichment adapters in total.

What outputs can Fynch AI generate?

Credit memo drafts are generated today from approved, citation-verified facts. Seven additional generated output types are dependency-gated so teams can see what is ready, blocked, or still missing before any work product is created.

How is the platform secured?

Workspace-level isolation, encryption in transit and at rest, role-based access, SOC 2-aligned practices, and full audit logging. The developer view exposes pipeline state — artifacts, runs, vector chunks, and env presence — without leaking secret values.

Demo calendar

Book a focused underwriting walkthrough.

Walk through a sample CRE package, the evidence model, and the review workflow with the product in front of you.

What we'll cover
Map your current underwriting flow
Start with how your team receives packages, checks facts, resolves gaps, and prepares committee materials.
Walk through the evidence workflow
See borrower portal intake, cited extraction, missing-data detection, review queues, and credit memo drafting in context.
Pressure-test fit and rollout
Talk through field dictionaries, security expectations, pilot scope, and the data sources your team already relies on.

No prep is required. If you have a sample package, checklist, or memo template in mind, bring it and we'll use that as the reference point.

Open calendar in a new tab
Fynch AI demo calendar
Calendly secure scheduling

Build a more reviewable underwriting workflow.

Give your team one place to intake packages, resolve blockers, verify source evidence, and draft credit materials from reviewed deal data.