Close loans faster. Reduce headcount.
AMY reads the documents, clears the conditions, and answers the underwriter — end to end, unattended. A processor supervises. They do not process.
98.6% of processing actions fully autonomous · 6 median human minutes per file, down from 244
Requires a signature AMY cannot give on someone else's behalf.
Scheduled · Disclosure timed against the counting rule and queued to go out inside the window.…
Scheduled · Disclosure timed against the counting rule and queued to go out inside the window.…
Submitted · Package assembled in stacking order with the manifest, and delivered to underwriting.…
Automation that stops at a suggestion isn't automation.
Most tools hand a processor a better to-do list. That still leaves a person opening files, reading statements and typing. 2.0 removes the list. AMY takes the action, end to end, and a person is only pulled in for the handful of calls that are not a machine's to make.
So someone opens three documents.
So someone checks the math before clicking.
So someone reads it and presses send.
So someone submits.
The work moved. It did not leave.
Missing page 3 becomes a borrower request in the same minute. No one is told about it.
Declining bonus caught, lower figure used, rule cited, worksheet attached to the file.
On a schedule, until the document lands. Then verifies it and closes the condition.
Evidence attached against the condition it satisfies, in the underwriter's own numbering.
Stacking order, manifest, open items stated. Nobody presses a button.
What AMY does between the upload and the underwriter.
Phone photos, PDFs, a screenshot of a brokerage app. Fifteen documents classified, every page counted, every field extracted with a confidence score.
Base from the salary. Bonus averaged over 24 months — and because the trend is down, the lower figure governs. AMY commits the number and attaches the worksheet.
Beginning plus deposits minus withdrawals equals ending, on every statement. The Comerica account is a business operating account — AMY excludes it from reserves itself.
An $18,400 deposit on the 12th. It matches the gift letter already in the file, to the dollar — AMY attaches it, requests the donor statement, and closes the condition when it lands.
The 1003 built, the 1008 derived, the package stacked in the order an underwriter reads — assembled and sent. Nobody clicked submit.
Reads the pile
Calculates the income
Reconciles the assets
Sources the deposit
Submits the file
Conditions, ordered by what will actually hurt.
Not by date entered. Deadline first, then how deep the dependency runs, then effort — and AMY's own drafts float to the top, because they are the cheapest work in the queue.
July statement for Chase ****1234 is missing page 3 of 5. Provide the complete statement.
Provide documentation for the $18,400 deposit posted 07/12 to Chase ****1234, including the donor's ability to give and evidence of transfer.
Provide the hazard insurance binder listing the lender as mortgagee, with coverage at least equal to the loan amount.
Pay stub (period ending 2026-06-30) expired 8 days ago. Pay stub (period ending 2026-07-15) expires 2026-08-14 — before the expected note date. Re-request now. Pay stub: have 1 of 2 required periods.
Bank statement: missing page 3 of 5.
Borrower must receive the CD by 2026-08-22 to close 2026-08-26. If mailed rather than e-signed, it has to go out by 2026-08-19 — the mailbox rule presumes receipt 3 business days after sending.
12 CFR 1026.19(f)(1)(ii)Lock expires 2026-08-24, before the 2026-08-26 closing. Extend now — an extension bought today is cheaper than one bought the day before closing.
Five reasons
a human is called.
Not “low confidence” — AMY resolves its own uncertainty by getting the missing document. These are questions of authority, not difficulty.
- policy-exceptionRequires a guideline exception — a human underwriter owns that call.
- identity-integrityA document failed an integrity or identity check. A person confirms fraud signals.
- borrower-disputeThe borrower disputes a figure AMY derived. A person owns the conversation.
- signature-requiredRequires a signature AMY cannot give on someone else's behalf.
- adverse-actionDenial or counter-offer. Regulated notice, human decision.
Every LOS and CRM maps to one canonical file.
Encompass never talks to Salesforce. Both map into and out of a MISMO 3.4-aligned canonical model, which keeps the number of mappings linear instead of quadratic.
- Encompass
Bi-directional loan, document and condition sync against the v3 Loan Schema, with tenant-resolved field IDs.
ICE Mortgage Technology · 94% coverage - LendingPad
REST for pipeline speed, MISMO 3.4 for full-fidelity writes — the adapter picks the lane per payload.
LendingPad Corp · 88% coverage - Arrive
Event-sourced sync with cursor resume — AMY reads the loan event stream instead of re-diffing whole files.
Arrive · 91% coverage - Fineract (fork) fork
Apache-2.0 core banking fork. Mortgage rides on a loan product + datatable; AMY owns the deployment.
Apache Software Foundation · 78% coverage - Frappe Lending (fork) fork
GPL-3.0 Python fork. A Mortgage Loan DocType carries the URLA fields; roles and workflow come free.
Frappe Technologies · 82% coverage - AMY OpenLOS fork
AMY's own self-hosted LOS. Speaks the canonical model natively, so the adapter is near-identity.
AMY · 100% coverage - Salesforce
Duplicate-safe external-id upserts, composite writes, and Financial Services Cloud objects when the org has them.
Salesforce · 96% coverage - Total Expert
Mortgage-native objects — loans map close to 1:1, so milestone-driven journeys fire on real loan state.
Total Expert · 93% coverage - HubSpot
Idempotent upserts on a custom unique property, with batch endpoints for backfill.
HubSpot · 88% coverage - Surefire
Marketing automation. AMY keeps contacts and milestones fed so the right campaign fires on real loan state.
Black Knight / ICE · 74% coverage - Velocify
Lead distribution. The adapter optimizes for one number: time from lead created to lead routed.
ICE Mortgage Technology · 71% coverage - AMY CRM built in
Built in. Referral attribution, past-client triggers and campaigns keyed to real loan state.
AMY · 100% coverage
Coverage is how much of the canonical model each connector round-trips — declared honestly, because the UI reads it. See what each one can and cannot do →
The 1003 builds itself, and every field says where it came from.
All nine sections of the 2020 URLA, generated from the canonical file. Every value carries a provenance chip naming the document, the page, and the confidence.
Everything AMY produces
- 1003 / URLAAll nine sections, provenance on every field
- 1008 transmittalFully derived from the file — never typed
- Income worksheetPeriods, add-backs, and the rule that governed
- 4506-CPer borrower, pre-filled and ready to sign
- Gift letters & LOXDrafted against the deposit they explain
- Submission packageStacking order, manifest, open items stated
- MISMO 3.4 exportAUS-validated before it leaves
- Condition responsesWritten by AMY, sent by a human
AMY answers the underwriter directly. It does not wait to be told to.
Every message hangs off the condition it resolves, not a person. Response time is split by who was holding the ball — almost always AMY — so “underwriting is slow” becomes a number instead of an argument.
Provide documentation for the $18,400 deposit posted 07/12 to Chase ****1234, including the donor's ability to give and evidence of transfer.
FNMA B3-4.3-04Attaching documentation for “Source of $18,400 deposit”:
• Gift letter — gift_letter_signed.pdf (1 p.)
• Donor transfer confirmation — requested from the borrower at 15:22, received 15:38
The signed gift letter from Rosa Ochoa for exactly $18,400 matches the deposit to the dollar. AMY requested the donor's transfer evidence, received it 16 minutes later, and closed the condition — 21 minutes end to end, no one paged.
Response time, measured
Split by who was holding the ball, per thread.
Where a human comes in
A different loan, same day: an underwriter flags that a paystub's employer name does not match the VOE. That is an identity-integrity question — AMY stops, escalates, and pages the processor instead of resolving it alone.
escalated · identity-integrity · 15:52Point it at your pipeline. Stop working the file.
Connect the LOS you already run, or self-host the fork. Either way AMY takes the actions — a person is called in for the handful of decisions that are genuinely theirs to make, and for nothing else.