Neural · Mortgage & lending
The file moves at the speed of its slowest document.
A loan file is a stack of documents that arrive out of order, from people who are not paid to send them, into a pipeline judged on days to close. The loan officer's hours go to the next lead, the processor's go to chasing the last one, and the borrower hears from nobody in between. Most of that chasing is legible work: what is owed, by whom, since when. An agent layer can carry it, and put the file that is actually stuck in front of the person who can unstick it.
How to read this. Neural is the agent architecture behind the software we build and the work we run. Client engagements run under NDA, which is why no lender is named on this page. Every capability below is labelled for exactly where it stands, so you can tell what is running from what is designed.
Contents
- 01Where it goes wrongThree places, in the order they cost you
- 02One file, one weekThe whole loop, start to finish
- 03The workforceFive workflows and exactly where each one stands
- 04StandingEvery piece, and exactly where it stands
- 05DeploymentThe questions your IT group will ask first
- 06How it startsOne workflow, sixty days, read-only
[01]Where it goes wrong
Three places it costs you.
Speed to lead loses to the loan officer's day
The lead arrives while the loan officer is on a closing call. By the time it gets a reply it has been quoted by two other lenders. The first contact, the follow-up cadence and the re-engagement of the ones that went quiet are all work nobody has a spare hour for, and every hour is measured in conversion.
The needs list is a moving target
Pay stubs, statements, the letter of explanation, the updated insurance binder. Every file has a list, every borrower sends a partial answer, and the statement that was fine at application is sixty days old by underwriting. The processor's day is spent re-deriving what is still missing across forty files.
The clock is running and nobody is watching all of them
Rate-lock expirations, disclosure timing, appraisal windows, contingency dates. Each one is known, and each one is on a different screen. The one that gets missed is expensive in a way the others never were.
[02]One file, one week
What it looks like when a file stops waiting on people.
Written in the present tense for readability. This is the designed sequence, mapped to your operation.
- Mon 08:10
A borrower emails three attachments to the loan officer: a bank statement, a pay stub and a photo of a driver's licence. Nothing is labelled.
- Mon 08:11
The agent layer reads them against the file's needs list, matches each one, notes the second statement still outstanding, and flags that the pay stub is from an employer that isn't on the application.
- Mon 08:30
The processor sees the file in her queue with two items left and a drafted note to the borrower asking for exactly those two. She edits one line and sends it.
- Wed
The lock expires in nine days and the appraisal isn't back. That file moves to the top of the loan officer's list with the reason attached, instead of sitting under thirty that are fine.
- ·
Every read, every draft and every approval is logged: what it saw, what it proposed, who approved it, when.
It drafts and it flags. A person sends. The agent never touches a credit decision.
[03]The workforce
Five workflows, and where each one actually stands.
Every one has the same shape: a trigger, agent work, a human checkpoint, an artifact. The status under each name is the honest part, and it names where a workflow has actually run rather than how finished it feels.
Lead follow-up drafts
Trigger
A lead lands from the website, an aggregator or a referral partner.
Agent actions
Checks it against the CRM for duplicates and prior contact, applies your routing rules, and drafts the first touch in the loan officer's voice. Re-drafts on your cadence for the ones that go quiet.
Human checkpoint
The loan officer sends, or doesn't. The consent on file governs what can be drafted at all.
Output
A worked lead with a ready draft, minutes after it arrives rather than hours.
Document chase
Trigger
Anything arrives on a file: an email, a portal upload, a photo by text.
Agent actions
Reads it against the file's needs list, matches what it satisfies, flags what has aged out, and drafts the ask for what is still missing.
Human checkpoint
The processor reviews the read and sends the ask. Nothing goes to a borrower on its own.
Output
A current needs list per file, and the draft that closes it.
Condition tracking
Trigger
Underwriting issues conditions.
Agent actions
Turns each condition into a tracked item with an owner, drafts the borrower or third-party request it needs, and assembles what comes back for resubmission.
Human checkpoint
The processor assembles each response and the underwriter clears the condition. The agent never marks one satisfied.
Output
A conditions board per file, oldest open item first.
Executive brief
Trigger
Every morning, before anyone is at a desk.
Agent actions
Reads across the systems that hold your operation and writes what changed, what slipped, and what needs a decision today.
Human checkpoint
You reply in the thread; the work routes from there.
Output
One brief, in the order you'd have asked for it.
Deadline watch
Trigger
Daily, across the pipeline.
Agent actions
Reads lock expirations, disclosure timing, appraisal and contingency dates from the systems that hold them, and ranks the files where a date is at risk against what is still outstanding on each.
Human checkpoint
The branch manager decides what moves. It flags timing; it does not assert compliance.
Output
The short list of files that will miss a date without intervention, with the reason.
[04]Standing
Where each piece stands.
Stated precisely, because in this category precision is the differentiator.
We've built the lead-to-loan plumbing
Integrations connecting lead management, dialer and loan-origination systems, built so a loan officer's leads moved from first contact through the lending process without being re-keyed at each step. Delivered before the agent platform existed.
We know where the file actually lives
Loan origination, point-of-sale, CRM and contact-center platforms each hold part of a file and disagree about the rest. Reading across them is integration work we have done. The chasing on top of it is the workflow we have designed.
We run our own company on the agent layer
Neural plans, builds, reviews and ships at CKS every day, including the site you are reading. We will show you the live console on a call rather than a slide.
The lending workflows are designed, not deployed
Specified against the loan-file lifecycle and the systems that carry it, which is why they name needs lists and lock dates rather than generic tasks. Borrower data is nonpublic personal information: a written data-handling plan and read-only access are the starting terms, not the negotiation. Routing and ranking follow rules you set and can read, and nothing about a borrower's protected characteristics enters them.
What runs for a client stays with that client: what you see here is the architecture and where each piece stands.
[05]Deployment
The questions IT will ask.
Answered here rather than in the third meeting.
- Where it runs
- Your infrastructure or a private tenant. Not a shared multi-tenant product.
- What it reads
- The systems you already run. Read access first, always.
- Who approves
- Actions you designate as consequential stop at a named person before they happen. You set that boundary; the platform enforces it rather than relying on discipline.
- What's recorded
- Each agent action is logged with its inputs, the sources it cited, what it did, and who approved it. The things that hold up in a review.
- Who owns it
- Your data and configuration are yours, and we'll put the exit terms in the contract rather than asking you to trust a web page.
[06]How it starts
One workflow. Sixty days.
Not a platform rollout. We pick the single workflow where it is costing you most, stand it up against your real systems, and you judge it on whether it caught things your people did not have time to.
Week 1
The workflow and the success metric are agreed in the first session, not discovered over a month. Read-only access to the systems it needs; your security review runs in parallel.
Weeks 2–7
It runs alongside your people on live work. Every output reviewed by your team, nothing acted on automatically, false positives tuned weekly.
Week 8
Measured against the metric we set in week 1. Keep it, change it, or walk away. Because it stayed read-only, walking away means revoking credentials and removing an integration rather than migrating off a platform.
- What it costs
- Fixed fee, quoted after the working session, so it is priced against your actual systems rather than a guess. No per-seat licence during the pilot.
- How it's judged
- One number, agreed before we start. Usually exceptions caught that your team didn't have hours to catch, measured against a baseline period.
- What we need
- Read-only access to two or three systems, one person who reviews the output, and an executive who reads the weekly.
- What you keep
- The configuration and everything it produced, whether or not you continue. Data handling and retention are in the agreement before access is granted.
A working session is ninety minutes with your operators, not a pitch. We map where the cost actually lands and tell you which parts of it are worth pointing an agent at, including the parts that are not.
Other sectors