Looking for a mortgage? royalmtg.com · Looking for the app? royalai.ai
Correspondent · capital · embedded
Counterparties who want to know what a file from here looks like. Capital that wants to know where the value sits. Builders, agents and platforms who want this intake running under their own name. Each one is below, in that order, and none of them is a pitch deck.
01 · Correspondent & warehouse
You are not taking a view on whether AI works in mortgage. You are taking a view on a licensed originator whose intake produces unusually complete files and whose decisions are signed by a person.
Borrowers come through one door and only one. Every Royal surface — the lender site, the consumer app, the builder and agent portals — points at the same intake. There is no second funnel quietly producing files under a different standard, because duplicate funnels were removed rather than maintained.
Data quality problems in this industry are overwhelmingly intake problems. A form takes whatever a tired person types at eleven at night. A structured interview asks in the right order, fills what it can find itself, and catches the self-employment answer on the way past instead of at the closing table.
Every decision that leaves this building has been reviewed and signed by a Royal Mortgage underwriter. Not sampled. Not audited after the fact. That is the answer to the question your credit committee is going to ask first.
The direction of travel is correspondent. We are building the file quality, the controls and the audited financial picture that relationship requires, in that order, and we would rather have this conversation early with people who will tell us what is missing than arrive with a finished application and a surprise.
The most useful thing a counterparty can do at this stage is name the condition that will fail before we build around the assumption that it will not. We would rather redesign a layer now than discover it in a purchase review.
02 · The file
The difference is not cosmetic and it is not a reporting layer bolted on top. It is what the intake was built to produce.
| On the file | Typical intake | This intake |
|---|---|---|
| Borrower answers | Final field values | Values plus the exchange that produced each one |
| Question order | Whatever the screen layout was | A governed order, versioned, with the branch recorded |
| Fee and cost disclosure | A form handed over because the rule says so | Every line explained in plain language at the moment it appears, so the borrower knows what is a fee, what is their own prepaid bill and what is set by statute |
| Self-employment | Often surfaces at document collection | Caught inside the first four minutes and forked immediately |
| Property portfolio | Stalls the application or gets skipped | Diverted to per-property capture without stopping the clock |
| Corrections | Overwrite silently | First-class events. The reversal is on the record. |
| Abandonment | An empty row | The exact question the file stopped on |
| Decision | Varies by shop | Human underwriter signature on every one |
The left column is a generalization about the category, not a claim about any particular lender or system.
03 · Capital & investors
This page describes a business. It is not an offer, a solicitation or a projection, and there are no numbers on it that we would not want read back to us in two years.
Not the interface, not the model, not the brand. A first-party structured record of how real borrowers answered real application questions, in order, at a licensed lender. It cannot be scraped, licensed or bought, and it gets denser with every file.
Owning the license is what makes the record possible. A pure software company cannot originate, so it cannot generate this data at all — it can only sell tools to the people who can. We are on the other side of that line on purpose.
Time to a real answer is the only advantage in this industry that a competitor cannot simply price against. Human underwriting on every decision is what keeps that speed defensible when somebody with authority starts asking questions.
The honest version of the risk. This only works if borrowers will actually talk to software about their money, and if the record that produces stays ours and stays secure. We think the first is already settled by how people use assistants everywhere else in their lives. The second is treated as the largest engineering commitment in the company, and it is the first thing we open in a walkthrough with anyone writing a check.
04 · Embedded & partner lenders
Builders, real estate brokerages, platforms and lenders who want the interview in front of their own customers rather than sending them somewhere else and hoping.
A builder's worst week is the one where a signed buyer turns out not to qualify. The intake in front of the buyer at the model home turns that into a four-minute answer instead of a three-week discovery.
The single sentence this platform exists to eliminate is a buyer making an offer without knowing whether they can close it. That is an agent's problem as much as a lender's, and it is solvable at the point of interest.
If your origination is fine and your intake is the bottleneck, the intake is the piece worth talking about. It is the layer we built and the layer we would put in front of your borrowers.
The platform's job in the pricing layer is to put real options in front of a borrower side by side and let them choose. It does not decide which lender should win, and the architecture is built so that it cannot start doing so quietly later. That neutrality is not a policy paragraph that could be revised in a meeting. It is a property of how the layer is built.
05 · Diligence
Nothing below requires a meeting to explain. Ask for any of it.
| Item | Where it is | How to get it |
|---|---|---|
| Licensing and entity record | Public | nmlsconsumeraccess.org, NMLS #2059962 |
| The intake, running | Public | The exhibit, or live in a walkthrough |
| The architecture | Public | The platform page, layer by layer |
| The record schema | On request | Opened field by field in a walkthrough |
| Data handling and security model | On request | Walkthrough, then written follow-up |
| Systems behind the bought layers | On request | Named in a walkthrough, not on a public page |
| Financial and audit position | Direct | Bryan Royal, under the appropriate agreement |
Ask it
Say which of the three you are, and the session is built around that one instead of covering all of them badly.