Why we build this

In most mortgage shops a loan moves quickly until it reaches something only one or two people know how to handle. It might be a self-employed borrower whose income has to be worked out from two years of tax returns, or a findings report that comes back ineligible with several ways to fix it and no obvious first move. At that point the file stops and waits for someone senior.

We build software that works those moments out, so the file keeps moving without waiting for anyone.

Where a loan waits

When we spoke with mortgage lenders in Michigan in September, they described the same loop in their own words. “You fix it, run it. Fix something, run it. Edit this, run it. Sometimes it’s 27 times.” One of them put the cost of it plainly: “We literally have somebody full-time on payroll, and all they do is they restructure files.”

Nobody in that loop is doing anything wrong. The work is real, it takes judgement, and the people who do it well are rare. The trouble is that it is done by hand, file after file, so a shop can only move as many difficult loans as its most experienced people have hours for. The other loan officers wait for them, and so does the borrower.

The rules are already written down

Almost every round in that loop follows a published rule. Fannie Mae, Freddie Mac, FHA and VA each publish how every kind of income is counted, the debt-to-income limit for each product, how much can be borrowed against a home and what reserves a borrower needs. County loan limits are published, and so is the federal cap on points and fees. The findings report itself says, in words, what failed and by how much.

What the experienced person carries is how to apply all of that to one borrower, in the right order, and which change to try first. That knowledge is valuable, and it can be worked out in code, precisely, on every file, the same way each time. Nothing has done that before a loan goes to the AUS. So the loan is sent, it comes back, and the rounds begin.

A file that works itself

The software we are building starts where the loan starts, with the borrower’s documents. It reads every page, scans included, and works out the qualifying income under the rule that applies to each kind of income, with every figure tied to the page it came from.

From there it checks the loan against every published limit before anything is submitted: the ratios, the loan-to-value, the county limit, the reserves and the fees. Where something fails, it finds the smallest change that clears everything at once, because a change that fixes one limit can break another. Lowering the loan amount, paying off a debt, changing the term and moving to another program each cost the borrower something different, and the software weighs them. The borrower and the loan officer choose between loans that work, instead of finding out later which ones did not.

The real AUS still makes the decision. DU and LP judge risk in ways nobody publishes, and a loan is approved when they say so and not before. What changes is how the loan gets there. It is built to pass on the first submission, and when DU or LP does come back with something only it can judge, the software works that answer in seconds and prepares the next round, instead of leaving it in a queue.

For the shop, that means more loans reaching approval and closing with the same team. Every loan officer can take on the self-employed borrower, the rental income or the stacked debts that used to wait for one expert, and the people who know how to make a hard file work spend their days on the files that genuinely need them.

Where it lives

None of this asks a loan officer to learn a new screen. The work happens inside the systems a shop already runs, its loan origination system, its CRM and the channel its team already talks in, and the finished loan shows up there. It runs in the shop’s own cloud, or in a private copy we host for that shop alone, so borrower files stay with the shop.

Where this goes

Restructuring is the clearest case, but it is one of several moments where a loan waits for a senior person. The conditions an underwriter sends back are another: each one can be matched to the document that satisfies it, and whatever is missing asked of the borrower in plain words. A loan that is approved and then falls apart weeks later is another: a low appraisal, a rate move or a new car loan can be caught the day it happens, and the loan fixed again before it is lost.

Underneath, each of these is the same problem. The shop already has the documents, the rules and the systems. What it has not had is software that finishes the work an experienced person finishes by hand today, on every loan, before anyone has to wait. That is the work we have taken on.