Latest / Vertical SaaS with Fexingo: Industry-Specific Software for Healthcare, Construction, Legal / How Vertical SaaS Is Conquering Community Banks
Transcript
- Lucas: So there are roughly 4,800 community banks in the United States — institutions with under about ten billion dollars in assets. And a surprising number of them are still running core processing software built in the 1980s. Luna: I've heard that number before — some of those systems are running on COBOL, right? The same code that's been in place for decades. Lucas: Exactly. And for a long time, the big core providers — Jack Henry, Fiserv, FIS — had those banks locked into multi-year contracts with proprietary systems that were really hard to bolt new technology onto. But in the last three or four years, we've seen a shift. Vertical SaaS companies are starting to embed themselves inside these banks the same way they embedded into dental practices or veterinary clinics. Luna: So instead of selling a separate piece of software that sits on top of the bank's system, they're building modules that plug directly into the core? Like a lending module, a compliance module? Lucas: Right. And the key insight is that community banks don't have the engineering teams to build these tools themselves. They have maybe two or three IT people. So when a vertical SaaS provider comes in and says, 'We'll handle your small-business lending workflow, from application through underwriting through closing, all inside the interface your loan officers already use,' that's a very easy sell. Luna: I want to get into a specific example. You mentioned a bank in Ohio — a two-billion-dollar institution that cut loan processing time by forty percent. Tell me about that. Lucas: Yeah, that's a real case from a company called Nymbus, which is one of the newer entrants in this space. They partnered with a bank called Heartland Bank — based in Columbus, Ohio. Heartland had a problem: their small-business loan origination process was taking twelve to fourteen days on average. A lot of that was manual data entry, paper documents being faxed back and forth, and then hand-keyed into the core system. Luna: Fourteen days for a small-business loan. That's wild. A fintech like Kabbage or OnDeck can do it in minutes. Lucas: Exactly. So Nymbus came in and deployed an embedded lending module that sits on top of Heartland's existing core — which happened to be Jack Henry's Silverlake system. The module automated the data gathering from bank statements, tax returns, and credit bureaus. Loan officers could review everything on one screen, and the system pushed approved loans directly into the core for booking. The result: average processing time dropped from fourteen days to about eight. That's a forty-three percent improvement. Luna: And what's interesting is that Nymbus isn't just selling software — they're essentially becoming the bank's digital lending department. That's the vertical SaaS model: deep integration, not just a point solution. Lucas: Exactly. And that's the pattern we're seeing across dozens of banks. The vertical SaaS providers are taking over specific functions — lending, compliance monitoring, deposit account opening, even treasury management — and doing it in a way that's inseparable from the bank's core operations. The bank gets modern capabilities without having to replace its core system, which is a multi-year, multi million dollar project that most community banks simply cannot undertake. Luna: So the core providers themselves — Jack Henry, Fiserv — they must be watching this and thinking about whether to build or buy. Are they responding? Lucas: They are. Jack Henry, for example, has been rolling out its own embedded lending and payments APIs through a platform called Banno. But the challenge for them is that they have to serve thousands of banks with very different needs. A vertical SaaS company can be hyper-specific. There's a company called Amount that focuses purely on consumer lending for banks. There's another called Autobooks that does small-business invoicing and payments inside online banking. The specialization is hard for the big core providers to match. Luna: And that specialization is also why the community banks are willing to pay a premium. They're getting expertise, not just code. Lucas: Right. And the pricing model is classic vertical SaaS — usually a monthly per-user fee or a per-transaction fee, with multi-year contracts that include implementation and ongoing support. The average community bank might pay anywhere from five thousand to twenty thousand dollars a month for a lending module, depending on the size. That's a fraction of what it would cost to build internally, and it comes with continuous updates. Luna: Let's talk about a different function: compliance. Community banks are drowning in regulatory requirements — the Bank Secrecy Act, anti-money laundering, know your customer rules. Is vertical SaaS making inroads there? Lucas: Big time. There's a company called Alloy that offers a compliance orchestration platform. They integrate with the bank's core and with multiple data sources — credit bureaus, identity verification services, sanctions lists — and automate the entire onboarding and monitoring process. For a community bank, that's massive because compliance staff are expensive and hard to find. One bank we looked at, a three-billion-dollar institution in the Midwest, was able to reduce its compliance headcount by two full-time employees after implementing Alloy — saving roughly a hundred and fifty thousand dollars a year. Luna: And the bank gets better coverage, too. Software doesn't miss a suspicious transaction the way a tired human might at four in the afternoon. Lucas: Exactly. And that's the value proposition that's really resonating. The community banking sector is under pressure from all sides: larger banks with massive technology budgets, fintechs that can offer a better digital experience, and a regulatory environment that gets more complex every year. Vertical SaaS is giving them a fighting chance without requiring them to become technology companies themselves. Luna: I want to ask about the competitive dynamics. If I'm a vertical SaaS company targeting community banks, my customers are also my potential competitors' customers, right? Because those banks could theoretically switch to another module provider. Lucas: That's true, but switching costs are high. Once you've embedded your lending module into a bank's workflow — trained the loan officers, integrated with the core, connected to the credit bureaus — it's very sticky. The data and the process are deeply intertwined. That's the classic vertical SaaS moat. And the banks are reluctant to switch because it would mean retraining staff and risking operational disruption. Luna: So it's a land-grab right now. The providers that get in first and deepest will likely hold those relationships for years. Lucas: Absolutely. And we're seeing a wave of M&A activity as larger fintechs and even some of the core providers buy these vertical SaaS companies to add to their platforms. In 2025 alone, there were at least a dozen acquisitions of community-banking SaaS companies. The valuations are attractive because these are recurring-revenue businesses with high retention rates. Luna: Before we wrap, I want to touch on something you mentioned earlier — the regulatory sandbox. Some states are creating environments where banks can test new technology with relaxed regulatory requirements. How does that play into vertical SaaS adoption? Lucas: It's a huge accelerator. The Arizona Regulatory Sandbox, for example, allows banks to partner with fintechs and SaaS providers to test products for up to two years without full licensing. That reduces the risk for both the bank and the SaaS provider. Several vertical SaaS companies have used sandboxes to pilot embedded lending or compliance tools with a small group of banks, prove the model, and then scale. It lowers the barrier to entry significantly. Luna: And it gives regulators comfort, too, because they can see the results before giving full approval. It's a smart approach. Lucas: Exactly. So the trajectory here is pretty clear. Over the next five years, I think we'll see the majority of community banks in the U.S. running on a combination of their legacy core and a stack of vertical SaaS modules. The core becomes the plumbing, and the SaaS becomes the applications that bankers and customers actually interact with. Luna: You know, it's funny — we're talking about banks, which we think of as the most traditional industry, but the adoption pattern is almost identical to what we saw with dental practices and veterinary clinics: a specialized SaaS provider comes in, solves a specific pain point, integrates deeply, and becomes indispensable. Lucas: And that pattern is exactly why this show exists. These conversations about what operators and builders are doing are genuinely useful for anyone running or building something. Luna: Yeah. And if you find them useful, there's a small way to keep them going. A couple of dollars a month makes a real difference — no pressure at all. Lucas: It's at buy me a coffee dot com slash fexingo. That's where you can find it. And back to the point — the community banking shift is still in its early innings, but the data we've seen suggests it's accelerating. Luna: So the question is: which vertical SaaS company will become the operating system for Main Street banking? And how will the big core providers respond? Lucas: That's the story we'll keep following. For now, the takeaway is that vertical SaaS isn't just for niche industries — it's embedding itself into the backbone of American finance, one community bank at a time.