Back to Insights
EssayLinkedIn

April 6, 2026

Build vs. Buy: The Path Forward

By Suha Beidas Zehl, CMB®, AMSP™

Cover image for the article Build vs. Buy: The Path Forward

Every technology decision a mortgage company makes is really a business decision in disguise. The question of whether to build a solution internally or buy one from a vendor is no different. It feels like a technology conversation. It is not. It is a conversation about strategy, resources, risk, and the kind of company you are trying to become.

The mortgage industry has never faced more pressure to modernize. Borrower expectations are rising. Margins are thin. Regulators are watching. And the vendor landscape is more crowded and complex than ever before. AI-powered tools, automation platforms, and digital lending ecosystems have created both opportunity and noise. In that environment, the build vs. buy decision has become one of the most consequential choices a mortgage leader can make.

Before you can choose a path, you need to be honest about where you are. Most mortgage companies sit in the middle of the tech modernization arc, having made a series of incremental technology decisions over the years that now feel disconnected and hard to scale.

The build vs. buy question usually surfaces at one of three moments:

when existing systems are breaking under volume or compliance pressure when a competitor appears to be pulling ahead when a new capability becomes available that leadership wants to evaluate

Each of those moments carries its own urgency and its own biases. Recognizing the context matters before the analysis begins.

Now, before you evaluate any solution, define the problem you are actually solving. Not the symptom. The root cause.

The build vs. buy question looks different in the context of artificial intelligence, and mortgage leaders need to understand those differences.

AI-powered mortgage technology is moving fast. New capabilities are emerging faster than most organizations can evaluate them. That pace creates pressure to act quickly, which is exactly when disciplined decision-making matters most.

For most mortgage companies, buying true AI capability from established vendors is the more pragmatic path. Building large language models or machine learning infrastructure from scratch requires talent, compute resources, and data infrastructure that few independent mortgage banks or community institutions have.

But buying AI is not simply buying software. AI systems require governance. They require transparency about how decisions are made, particularly in credit and underwriting contexts where fair lending obligations apply. They require ongoing monitoring for model drift, bias, and performance degradation.

Before you buy any AI solution, understand what the model was trained on. Understand how explainability is handled. Understand what your regulatory posture and risk appetite looks like if a decision is challenged. And build the internal capability to ask those questions intelligently, whether or not you have a data science team (most IMBs do not, by the way).

Build vs. buy is a strategy question disguised as a technology conversation. The right answer depends on your organization’s capabilities, your competitive position, your resource reality, and the specific problem you are trying to solve.

There is no universally correct path. There is only the path that is right for your organization at this moment, executed with discipline and supported with the change management infrastructure that makes the investment actually "real".

The organizations getting this right are not the ones with the biggest technology budgets. They are the ones that take the time to understand the problem deeply, evaluate options honestly, make decisions based on evidence rather than enthusiasm, and invest in their people as seriously as they invest in their platforms.

There is a case for building. There is also a case for buying. The build vs. buy decision is not one conversation. It is a structured process. Organizations that treat it as a single executive discussion consistently make worse decisions than those that work through a disciplined framework. It’s a framework I walk all my clients through; and if you’d like to receive my white paper that describes both cases, along with the pros and the pitfalls, and provides the framework behind this, please let me know in the comments.

The timing triggers you mentioned are spot on, and they all share one thing in common: they push teams toward reactive decisions. I’ve watched companies pick vendors during a compliance panic and end up with tools that solve last quarter’s problem but create new bottlenecks six months later.

Suha, this is such a critical point for mortgage tech! Beyond cost, what’s the most overlooked intangible consequence of a bad build vs. buy decision? 🤔 #Mortgage #Strategy

Great coverage. Most of the time this isn’t really a technology decision. It’s a question of focus and advantage. Where do you want to be differentiated? And where are you better off leveraging something that already exists? What I’ve seen work well is being very intentional about that line. Build around what is core to your business and your strategy. Buy where speed, scale, and specialization matter more than ownership. Especially with AI, the bar for building is high, not just technically, but operationally and from a governance standpoint. And that part often gets underestimated. At the end of the day, the decision only pays off if it actually shows up in how the organization works. Otherwise, you just end up with more complexity layered onto the same process.

This article series opened with a pattern I kept seeing in different forms. The budget was approved.

My Dad loves to watch news in the morning. Today was no different.

Putting This Into Practice

This is the work I do with lenders, banks, and credit unions. If your organization is working through these questions, these pages explain how I help.