Next week I’ll be at the Optimal Blue Summit representing Dark Matter. For me, it’s not just another summit. It brings me back to my first job in the mortgage industry.
Years ago, I was sitting on a lock desk at Norcom Mortgage, living inside our LOS and our pricing engine every single day. I wasn’t thinking about integrations from a technological perspective. I was thinking about them from an operational one. Could I trust the price? Did it write back correctly? Did the lock actually stick? If something failed, how long would it take to figure out why?
That’s when I first got deeply familiar with Optimal Blue. We implemented it as our pricing engine, and it became mission-critical almost immediately. Pricing and locking weren’t background tasks. They were the heartbeat of the secondary department. When the connection between the LOS and the pricing engine worked the way it was supposed to the day moved smoothly. When it didn’t, everything slowed down.
You don’t forget that kind of friction.
Fast forward to today, I’m working with the Empower LOS, a comprehensive lending platform that ties together the borrower journey, operational workflows, and secondary execution. I’m not locking loans anymore, but that lock desk mindset hasn’t left me. When we talk about integrations, I don’t think about them as feature checkboxes, I think about what happens when they break, lag, or require workarounds.
That’s why our integration with Optimal Blue matters to me personally.
Recently, I sat down with Lisa Ward, who leads our integration efforts between the Empower LOS and Optimal Blue, and asked her to walk me through where we stand. I didn’t want a marketing overview; I wanted to understand what’s happening under the hood. What she described is very different from the older hybrid models many of us remember.
This is a true API integration. Optimal Blue pulls the fields it needs directly through the pricing API. It isn’t passing through a layered service that requires multiple hops to get data from point A to point B. It isn’t relying on a patchwork of custom containers to compensate for missing write-backs. It’s a direct connection built for how Empower is structured.
That last part is important. Empower isn’t just a flat database. There are structural nuances, count fields, and workflow logic that make it different. Instead of forcing Empower into a generic connector model, Optimal Blue built a service specifically designed to work with it. That means data retrieval and write-backs are aligned to the way the system functions.
Lisa also walked me through something that would have saved a lot of headaches back in my lock desk days: error handling. In older hybrid models, if something failed, you often didn’t get meaningful feedback. You just noticed that pricing didn’t appear where it should have. Someone had to trace it manually. That ambiguity is what eats up time.
In the newer service, if a save-to-LOS or lock action fails, the user gets context. There’s visibility into what didn’t return and why. That might sound small on paper, but from an operational standpoint, clarity is everything. The difference between “it didn’t show up” and “this specific field failed due to an enumeration issue” is the difference between guessing and solving.
Another area we discussed was the transition away from hybrid altogether. Technology upgrades are rarely just technical projects. They require planning, training, procedure updates, and coordination with release cycles. Lisa was clear that while the new service is stronger, cleaner, and more resilient, moving clients thoughtfully matters just as much as the code itself. The goal isn’t just modernization. It’s stability during the transition.
What makes this integration unique isn’t just that both companies operate within the same broader portfolio. It’s that there’s real alignment in roadmap and architecture. The teams understand each other’s systems deeply. When you have that level of familiarity between a pricing engine and an LOS, you reduce the translation layer that often creates friction in the first place.
From my perspective, having lived on both sides of this equation, that alignment is powerful.
As a former secondary analyst, I know how critical clean pricing data is. As someone now working on the LOS side, I understand how fragile integrations can become when they rely on shortcuts or aging infrastructure. Bringing those two perspectives together changes how you think about building and maintaining these connections.
When pricing flows seamlessly into the LOS, when locks write back reliably, and when errors are transparent instead of mysterious, the entire origination process benefits. Loan officers move faster. Secondary works with more confidence. Operations teams spend less time reconciling and more time producing.
So, when I walk into the Optimal Blue Summit next week, I’m not just representing Dark Matter’s Empower; I’m representing a story that started years ago on a lock desk, staring at a pricing screen, hoping the data would land exactly where it was supposed to.
Today, I get to help shape the kind of integration I used to rely on, and that feels like a meaningful full circle.