Eric DeMatteis
Ruled entries in a merchant's handwritten ledger, September 1833

Most of the software a mortgage company pays for by the seat can now be rebuilt inside the Microsoft or Google tenant it already owns, by the people who use it, in weeks. I have done it across underwriting, processing, post-closing and marketing. Here is how, and what carries over to your company.

Stop renting what you can own.

Why build instead of buy

Three things changed in the last two years. Together they end the case for most per-seat software in a mortgage company.

  1. The reading is solved.

    Document OCR from Microsoft or Google plus a tested set of instructions reads a condo budget, a title commitment or a bank statement the way your best underwriter does, every time, at seven in the morning. The instructions are the product, and they are tuned on your files.

  2. The platform is already paid for.

    Microsoft 365 or Google Workspace, the cloud account that comes with it, and your LOS's API are the whole stack. Nothing new to license, no new vendor holding your borrowers' documents, and every login belongs to you.

  3. The build is weeks.

    With the readers and the LOS connection tested, a new workflow is a conversation with the person who does it today and about a week of building. Then they correct it by forwarding an email.

Ten days to replace a marketing platform

The last subscription the company dropped was a marketing automation platform it had rented for years: the lists, the email templates, the landing pages and forms, and the programs that write to borrowers after closing. We rebuilt the parts that were actually used inside the company's own dashboard, on the company's own Azure.

The new side ran beside the old one until every list, every segment and every program step matched record for record. Nothing sent from the new side until it did. Then the renewal lapsed, and the rebuild kept growing into the CRM the company never had.

Marketing platform rebuild

From the build log, October 2026

Automated programs rebuilt22 · 622 steps
Email templates carried over119
Landing pages and forms52 · 58
Contacts moved, every row matched34,717
Sends from the new side before it matched0
From first look to parity10 days
Per-seat licence after cutoverNone

The vendor is not named here. What was left behind on purpose: the features nobody in the company had opened in a year.

The card that wraps the LOS

Your LOS keeps the record. It was never built to run a processor's day, so a card on your own dashboard does: one per loan, laid out the way your team asked, and it writes back.

Rivera · 1024-0471
PurchaseCONVCloses 11/14 · 16d
Lane Submitted to UWApproved with conditions · 2 of 7 cleared

Press a tracker to read what the hover would say.

Nothing sent

Built for lenders and brokers, so far

Every tool below runs every business day for a mortgage company's own desks. None was bought. Each was shaped by the person who used to do the work by hand, and corrected by them as it ran.

Reads the documents

Each one read by Microsoft's or Google's OCR, checked by a tested prompt against the loan, filed to the loan, and told to the right inbox.

Condo project review

Oakmont Commons · 57 units · Full Review

Master policy now Actual Cash Value
Declarations page, effective 8/1
Reserves 16.4% of budget
Clears 15%, LL-2026-03
Clear
Delinquent dues 6.9%Clear
Eligible with conditions3 follow-ups
Condo project reviewQuestionnaire, budget, financials, reserve study, master policy, minutes. A disposition with the guideline cited and the questions for the HOA.Underwriting
Title commitmentNames, vesting, address, liens and the payoff lender against the 1003. Mismatches first, on one page.Processing
Purchase contractDates, credits, who pays the commission, every agent's contact block ready to paste.Processing
Homeowner's insurancePremium, coverage, deductible and mortgagee clause from the declarations page, checked against the loan.Processing
Bank statement incomeTwelve or twenty-four months of deposits, transfers matched and excluded, large deposits queued for a decision.Underwriting
Asset depletion incomeEvery asset account from the LOS, priced across each investor's program side by side before the file is submitted.Loan officers
Appraisal and 1004DSorted, checked against the loan, uploaded; the value watched for the high and the low.Processing
Purchase advice, nine investorsFrom email and from portals. Figures entered in the LOS, the PDF filed, any mismatch flagged to the dollar.Post-closing
Investor conditionsPulled from the investor's portal into the LOS, with the request to the borrower drafted for the processor.Processing
Any fillable formA form the tool has never seen: fields mapped from the loan, filled, sent for signature. VOEs go out with the authorization attached.Processing

Wraps the LOS

The LOS keeps the record. A card on your own dashboard keeps the day, and writes back.

Conditions · Rivera

Approved with conditions · 2 of 7 cleared

Updated insurance binder
Requested 10/27 · LOS updated 10/27
Requested
Signed 4506-C
Sent for signature 10/26
Sent
Gift letter and transfer
Cleared 10/25
Cleared
Payoff lender name on title
Cleared 10/22
Cleared
Trackers on the card faceCommitment, insurance, title, appraisal, payoff, lock, closing disclosure, walkthrough. Green, yellow or red by limits your team sets; hover reads the due date.Processing
Emails from the cardClear to close, lock extension, final loan structure: drafted in the processor's own Outlook or Gmail, addressed to the right desk, with the lender's loan number in the subject.Processing
Conditions write backMark a condition requested, sent or cleared on the card and the LOS is updated for you.Processing
Documents dropped on the cardLand in the loan's SharePoint or Drive folder, named, with no upload screen.Processing
Dates that follow the LOSA lock date typed on the card follows the LOS when the LOS changes. No card says EXPIRED after an extension.Processing
Handoff that holdsThe file cannot move to the next desk until each person's questions are answered or marked not applicable.Sales and processing
The 9 AM pictureThe whole pipeline, as a picture, in every inbox before the first meeting.Owner

