The Headless LOS Has Arrived. The Lender Defines It Now.
A month ago, Blend launched Autopilot MCP. A server built on Model Context Protocol that gives any AI agent the lender authorizes secure, programmatic access to the full lending platform. Credit, underwriting, compliance, disclosures, closing. Not Blend’s agents. Any agent.
The week before that, Salesforce shipped Agentforce Operations. Back office agents, generally available. The launch leads with supply chain work, but one of the examples in Salesforce’s own announcement is a loan application moving through underwriting end-to-end. Extracting data from tax returns. Chasing signatures. Validating against compliance rules across systems.
A few months ago, I wrote that the LOS was reaching the end of life. That the architecture replacing it would be headless. The workflow is invisible, the database the command center, the AI the interface. I expected to spend two years defending that call.
Instead, two of the biggest platform vendors in the category shipped it.
Here’s what struck me when I read the announcements. The vendors are not announcing that they built the future. They are announcing that they will no longer be the ones defining it.
For two decades, the deal worked one way. The tech vendor wrote the workflow. The lender bought the workflow, then bent their operation around it. Every implementation project, every configuration workshop, every “that’s not how the system works” conversation was downstream of one assumption: the workflow ships with the platform.
I’ve started calling that assumption a vendor-authored workflow. It is baked so deeply into lending technology that most operators have never imagined the alternative. And as of this spring, it’s broken.
A few months ago, the question was whether the tech would ship. The tech shipped. The question now is who gets to define what the lending platform actually does.
Look at what actually changed, because it’s more than two press releases.
MCP, the protocol underneath all of this, went from roughly two million monthly SDK downloads at launch to 97 million by March. Sixteen months. Kubernetes took nearly four years to reach comparable deployment density. This is not an experiment developers are kicking around. It is infrastructure, already laid.
Meanwhile, the cost of running the old model keeps climbing. The MBA put production cost at $11,898 per loan in Q1. The long-term average is near $7,900. Margins are a sliver. The status quo isn’t a safe harbor anymore. It’s the expensive option.
The technical part of MCP is boring. The economic part is the story.
An LOS vendor historically controlled three things. The data model. The workflow. The interface. That bundle is what you were really paying for, and the workflow was the lock. Once your operation ran on the vendor’s stages and screens, leaving meant an eleven-month implementation and a seven-figure invoice.
When the platform accepts instructions from outside agents, two of those three things come unbundled. The workflow no longer has to be the vendor’s workflow. The interface no longer has to be the vendor’s screens. What the vendor keeps is the substrate. The data model. The system of record. The compliance rails, the audit trail, and the permissioning that decides which agent may touch which file. That is not a smaller business. It is a different one. In a regulated industry, it may be the more defensible one.
Clayton Christensen described this trap in The Innovator’s Dilemma. Incumbents respond rationally to disruption, and the rational response accelerates it. Blend, adding MCP is the right move. Not adding it would be worse. But the move that keeps them relevant is the same move that turns their workflow layer into a commodity. The vendors who win from here won’t be the ones selling workflow. They’ll be the ones selling the certainty underneath it.
Now flip to the lender’s side, because this is where it gets interesting.
Today, your underwriting workflow lives inside the LOS. Step by step, stage by stage. Configurable, not redesignable. Your operation is an annotation on the vendor’s flowchart.
With MCP, the workflow becomes something you author. An agent calls into the LOS for the file state. Into the bureau for the pull. Into the income verifier for the document. Into the AUS for the decision. The sequence, the exceptions, the escalation rules, the compliance posture: yours. Written by your team, changed by your team, in days instead of quarters.
The lender owns the orchestration. The vendors own the substrate.
And the substrate is not a consolation prize. An agent can author a workflow. It cannot manufacture what a regulator needs underneath it. Somebody has to guarantee where borrower data lives, keep the audit trail immutable, enforce which agent is allowed to decide what, and hold the orchestration rails steady while the agents on top change weekly. That is why it is still worth working with the FundMores, the Blends, and the Salesforces of the stack. You are no longer buying their workflow. You are buying the foundation your workflow stands on.
Carlota Perez, in Technological Revolutions and Financial Capital, splits every technology revolution into two phases. Installation, when the infrastructure gets built, and the money chases the technology itself. Deployment, when the infrastructure is assumed, and the value moves to whoever uses it best. Ninety-seven million downloads and two platform announcements in a single spring is what the end of installation looks like. Deployment is where operators win or lose.
Most lenders will miss this, and the reason is the frame.
The reflex when a vendor announces MCP support is to file it as another integration. Something for the IT roadmap, somewhere below the CRM migration. That frame is wrong. The platform just announced it will accept instructions from outside the platform. Which means the platform is no longer the operating model. You are.
Acting on that requires a competency most lending organizations never built. Workflow authorship. Agent orchestration. The discipline of designing your own operation instead of inheriting one. That is a different muscle than vendor management, and it doesn’t live in procurement.
The lenders who build it will ship operational changes in days, hold their underwriting logic as proprietary advantage, and stop paying rent on a workflow that was never really theirs. The lenders who don’t will keep adapting their operation to someone else’s flowchart, in the year the flowchart’s authors admitted it’s up for grabs.
A few months ago, I made a prediction about architecture. The LOS was reaching the end of its life, and something headless would replace it. The prediction held. The timeline didn’t. What I thought would take two years shipped in months. And the part I underweighted wasn’t the technology at all. It was the power shift.
MCP isn’t an integration story. It’s a sovereignty story. The agent is the workflow now. The platform is the substrate. And the lender, for the first time in two decades of mortgage technology, gets to write the operating system instead of buying it.
That is not a reason to walk away from your platform vendors. It is a reason to change what you buy from them. The workflow and the front end are yours now, adaptable in days. The compliance, the data integrity, and the orchestration rails are theirs to keep solid underneath you.
Stop renting your workflow. Keep paying for the rails. The difference between those two line items is the next decade of lending technology.
Chris Grimes is the founder of FundMore, an AI native loan origination platform. FundMore builds agentic mortgage and lending infrastructure for institutional clients across Canada and the US.