Eric DeMatteis

Your processors shouldn't be re‑keying loans.

I connect your tools to your LOS, automate the busywork, and move your people onto the work that closes loans. It all runs in your own accounts, and your team learns to own it.

Book a 30-minute call See what's running

Built and running every day at a 16-state mortgage broker, on Arive.

Automation logTuesday morning
  1. Closing reminder sent to the team6 loans closing this week, open conditions and title contacts attached
    Sent
  2. Title review found a lien mismatchPayoff amount differs from the 1003 on a refinance
    Flagged for processor
  3. VOE filled out and emailedBuilt from the loan number alone, authorization form attached
    Done
  4. Appraisal filed to AriveValue and 120-day expiration set, document uploaded
    Done
  5. Wire expiring in 2 daysPost-closing board updated and the team alerted
    Needs attention
Example activity based on tools in production. No borrower data shown.

More than 35 of these automations run every business day at a mortgage broker licensed in 16 states.

I built them. Now I build them for other lenders.

What I build for lenders

Four kinds of work, all aimed at the same thing: fewer hands moving data between screens.

Connect your tools to your LOS

Arive, Microsoft 365, pricing, title, your warehouse bank, accounting, email marketing. Data moves between them on its own, so nobody copies it by hand.

ExampleClosing disclosures are merged, matched to the right loan, and uploaded to Arive, without logging in to the doc vendor.

Automate the workflows that eat the day

The same twenty steps, done the same way on every file, are exactly what software should do. Your team just checks the result.

ExampleA verification-of-employment form filled out from the Arive loan number and emailed to the processor with the authorization attached.

Reposition your people

When the re-keying is gone, processors review flags and talk to borrowers. Nobody's job should be moving data from one screen to another.

ExampleTitle and insurance review reads every document and flags only what doesn't match the file.

Build what your vendors don't sell

A pricing engine on your website. A post-closing board for wires and expirations. The dashboard your LOS doesn't have. If you keep a spreadsheet to track it, it can be a tool.

ExampleA live pipeline dashboard refreshed every 10 minutes, without paying for Power BI.

Your LOS in the middle. Everything else plugged in.

Most lenders run a dozen systems that don't talk to each other. People fill the gaps. I close them.

  • Built on your LOS's own API wherever it has one
  • Secure automated sign-in where the API stops
  • No tools that depend on someone logging in every morning
Microsoft 365email, Teams, files Website pricingyour rate sheets Title & insurancereview and upload Warehouse bankwires, funding Accountinginvoices, entries Email marketingpast clients, partners Creditliabilities, reports Investorslocks, purchase advice Your LOSArive, and others

A processor's morning, before and after

Same people, same pipeline. Different work.

Before

  • Re-typing employment details into a VOE form
  • Dragging documents into the LOS one at a time
  • Reading every title commitment and insurance policy line by line
  • Checking a spreadsheet for expiring locks, credit, and wires
  • Writing the same follow-up email for the tenth time

After

  • Reviewing a short list of flagged items
  • Documents already filed to the right loan
  • Only the mismatches, with the page they came from
  • An alert before anything expires
  • Follow-up drafts waiting, sent only when a person clicks send

Nothing sends or changes a loan without the rules your team sets. People stay in charge. The tools do the typing.

How working together goes

A three-month start, then you decide how much help you want.

1

Set up in your accounts

Weeks 1–2

A secure automation server in your Azure account, connected to your LOS and Microsoft 365. You own every login and every line of code.

2

Build your first tools

Months 1–2

We start with what costs you the most time. Pricing, post-closing, and file review are the usual first picks.

3

Hand it to your team

Month 3

Weekly training with someone on your staff, so they can change, fix, and build tools after I step back.

You own everythingServers, code, accounts, and data live in your accounts from day one.
Borrower data stays homeNothing is copied out of your Microsoft and Azure environment.
Least accessA named account with MFA, admin rights only during setup, every grant logged.
Built by an operatorI run the same tools on a real pipeline, so I know where they break.

Tell me what your team re‑keys every day.

In 30 minutes I'll tell you what can be automated, what can't, and what I'd build first.

Book a 30-minute call