I've spent 20+ years in consumer credit. I've seen a lot change. But one thing that always struck me was how fragmented the lending world remained. Retailers with multiple lenders had to juggle multiple logins, no transparency on data, and completely inconsistent user experiences. It was chaotic. That's why we built Stax. A broker platform that aggregates multiple lenders into one unified experience for retailers. It took 9 months to get an MVP in front of users. Another 6 months to full rollout. Now we process over £300m annually. But the real story isn't just the numbers. It's what we learned about why lender aggregation matters and how to do it properly.
The Problem We Solved
Let me paint you a picture of what life looked like before Stax. A typical retailer working with three lenders would have:
- Three separate logins
- Three different platforms
- Three different user interfaces The sales staff at Branch A might process Lender X first, then Y, then Z. Branch B down the road? They'd do it Z, X, Y. No consistency. No strategy. Just whatever the branch manager happened to prefer. A customer walks in, wants finance for a kitchen. The salesperson enters their details into Lender X's portal. Declined. Opens Lender Y's portal. Enters everything again. Declined. Opens Lender Z. Same data, third time. Finally approved. Three data entries. Three separate systems. Three sets of compliance obligations. And all the data? Siloed. The retailer has no single view of their lending performance. The customer has had a frustrating experience. Nobody wins except the lenders who got to keep their walled gardens. From a lender's perspective, you were fighting for shelf space against competitors on the same fragmented platform. There was no way to differentiate your product, no way to control your credit strategy, no way to ensure consistency across different points of sale. Aggregation changed that. But only if you built it right from the start.
What Stax Actually Fixed
With Stax, that same retailer has:
- One login
- One data entry
- One consistent credit strategy across every branch Customer details go in once. The waterfall kicks in. Lender X declines? Automatically moves to Lender Y. Still no? Lender Z. The customer never re-enters anything. The salesperson never juggles portals. And the waterfall order? That's configured centrally based on actual strategy, not branch manager preference. Prime customers might go to the lender with the best rates first. Sub-prime customers might go to a specialist lender. The retailer decides the strategy. Every branch executes it identically. All the data sits in one place. One dashboard. One set of reports. One compliance framework. That's not a nice-to-have. That's the difference between a business that can scale and one that's held hostage by fragmentation.
The Consulting Firm Lesson
I'll be honest about what we got wrong. When we commissioned Stax, we went with a major consulting firm. A solid company. Big name. Lots of capability on paper. The pitch was impressive. A charismatic partner walked us through their vision. Decades of financial services experience. Global delivery capability. Enterprise-grade everything. Then the work started. The partner disappeared. The work got delegated to junior developers offshore. The "thought leadership" we were paying premium rates for never materialised. The discovery sessions that were supposed to be collaborative became documentation exercises that got set in stone. Any change request? Expensive. Slow. Fought for. We spent a SIGNIFICANT amount of money before we realised what should have been obvious: a small, senior team would have delivered better work faster and cheaper. At that point, it's too late. They recommended we chose Salesforce as the backend. Solid company. But not ideal for a lending platform front end. We've since been working to move away from that. They also chose Mulesoft as our initial integration layer. Again, solid product. But when we moved to AWS last year with a boutique firm, they accomplished in weeks what Mulesoft required months to do. At a fraction of the cost and several magnitudes better in terms of scalability. Would I use a big consulting firm again? No. Not for core platform development. They built Stax from scratch, which was valuable. But once you have a direction, once you have requirements, once you know what you're building, you want smaller, more specialised teams. We recently did our AWS migration. A boutique firm handled it. The outcomes were dramatically better.
Why Aggregation Actually Matters
The value of lender aggregation isn't just convenience. It's strategic control. When you aggregate multiple lenders behind a single platform, you can finally orchestrate credit strategy properly. You're not at the mercy of individual lender portals. You're not hoping your staff remember to check all three systems. You're not praying the data matches up when you try to run reports. For retailers, that meant:
- One login
- One data source
- One consistent experience across every lender For lenders, it meant we could finally offer something fragmented approaches couldn't: predictable, consistent execution of their credit products across hundreds of points of sale.
The Two Architectural Decisions I'm Most Proud Of
First: Waterfall Configurability
We built the system so that a retailer could lock-in their entire credit strategy at the point of sale. Not across the whole retailer. At the individual product level. By price bracket. By deposit level. By product vertical. Even by branch if they wanted. A retailer sells windows and doors. They might want different credit strategies for each. They might want different credit strategies for different price points on windows. Stax let them configure all of that ensuring consistency and compliance. It's granular. It's powerful. And it's only possible because we designed Stax to support it from day one.
Second: Mandatory Training Triggers
We built a system where users cannot propose an application until they've completed mandatory regulatory training. That gave us 100% certainty that every single user who was using Stax had been trained. No exceptions. No shortcuts. No blame-shifting between retailers and lenders when something goes wrong. Training is reissued every 10 months. Users get 4 weeks to complete it or they are blocked from proposing new apps until it's complete. It sounds simple. It's not. It protects everyone: lender, retailer, consumer and us.
The Landscape Has Changed
The loan origination software market is growing at 14.8% annually. The market was worth $6.06 billion in 2025 and is expected to hit $24.11 billion by 2035. Everyone's moving to the cloud. Everyone's realising that monolithic systems don't work anymore. In the UK specifically, our open banking ecosystem has matured faster than anywhere else in the world. By 2025, there were 24 billion successful API calls in the UK's open banking system. That's up 27% from the year before. The infrastructure exists. The question is whether you're using it properly. What still surprises me is how many lenders aren't there yet. Still building in-house proprietary systems. Still making retailers jump through hoops to integrate. Still operating like it's 2010. Still using external 3rd parties to create platforms they don't understand.
The Real Shift
Building a lender aggregation platform is both a technical decision and a cultural one. It means committing to transparency. Your data model has to be consistent. Your error messages have to be helpful. You can't hide behind a UI and inconsistency. Everything is exposed. It means committing to configurability. You can't hard-code business rules. Everything has to be parametrised. That's only possible if your system is built for it. It means committing to support. Your support team has to understand the platform deeply. It can't just be a Help Desk team responding to form submissions. Most of those things take more effort upfront. All of them pay dividends over time.
What Stax Proved
I won't tell you building a lender aggregation platform is easy. It's complex. It requires discipline. It requires saying no to features that don't support the core model. It requires thinking five years ahead about how you want the platform to evolve. But I will tell you it works. Processing £300m annually. 250 retailers who no longer juggle multiple logins. 220,000+ customers who enter their details once instead of three times. Credit strategies that execute consistently instead of varying by branch manager mood. The fragmented world we started with? It doesn't have to stay that way. The consulting firms and the monolithic systems got us to where we were. But they're not taking us where we need to go. Smaller teams. In-house teams. Flexible architecture. Genuine integration. That's what wins now.
Sources
- Open Banking in 2025: Now Part of the UK's Everyday Financial Life - Open Banking
- Hiring Fintech Consultants: When, How, and What It Costs
- In-house FTE or consultant subject matter expert?
- Top Fintech Lending Platforms 2025: APIs & Features
- Loan Origination Software Market Size and Growth