/* With JS off, a prerendered page reads in full, so the fallback below is only for a shell with nothing in #root, on its own readable paper. */ body:has(#root > *) noscript > div { display: none; } body:has(#root:empty) { background: #F4F3EF !important; }

Proxara mortgage LOs

The loan officer's assistant, for mortgage lenders and broker shops.

Overview, How it works, Questions
Security, Company, Blog, Trust Center

The full site needs JavaScript. A plain-text description is at /llms.txt.

Skip to content

Proxara for lenders

Proxara Technologies

The work behind every loan.

Why we build this.

Behind every loan is work done by hand: what a borrower said, typed into the loan system; papers asked for, chased and checked against each other; the record of what happened, and when.

We build the software that does that work on every loan, inside the systems a company already runs, and asks people only what is theirs to decide.

How we build it.

Finished work, not another tool
The work is done in the loan and in the channel the team already uses. Nobody learns a new screen to get it.
The model reads. Code decides.
A model reads what was said or written and points at the words. Code checks every figure against them and decides what goes where, so the same input gives the same answer.
The customer’s, not ours
Borrower data does the customer’s work and nothing else, and no model is ever trained on it.

Where it goes next.

Every loan, from the borrower’s first call to closing. The work is done in the systems each company already runs, and its people keep the conversations only they can have.

Meet the team

Founders

Jex PearceFounder
Hemanth TadepalliFounder

Reach us

From the blog

The rerun loop: from a Refer to an approvable structureHow the findings are read, every lever is tried, and the next structure comes back as fields, round after round, until the loan passes.Read more Why the qualifying income is code, and never a model’s answerOne model reads the documents. Code computes the income. Where that line sits, and why every figure can be checked in the time it takes to read it.Read more What stays in your tenant, and what is deletedWhere the model runs, what it keeps while a loan is worked, and what is left when the work is done.Read more Reading a findings report the way the specialist doesEvery message on a DU or LPA report, what kind of issue it is, and which ones have a threshold to clear.Read more One installer, run by your ITWhat the installer checks before it creates anything, what it creates, and how an update arrives without anyone holding access.Read more Why we build thisThe moments a loan waits for a senior person, and what changes when those moments are worked out in code.Read more

WalkthroughHow it worksOne call, from the agent’s text to DU’s answer.See how it works ArchitectureSecurityWhat’s heard, what’s kept, and where it runs.Read the architecture

Talk to the people building it.

Tell us what you run and where files wait today. A person reads every message and replies.

Or write to jex@proxara.ai.