Watches the money

Boards that replace the spreadsheet someone used to refresh by hand.

Wires and expirations

Refreshed every 10 minutes · 7:40

LoanReceived
1024-0463 Okafor$412,900.00Purchased
1024-0471 Rivera$366,629.64+$412.50
1024-0480 Mbeki—Lock 11/02
Wires and expirationsOne board, refreshed every ten minutes, from the LOS and the investors' notices.Post-closing
Non-delegated closings and warehouse linesWhich loan is on which line, what has been purchased, what is still owed.Post-closing
Title and appraisal ordersFrom the vendors' own APIs onto one board, with the digest emailed each morning.Processing
Locks, credit and documents expiringA note before anything expires, not a spreadsheet to check.Processing
Invoices and journal entriesCreated in QuickBooks at broker check, one per loan purchased, with the margin posted.Accounting
Receipts and shippingReceipts read from the mailbox into the books; shipping labels made from the file.Accounting

Writes for people

Drafts, never sends. The person reads it and presses the button.

Clear to Close 7781234 RIVERA, Ana Purchase NJTo the title company and both agents · CC the loan officer
Hi all, the Rivera file is clear to close. Closing is set for 11/14; the final CD goes out today. Anything still needed from your side, let me know.
Waiting in the processor's DraftsNot sent
Follow-ups in Outlook or GmailDrafted in the officer's own voice from the file and the notes, waiting in Drafts.Loan officers
Intro email to a new prospectThe moment the lead arrives, from the officer's mailbox.Loan officers
Preapproval letters and packagesLetter and findings in one click from the file.Loan officers
Call notesFormatted into the template while the agent is still on the line.Loan officers
Bulk notes to the LOSA list in, a note on every loan out.Processing

Markets

The rebuilt platform, now the company's own.

Lists and segmentsEvery contact, every funded loan, segmented the way the old platform did it and checked against it.Marketing
Templates, landing pages, formsWith one signature per loan officer, a block editor for new ones, and event pages that copy their own form.Marketing
Automated programsPost-closing, anniversaries, rate drops, events: the same schedules and branches, sending from the company's own Azure.Marketing
Rate watch on funded loansBorrowers whose rate is above today's market, listed with the savings, for the officer to call.Loan officers
Newsletter and website pricingThe newsletter built and sent; the website's rate engine fed from the company's own pricing.Marketing

Knows the guidelines

So the readers can cite the rule, and so can your people.

Guideline harvesterEvery lender's current guide, pulled from their portals nightly and replaced in place.Underwriting
Guideline assistantAsk one question across every lender's guide and get the answer with the page cited.Underwriting and sales

Keeps itself running

The part nobody sees until it is missing.

Watchdogs and healthWhat ran, what failed and why, in one morning email. The browser sessions, the disk, the mailbox, all kept tidy.Owner
Corrections by emailForward any result with a note. The fix goes to the root of the tool, not to a ticket.Every desk

37 tools · interface and loan details on this page are made up; no borrower data is shown.

Tested once. Shaped to you.

Already tested, comes with me

Shaped by your desk

Every lender's process is different. That is the point of building instead of buying: the tool bends to the desk, not the desk to the tool.

Let’s build what works for you

I am not selling these tools. Every one of them was shaped by the desk it sits on, and yours will be too. What I bring is the parts that are already tested, and a way of working: your team says what it would stop doing, the first tool runs on real files inside a week, they correct it by email, and it is theirs.

Three ways this can go

With your people For you Over the fence

I sit in your ops meeting. We build the first tool together, from your team's list, in your own cloud account. Your people learn the loop and keep building after I leave.

Your list, my build, your accounts. Each tool is run by your own staff on real files and corrected by email as it goes. The code, the logins and the documentation are yours from the first day.

An afternoon through everything on this page: the code, the prompts, what broke and what fixed it. Your IT builds. I answer the phone.

Whichever way, it starts the same: a secure automation server in your Azure or Google Cloud account, connected to your LOS and to Microsoft 365 or Google Workspace, in the first two weeks. You own every login and every line of code from then on.

A 30-minute call

Pull up two lists: the software your company pays for by the seat, and the work your team still does by hand. Bring both and in 30 minutes we go through them: what you could stop paying for, what you could stop doing, and what I would build first.

[email protected]
New Jersey, working with lenders anywhere in the US.