For lenders/From the first email to the last condition
Loans move forward the day they arrive.

Your systems record the decision. Nothing records how you reached it.
If someone has to defend a number, to a borrower, an investor, a committee or a regulator, it is built on the loan file.
Precurion for lenders
One constructed file, worked end to end. The arithmetic ties and the clock runs one way.
41
Documents already read and filed when the officer opened the file
12
Paper figures that open the page they came from
4
Conditions named by mid-morning, none of them waived
A loan is judged three times.
When you write it, while you hold it, and when someone asks you to justify it. One record has to survive all three.
Fwd: Carroll Gardens portfolio — 3 buildings, ask $38m
Team: purchase agreement and rent roll attached, T-12s to follow this morning. Sponsor is Roundhouse, a repeat borrower of yours. Looking for $38m on an 18-month bridge, IO. Can you take a look this week?
The documents chase themselves.
Material keeps arriving where it already arrives: mailbox, drive, origination system. What changes is that it is read and filed against the loan at the hour it lands, not on the day someone gets to it. What is missing is named while it is still cheap to fix: by 10:04 on this file, four conditions were open and each one had a name. The chaser is drafted, addressed and dated for you. Nothing goes out under your name until one of your people sends it.
The first pass, done before you open the file.
Company and registry records pulled, statements read line by line, and figures that disagree surfaced as a disagreement with both sources kept: $249,400 on the rent roll against $243,100 on the T-12, neither one overwritten. Computed values carry a leading = and say so; a figure no document carries stays an em dash until one does.
Verification
Carroll Gardens Portfolio · 7 rows · against your policy$63,400,000
Purchase agreement, p. 4 · read 09:24 · sourced
$5,280,000
Renovation budget, p. 2 · read 09:47 · sourced
$249,400 ≠ $243,100 — raised
Rent roll, 57 lines · $249,400 | T-12, p. 3 · $243,100 · both kept, neither overwritten
=$76,000,000
Computed · $63,400,000 + $5,280,000 + $7,320,000 · marked as computed, not sourced
=50% · holds
Computed · $38,000,000 against $76,000,000 · your policy, not ours
12 · all at 534 Henry
Rent roll, lines 1–12 · read 09:31 · the plan cannot touch these rents
— outstanding
Requested 10:04 · one of 4 open conditions · an em dash until a document carries it
Recommendation
The facility is recommended at $38,000,000: =50% of a total project cost of =$76,000,000, inside the 60% ceiling. Two statements disagree on in-place income: $249,400 on the rent roll against $243,100 on the T-12. This paper carries both. The committee should decide which it underwrites to.
The credit paper drafts itself from the record.
Not a summary. An argument assembled from values that still point at their pages. Where two statements disagree, both are carried into the recommendation rather than resolved out of it, and the committee is told which question it is deciding. It leaves as the Word document your committee already reads, and there is a whole one you can read before you speak to us: not an excerpt, the whole paper, the way it leaves the system.
No decision is ever made by the system.
The record carries who accepted what, what they accepted it on, and what it looked like before. Every figure opens the page it came from and every acceptance carries a name and an hour, kept as the facility lives. A number that is wrong is a wrong page you can open, rather than an answer you have to take on trust.
Nothing here is re-keyed. That is the whole of it.
A CRM, then an origination platform, then a credit system, and the same figure entered into each of them. What breaks is not the workflow. It is that no one place holds how the number was reached.
The loan does not stop being a loan when it completes.
The file should not disassemble at completion.
Every condition will keep the party it waits on, the date it is due and the document that discharges it, so the annual starts from a file that is already built rather than an empty folder and four mailboxes.
Coming
Insurance broker · discharged by Certificate of insurance
Counsel · discharged by Title commitment
Environmental consultant · discharged by Phase I report
Sponsor · discharged by Reconciled rent roll
Watching them for you, and the quarterly portfolio picture, are what we are building next.
When someone asks how, the record answers.
A committee, an investor, an examiner or a buyer of the book are all asking one question, and the file answers all four out of the same trail. The record you start keeping this quarter is the one that answers next year's questions.
Every lender will have the tools. Not every lender will have the record.
The loans we do this for.
Bridging to invoices. Whatever the collateral, the record is assembled the same way.
We go in and get the loan shop AI-ready.
Week 0
Verification
against your policyIt starts on your file
One of your live deals, run against your own policy before anything is signed. You see where it holds and where it breaks.
Weeks 1–6

Wired into the work
Mailbox, drive, origination system. Your loan processes, your criteria, your credit boxes and your mandates, mapped into the record. We do not ship a view on what a good loan is.
Ongoing
Accountable, in the room
We sit with the team until the workflow carries itself, then stay on retainer: for the connectors, the policy changes, the examiner's questions, and the next place AI earns its keep.
A deployment only counts when the team stops needing us in the room.
AI-ready, not AI-dependent.
We take on a few of these at a time, deliberately.
What credit officers ask us first.
What happens when it gets a number wrong?
You see where it came from. Every value names its document and page, so a wrong figure is a wrong page you can open rather than an answer you have to trust. A figure no document carries is marked outstanding: an em dash, never an estimate.
Who is accountable for the decision?
Your officer, by name and hour. The credit decision never enters the system; the record carries who accepted what, what it was accepted on, and what it looked like before.
Where does our data sit?
One stated home for your data, in your region, and you can take it out whole on any day you like.
Do we own it, or are we licensing it? Why would we not have someone build this for us?
Agents are the cheap part. The governed record is the hard part. The agent your team could build this quarter is genuinely capable, and it would be standing on Excel. What sits underneath it is not a project: it is a permanent line in the operating budget, a year of someone's roadmap, and somebody to maintain it after they leave. On the licence, plainly: it is self-hosted and extendable, what we configure for you is yours to run and to extend, and the one restriction is that you do not relicense it to your competitors.
What about the two thousand files we already have?
We have not brought a back book across at scale, and we would rather say that than sell you a plan we have not run. When your book needs to come across, it comes across with us in the room, and we tell you what that takes before you commit to it. A closed file is documents, and documents are what this reads.
We already work with an AI vendor. Why would we run two?
Because they are not the same object. A workspace keeps the state you left it in. This keeps how you got there: the documents, the figures and the page behind each one, on the loan. When someone has to defend a number, that is the file they defend it from.
What is not built yet?
The part that runs after the yes. Six of them are named in full on this page, in amber, rather than kept for the third call.
See the first pass, live.
Thirty minutes on a real deal, mid-process. We bring the file, and every figure names its page as it happens. Nothing to install, nothing for you to send, no deal of yours in the room.




