01
Origination workspace
CRM relationships, pipeline stages, contacts, tags, notes, tasks, email, and activity stay connected as a qualified opportunity becomes a borrower project.
§ Platform
Six products. One borrower file.
Most teams begin with CORE Workflow or CORE Underwriting, then add products upstream or downstream without rebuilding the relationship, opportunity, or borrower context.
The same file moves through every product.
Find the opportunity, manage the relationship and deal, convert it into a borrower project, then underwrite, document, close, and service without rebuilding context.
Find -> Manage -> Underwrite -> Document -> Close -> Service§ Product lifecycle
Find, manage, underwrite, configure, close, service.
Choose the point of entry that solves today's bottleneck. CRM relationships and pipeline opportunities become borrower projects deliberately, then each added product extends the connected context instead of creating another system handoff.
01Find
CORE Lead Discovery
Program-fit borrowers
Find borrower opportunities that fit your programs - human-screened before they touch the pipeline.02ManageCORE Workflow
Manage the relationship + deal
Manage CRM relationships, pipeline opportunities, borrower files, collection, routing, and audit history.Most teams land here03UnderwriteCORE Underwriting
Underwrite the deal
Underwrite the deal: Table Evidence, spreads, pro forma, capital, coverage, risk, and COREView.Most teams land here04DocumentCORE Credit Memos
Document the decision
Program-specific credit memo analysis - grounded in evidence, policy, risk, and analyst review.Human-in-the-loop05CloseCORE Closing
Close with control
Close with control: approval snapshot, conditions, funding reconciliation, blockers, and human certification.06ServiceCORE Servicing
Service the portfolio
Service the portfolio: boarding, obligations, ledger, payment controls, reviews, and action packages.Six products on one borrower file. Most teams begin with Workflow or Underwriting, then add products upstream or downstream as the operation is ready.
§ Progressive adoption
Start with today's bottleneck. Add products as the operation is ready.
01
Where most teams begin
CORE Workflow manages relationships, pipeline opportunities, and borrower files. CORE Underwriting turns reviewed evidence into credit judgment. Either can be the first deployment.
02
Find the next borrower
Add CORE Lead Discovery when origination needs human-screened, program-fit candidates feeding the CRM relationship and pipeline path.
03
Document the decision
Add CORE Credit Memos once the credit box, memo templates, evidence rules, and AI support are ready for governed rollout.
04
Continue after approval
Add CORE Closing and CORE Servicing when the approved file needs to move through funding and portfolio management without losing its decision history.
§ Engine layer
Program Studio is why six products do not become six builds.
CORE Underwriting configures the credit box. CORE Credit Memos adds program-specific memo templates, evidence rules, and AI support under human review.
Configured by Program Studio
A loan program is a configuration, not a build.
The document package, credit box, policy library, and memo template remain visible, versioned configuration layers across the borrower-file lifecycle.
WorkflowLoan Programs + Collection Packages
UnderwritingUnderwriting Policies + COREView
Credit MemosMemo Templates + human-in-the-loop agents
§ Inside the platform
Specialized capabilities stay connected across the borrower file.
Document intelligence, spreading, COREView, AI governance, and examiner defense connect source evidence to analysis, decisions, and replay across the borrower file.
Shared capabilities
Evidence, analysis, governance, and replay stay connected.
§ Architecture · Workflows
One project. Many workflows. One audit trail.
A project can carry multiple program-scoped financing workflows. Each workflow can follow a different loan program, stage plan, and status history while sharing one borrower file and connected audit trail.
PROJECTMaplewood Apartments·124-unit affordable multifamily·Atlanta GA·$42.0M total
- ├──Bridge$34.0Minterimapplication → underwriting → drawn → repaid at HUD close
- ├──HUD 221(d)(4)$34.0Mpermapplication → MAP review → firm commitment → closed
- └──C-PACE$4.5Mpermproject → engineer → lender consent → recorded
3 workflows·1 project·sequenced bridge-to-perm·1 connected audit trail
Disconnected setup: 3 loan records with 3 disconnected workflows.
CORE: one project view, workflow-level history, and a connected audit trail — the bridge close feeds the HUD take-out.
§ Connected operations · One controlled record
The relationship does not disappear when credit work begins.
Origination users promote a qualified deal into the formal project. Borrower-file operations, closing, and servicing then continue from the connected context, permissions, evidence, and decision history.
02
Borrower-file operations
Email, project communications, tasks, forms, collection, and data-room access remain attached to the same controlled record.
03
Post-approval operations
CORE Closing and CORE Servicing carry the decision into funding, boarding, obligations, annual reviews, action packages, and sandbox payment controls.
From the first relationship through servicing, each action stays connected to the borrower file and its decision history.
§ Next Step
See the platform on a real borrower file.
Follow one relationship from CRM and pipeline through project conversion, underwriting, closing, and servicing.