- Unblurred: AI & Mortgage
- Posts
- The BPO Model Isn't the Problem. The Work Is.
The BPO Model Isn't the Problem. The Work Is.
The mortgage industry offshored the work. Costs came down. The re-work stayed. Forty percent of mortgage operations still runs through BPOs, and that number has barely moved.
The BPO model made sense when the only other option was hiring. Build an onshore team, and your cost line scales with every rate cycle. Offshore it instead, and the margin gets better. The logic held up long enough to become standard practice.
So the industry outsourced. And the work kept moving: post-closing, conditions clearing, document validation, servicing pre-boarding, out the door, and into third-party operations centers. Less expensive per hour. Same number of hours.
That last part is the problem nobody talks about.
Re-work isn't a staffing problem
The same loan gets re-validated five or more times between close and the servicing platform. Post-closing reviews what the closing agent did. Warehouse reviews what post-closing did. The custodian reviews what the warehouse did. Servicing pre-boarding reviews the whole thing again before loading.
Same file. Same documents. Same loan. Different team. Every time.
This isn't a quality control failure. It's a structural feature of how mortgage operations is built. Data lives across multiple systems. Signed instruments are PDFs, not rows in a database. No system wins by default when there's a discrepancy. So a human decides. Then the next human decides again.
Offshoring that loop is cheaper. Eliminating it is a different outcome entirely.
A BPO doesn't change the loop. It runs the loop for less per hour. When the BPO can't resolve an exception, the work comes back upstream. When volume spikes, the BPO scales headcount. When volume drops, the problem shifts back. The cost is managed. It isn't removed.
What the numbers actually look like
The re-work pattern isn't abstract. It has a cost per loan - roughly fifteen hours of human labor and around $800 per loan in operational spend, distributed across internal teams and outsourced partners. Forty percent of that work, by current industry practice, runs through BPOs.
~15 hours of human work per loan, on average | ~$800 per loan in labor cost across the lifecycle | 40% of that work runs through BPOs today |
Offshore a portion of those fifteen hours, and the bill goes down. But the hours don't. The reviews still happen. Exceptions still escalate. Trailing documents still come back. The model absorbs the labor cost somewhere. It just moves where the invoice comes from.
The question the industry hasn't answered is what it would mean to not do the work at all.
Why this is a structural issue, not a vendor problem
Five conditions force manual reconciliation at every handoff in the mortgage lifecycle. Data lives in multiple systems: LOS, doc storage, custodial, servicing, investor platforms, and none of them is the canonical record on its own. The truth on closed terms is a signed PDF, not a field in a database. When systems disagree, there's no system that wins by default. Investor guidelines and policy overlays sit in PDFs and checklists. And every counterparty re-verifies the same loan against its own definition of complete.
Those five conditions don't go away when you move the headcount offshore. They go away when the work is autonomous: when a system can ingest the evidence, resolve the discrepancies, apply the guidelines, execute the controls, and certify the outcome without a human doing each step manually.
That's a different conversation than the one BPO procurement has been having. It's also the reason the forty percent number hasn't moved.
The conversation the industry is starting to have
COOs and heads of operations have been optimizing inside the BPO model for years. The vendors got cheaper. The contract terms got better. The SLAs tightened. And cost-per-loan still runs above where most operations teams want it to be.
The teams doing this work aren't inefficient. The model they're operating inside has a ceiling. Every rate cycle exposes it. Volume surges, headcount has to scale, BPO capacity gets stressed, quality slips, and exceptions compound. Then volume drops, the team contracts, and the cycle resets.
The organizations starting to break out of that pattern aren't doing it by finding a better BPO. They're asking what it would take to run the work autonomously - faster, more accurate, with no offshore dependency - and treating that as a cost structure question rather than a technology question.
That shift in framing is where the real conversation begins.
Alpha7X eliminates the manual work inside mortgage operations.
We don't assist teams with software. We do the work itself, inside your workflow.