A mortgage servicing company managing a large portfolio of loans for institutional investors built its own servicing and workout platform under our founder, then the company’s technology chief, in the years before and during a housing downturn. The platform did two things its competitors’ systems could not: work out troubled loans at scale, and prove it to the investors who decided where the next portfolio went. Over the measurement window the meter read $120M in attributed revenue on roughly $20M all-in, a 500% ROI.
This is the oldest story on our impact page, and the one that shaped our framework most. It is the reason we say technology strategy cannot stop at keeping the lights on and the hackers away.
The Situation
Servicing is a volume business with thin margins and unforgiving customers on both ends: borrowers who call when something has gone wrong, and investors who measure a servicer on what it recovers. The company had built a reputation for working harder on troubled loans than the industry norm, and that reputation lived in its people and its phones. The systems underneath were the industry’s standard platforms, which were built for the steady state of collecting payments and had no answer for a year in which a large share of the portfolio needed a workout at once.
When the downturn arrived, the companies that could modify loans quickly, document every decision, and report outcomes to investors kept their portfolios and were handed more. The companies that could not were losing both.
Deciding How to Measure Impact Before Creating It
The yardsticks were set with the executive team and the company’s principal investors before the platform was funded. Revenue would be attributed to the platform on two bases: fees and incentives earned on workouts the platform processed that the prior systems could not have handled at that volume, and servicing revenue on portfolios awarded where the platform was named by the investor as a reason for the award. Costs were counted all-in: development, infrastructure, licensing, and the team.
The Work
- A workout engine. Proprietary decisioning and workflow for loan modifications and other workouts, built so that a specialist could resolve a case in a fraction of the time the standard platforms allowed, with every step documented. [NEEDS JEFF’S INPUT: the core capability in your words]
- Borrower contact at scale. Dialer, correspondence, and case management integrated with the engine, so that outreach, offer, and acceptance ran as one process instead of three.
- Investor reporting. Outcome reporting built for the investors’ questions rather than the regulators’ minimums, which turned the platform from an internal tool into a sales argument.
- A development team that owned it. The software team our founder had built over the preceding decade owned the platform end to end, which is why it could change as fast as the market did.
The Results
Over the measurement window:
- $120M in attributed revenue, from workout fees and incentives and from servicing revenue on portfolios awarded with the platform cited as a reason.
- Total investment: roughly $20M all-in, inclusive of development, infrastructure, and the team over the build and the measurement window.
Net return: 500% ROI over the measurement window.
Per our client confidentiality policy, the client is not named and certain figures are rounded.
From Cost Center to the Reason Clients Sign
The number worth dwelling on is not the ROI; it is that the second revenue basis existed at all. A servicer’s technology is supposed to be invisible to the investor. Here it became the thing investors asked about, and the thing that won portfolios. That is the Monetize tier of our Innovate Beyond Efficiency® framework in its earliest form, years before we gave it a name: IT built well enough that it stops being a cost of doing business and starts being the business’s argument for itself.
The pattern has repeated in every industry we have worked in since. The platform that lets a company do the hard thing faster than its competitors is also the platform that lets its salespeople say so.
What We’d Do Differently
The platform was built for the company’s own operation first and for the investors second, and the investor-facing reporting trailed the workout capability. The workouts were real from the first release; the ability to prove them to the people awarding portfolios came later. Were we starting again, the outcome reporting would ship with the first release, even in a plain form, because as we learned: the proof is the part of the product that enables the advance. The lesson generalizes: when technology is going to be a reason clients choose you, build the evidence alongside the capability, not after it.
