Workflow Orchestration for Mortgages

Diving deeper into

Mike Yu, CEO of Vesta, on building a new system of record for the mortgage industry

Interview
Instead of having one human do the process, we're going to have five humans independently do the process.
Analyzed 5 sources

The core problem in mortgage ops is that lenders buy safety by paying multiple people to recheck the same file. A processor gathers pay stubs, bank statements, tax returns, and disclosures, then an underwriter checks the same package again, then closing and post close QC often repeat the review. That redundancy exists because mortgage rules are hard to translate from common sense, and because secondary market standards from Fannie Mae and Freddie Mac punish avoidable defects, so every handoff becomes another manual control point.

  • This is exactly the workflow Vesta is trying to replace. Rather than assign one person a whole loan file, it breaks the loan into smaller tasks and rules, then software routes each step, tracks what is already done, and prevents later teams from redoing the same checks out of habit.
  • The comparison is old LOS platforms like ICE Mortgage Technology's Encompass versus newer workflow first systems. Incumbents are broad systems of record, but the process still relies heavily on humans inspecting files. Agency tools like Fannie Mae Desktop Underwriter and Freddie Mac Loan Product Advisor automate eligibility checks, yet lenders still need internal teams to assemble documents and clear exceptions.
  • The economic implication is simple. If one loan gets touched five or six times, labor cost compounds and cycle times stretch. That is why mortgage tech startups have often focused on one slice, like pricing, frontend application flow, or closing, while the biggest prize is the workflow layer in the middle where duplicate work actually happens.

The next step for mortgage software is moving from digital filing cabinets to true task orchestration. As lenders connect automated underwriting, document verification, pricing, and closing tools into one workflow, the winners will be the systems that can prove a check was completed once, carry that result through the file, and remove whole layers of human rework.