Latest / Vertical SaaS with Fexingo: Industry-Specific Software for Healthcare, Construction, Legal / How Vertical SaaS Builds Indispensable Workflows
Transcript
- Lucas: I want to talk about the moment a piece of software stops being a tool and starts being infrastructure. In the horizontal world, you buy a project management app because it’s flexible. But in vertical SaaS, you install the software because if you don’t, your entire operational model collapses by Friday afternoon. Luna: Right, because the flexibility is actually the trap. If it’s too generic, nobody trusts it with their core revenue process. Lucas: Exactly. Let’s look at a concrete case from the legal sector. There was a mid-sized firm in Chicago that tried to run on a combination of a generic CRM and a spreadsheet tracker for billable hours. It took them eighteen months to realize they were losing twenty percent of their billable time just in administrative overhead. They switched to a vertical legal practice platform, and within six weeks, that overhead dropped to three percent. Luna: That’s a massive margin shift. Did they have to change how the attorneys worked, or did the software just adapt to them? Lucas: The key difference is that the vertical platform dictated the workflow in exchange for removing the friction. Horizontal tools try to accommodate every possible user behavior. Vertical tools say, this is how this industry works, and here is the single path to do it right. That constraint is what creates the moat. Luna: So the moat isn’t the code, it’s the institutional knowledge baked into the default settings? Lucas: Precisely. And this brings us to today’s angle: indispensability through workflow entrenchment. Most people think vertical SaaS wins on compliance or specialized features. But I’d argue the real winner is the company that becomes invisible because it handles the boring stuff so well that you can’t imagine working without it. Luna: Invisible is the goal. But does that make them vulnerable? If everyone uses the same invisible backbone, doesn’t that create systemic risk? Lucas: It does, but the switching cost is so high that it acts as a stabilizer. Let’s pivot to construction. In that sector, the software isn’t just tracking tasks; it’s managing subcontractor payments, material delivery windows, and safety compliance all in one thread. When you replace that system, you aren’t just changing software; you’re disrupting cash flow and supply chain logistics simultaneously. Luna: Which means the sales cycle is long, but the retention is practically permanent once they’re in. Lucas: Permanent is a strong word, but highly sticky is accurate. Because these systems capture historical data on every job, every vendor rating, and every material price variance. That data liquidity becomes a competitive advantage for the client, not just the vendor. You get smarter at bidding because the software remembers what you paid for lumber last winter. Luna: So the value proposition shifts from saving time to generating better decisions based on proprietary history. Lucas: Yes. And that’s where the distinction between a feature and a workflow matters. A feature is a button you click. A workflow is the sequence of events that leads to a paycheck. Vertical SaaS owns the paycheck moment. Luna: It sounds like they’re essentially acting as the operating system for industries that never had one before. Lucas: That’s the best way to put it. Before vertical SaaS, many industries ran on email chains and Excel sheets. Now, they run on a centralized truth. But let’s pause for a second to talk about how we keep this show running, because that truth applies to us too. Luna: Yeah, transparency is part of the workflow here. We rely on our listeners to keep the lights on. Lucas: Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. No ads, no corporate sponsors, just direct support from operators who find value in the analysis. Luna: It keeps the signal clean and lets us dig deeper into the niche topics that matter most to builders. Lucas: Back to the workflow. In healthcare, this entrenchment looks different than in construction. Here, it’s about patient continuity. A clinic uses a vertical EHR system that tracks everything from intake forms to insurance pre-authorizations. The doctor doesn’t just see a patient; they see the entire history of interactions, referrals, and outcomes. Luna: And that data linkage is what makes it dangerous to switch. You’d lose the context of care. Lucas: Exactly. And unlike construction, where the data is mostly financial and logistical, healthcare data is deeply relational. The software learns the preferences of specific providers, the common protocols for specific conditions, and even the communication styles of different nursing staff. It becomes a cognitive extension of the medical team. Luna: That’s a high bar. It’s not just storing data; it’s learning the culture of the practice. Lucas: Right. And this is why generalist health tech often fails. They build a dashboard. Vertical players build a habit. When the nurse walks in, the first screen shows exactly what needs to happen next. That reduces cognitive load, which is the scarcest resource in medicine. Luna: So the product design is driven by reducing stress, not just adding functionality. Lucas: Absolutely. And this ties back to the implementation gap we discussed in previous episodes. The software only works if it fits the existing rhythm. If you force a new workflow on a tired surgeon, they will revolt. The best vertical SaaS companies hire former practitioners to design the interface, not just engineers. Luna: That explains why some of these tools feel so intuitive while others feel like they’re fighting you. Lucas: It’s the difference between a tool and a colleague. A tool waits for your command. A colleague anticipates your need. That anticipation is built on thousands of iterations of user feedback from inside the industry. Luna: But doesn’t that specialization limit their total addressable market? If you’re only serving lawyers or contractors, how do you scale? Lucas: They scale by dominating the niche vertically rather than expanding horizontally. They become the standard. Once a vertical player defines the category, they set the pricing power. Clients don’t compare them to alternatives; they compare them to the cost of chaos. Luna: Chaos is expensive. So the premium price is justified by the avoidance of disaster. Lucas: Disaster is the baseline expectation in complex industries. Avoiding it is the product. This is why these companies often have higher gross margins than their horizontal counterparts. They aren’t spending millions on broad marketing campaigns. They are embedded in the professional networks of their customers. Luna: Word of mouth in a closed industry is incredibly powerful. If the top firm uses it, everyone else has to follow. Lucas: It creates a network effect within the vertical. Your vendors use the same platform, your clients can access their data easily, and your regulators are comfortable with the audit trail. It becomes a ecosystem lock-in. Luna: So the moat is defensive, but also offensive. It helps your customers do business better with their partners. Lucas: Exactly. And that’s the future of B2B software. It’s not about isolated productivity; it’s about connected reliability. As we move further into October 2026, with interest rates stabilizing and capital becoming more selective, investors are looking for businesses with predictable, recurring revenue and high switching costs. Luna: Vertical SaaS delivers both. It’s unsexy, but it’s durable. Lucas: Durability is the new growth. Growth is noisy. Durability is quiet. And in the long run, quiet compounds. Luna: I think the lesson for founders is to stop trying to be everything to everyone, and start being indispensable to someone. Lucas: Indispensability is harder to build than ubiquity, but it lasts longer. If you can solve the specific pain points of a narrow group so well that they cannot function without you, you have won. Luna: So the question isn’t how big can you get, but how deep can you go. Lucas: Depth beats breadth every time when the stakes are high. The next wave of winners won’t be the ones with the flashiest AI demos. They’ll be the ones who understand the daily grind of their customers better than the customers do themselves. Luna: That’s a compelling vision for the next decade of software. Deeply integrated, deeply understood. Lucas: And deeply necessary. When the system goes down, the business stops. That’s the ultimate leverage. Luna: It forces you to ask: what part of your operation is truly essential, and what part is just noise. Lucas: If your software is just noise, you’ll cut it. If it’s essential, you’ll pay anything to keep it running. Luna: A useful filter for any tech investment decision. Essential versus optional. Lucas: Essential is the only category that matters in the long run. Everything else is just a hobby. Luna: Here’s to building software that matters, not just software that sells. Lucas: Agreed. Next week, we’ll look at how these embedded workflows are starting to influence credit markets.