Define what the company cares about
Set the fields, document types, diligence checks, synonyms, and output expectations every property workspace then follows.
Define the underwriting facts, documents, and diligence standards your company cares about. Fync AI 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.
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.
Fync 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.
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.
The deal package turns a messy intake into a readiness map. Borrower 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.
Upload package PDFs once. Fync 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.
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.
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.
Fync 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 →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.
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.
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.
r2://parcel/p1/h1/ ├─ source.pdf ├─ parsed/markdown.md ├─ parsed/tables.json └─ facts.json (40 facts)
Borrower documents, public data, and vendor reports flow into one evidence engine, then out to review, chat, and generated work product.
Set the fields, document types, diligence checks, synonyms, and output expectations every property workspace then follows.
Upload the OM, rent roll, operating statement, term sheet, appraisal, and sponsor materials and watch readiness fill in.
Open package blockers, missing critical fields, and unapproved facts, resolve exceptions, and draft a memo outline.
Open any fact and see source document, page, excerpt, citation match, approval state, alternates, and audit trail.
Run Census, FEMA, BLS, assessment, permits, HUD, and FRED adapters; results become cited facts alongside PDF extractions.
“What supports the NOI?” or “Show the package blockers.” Answers route to facts, package state, metrics, or document search.
Map extracted labels to a canonical field model; unmapped labels become schema candidates instead of disappearing.
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.
Fync 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.
Fync AI is a CRE underwriting intelligence workspace. Companies define their underwriting standard once — fields, required documents, synonyms, and outputs — and Fync AI applies it to every property package. Every fact is extracted from documents or external data with a verifiable citation back to the source.
Fync 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.
Fync 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.
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.
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.
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.
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.
Give your team one place to intake packages, resolve blockers, verify source evidence, and draft credit materials from reviewed deal data.