Latest / Vertical SaaS with Fexingo: Industry-Specific Software for Healthcare, Construction, Legal / How Vertical SaaS Is Embedding Insurance Into Software
Transcript
- Lucas: You walk into a restaurant. The host seats you, the waiter takes your order, the kitchen fires up the grill. Behind that smooth experience there is a stack of software—point of sale, inventory, scheduling, payroll. And now, increasingly, insurance. Luna: Insurance? Like, the restaurant owner is buying a policy through the same tablet they use to swipe credit cards? Lucas: Exactly. That is the embedded insurance model, and it is one of the fastest-growing revenue lines for vertical SaaS companies. Toast, the restaurant operating system, started offering general liability and workers' comp coverage through a partnership with Progressive. The restaurant owner never talks to an agent. They click a button inside the Toast dashboard, answer maybe six questions, and get a quote. Luna: So Toast becomes an insurance distributor. What's in it for them? A commission on every policy sold? Lucas: Yes, typically a commission between 10 and 20 percent of the premium. But the bigger play is retention. A restaurant that buys insurance through Toast is significantly less likely to switch POS systems. The insurance becomes another layer of lock-in. For the insurer, Progressive gets access to a curated pool of businesses with real-time transaction data, so they can underwrite more accurately than a generic small-business policy ever could. Luna: So the restaurant's actual sales data helps determine the premium. If they have lower alcohol sales, maybe lower liability risk? Lucas: That is exactly the idea. Toast can share anonymized data on revenue, employee count, even the type of cuisine—a pizzeria has different risk profile than a seafood place with a fryer. The insurer uses that to price the policy more precisely. The restaurant owner often gets a lower rate than they would on the open market, because the data reduces the uncertainty premium. Luna: And Toast isn't alone. Procore in construction, Mindbody in fitness, even some veterinary practice management platforms are doing similar things. Lucas: Procore is a great example. They launched Procore Insurance in 2022, initially focused on general liability for subcontractors. Construction has notoriously high premiums and complex risk profiles. Procore uses project data—scope of work, safety logs, subcontractor tier—to help insurers quote faster. Some reports say contractors get quotes in under a minute, compared to days with a traditional broker. Luna: That speed alone changes the buying behavior. If you're a small contractor juggling three bids and a crew on site, you're not going to spend a week shopping for insurance. You'll buy the one that shows up in your software. Lucas: And that is where the embedded model wins. It is not just convenience—it is reducing friction in a category where most small business owners are underinsured or buy the wrong coverage because they don't have time to compare. A 2023 survey from the Small Business Majority found that 40 percent of small businesses don't have any general liability insurance. The embedded channel can close that gap. Luna: Let's talk numbers. How big is this market? Lucas: The global embedded insurance market was valued at around $60 billion in 2024, and projections for 2030 range from $70 to $100 billion depending on how you define 'embedded.' The vertical SaaS slice is still small—maybe 5 to 8 percent—but growing at a compound annual growth rate north of 25 percent. The big incumbents are paying attention. Allstate and Nationwide have both launched api based programs specifically for SaaS platforms. Luna: You mentioned the data advantage. But doesn't that also create a conflict? The SaaS platform wants to sell policies to boost revenue, but they're also supposed to be the restaurant's trusted partner. If they push a policy that isn't the best fit, that trust erodes. Lucas: That is a real tension. The best implementations are transparent about the commission and offer multiple carrier options. Toast, for instance, started with Progressive but has since added other carriers. They also make it clear that buying insurance through them is optional—you can still use Toast without it. The key is that the insurance product has to be genuinely better or more convenient than the alternative. If it's just a cross-sell with no value add, customers will churn. Luna: And if they handle it well, the SaaS platform starts to look less like software and more like a business operating system. You're managing payments, payroll, employees, and now risk. Lucas: That is the endgame. The term 'operating system' gets thrown around a lot, but this is the real thing. When a business runs every critical function through one platform, including insurance, the switching cost becomes enormous. That is why the public market values companies like Toast at a multiple that would be hard to justify on restaurant POS alone. The embedded revenue is the growth story. Luna: One thing I'm curious about is the regulatory side. Insurance is state-regulated in the US. How do these SaaS platforms handle fifty different sets of rules? Lucas: They typically don't become insurers themselves. They partner with a licensed carrier or an MGA—managing general agent—that holds the licenses and assumes the risk. The SaaS platform acts as a distributor. But they do need to comply with state-specific disclosure requirements, licensing for the sales process, and data privacy laws. That's why most platforms start with a single line of business in a few states and expand gradually. Toast began with general liability in about 30 states and added workers' comp later. Luna: So the compliance overhead is real but manageable if you've got a good partner. What about the customer experience? Is it truly one-click, or is there still paperwork? Lucas: It varies. The best-in-class experiences are almost fully automated. You log into the dashboard, you see a prompt: 'Your restaurant may qualify for a discounted insurance policy. Get a quote in 60 seconds.' You click, the system pre-fills your business info from the data Toast already has—name, address, revenue range, number of employees. You just confirm a few details and hit submit. The quote comes back instantly. If you accept, payment is processed through the same payment system you already use. The policy documents are stored in the dashboard. No faxing, no phone calls. Luna: It's like buying a plane ticket online versus calling a travel agent. That shift is huge for an industry that still runs on paper in many corners. Lucas: And it's not just restaurant and construction. We're seeing it in fitness—Mindbody offers liability coverage for yoga studios and gyms. In veterinary, some platforms are embedding pet health insurance at checkout. Even in legal, a few practice management tools are testing malpractice insurance for solo attorneys. The pattern is the same: identify a common insurance need, use existing data to streamline underwriting, and integrate the purchase into the software workflow. Luna: It makes me think about the economics for the SaaS company. If a typical restaurant pays, say, $2,000 a year for general liability, and the SaaS platform gets a 15 percent commission, that's $300 per customer per year. If they have 50,000 restaurant customers, that's $15 million in annual commission revenue—mostly high-margin, recurring. Lucas: And that's just one line of insurance. Add workers' comp, property, cyber liability—the per-customer revenue can double or triple. Plus, these commissions are often more profitable than the core subscription fee because there's no hosting cost associated with them. The incremental cost of adding insurance distribution is close to zero once the integration is built. Luna: Let's zoom out. How does this trend affect the traditional insurance agent? Are they being disintermediated? Lucas: In some segments, yes. The independent agent who specialized in small commercial lines—restaurants, contractors, retail stores—is losing business to embedded channels. But the agents who focus on complex risks, like large construction projects or multi-location enterprises, are less affected because those policies require more customization and human judgment. The embedded model works best for standardized, low-touch policies. So it's not extinction, but it is a shrinking of the market for certain agent types. Luna: It also changes the customer relationship. If you buy insurance through Toast, who do you call when you have a claim? Toast or Progressive? Lucas: That's a critical detail. Most embedded models route claims directly to the carrier, not the SaaS platform. The platform doesn't want to build a claims department. But the customer's expectation is that they can get help from the platform they trust. So some platforms are adding a concierge layer—a small team that helps the customer file the claim and then advocates on their behalf with the carrier. That adds cost, but it also deepens the relationship. Luna: So the platform becomes an advocate, not just a middleman. That's a smart way to maintain trust. Lucas: Exactly. And it ties back to the data advantage. When a platform helps with a claim, they can see patterns—which types of claims are most common, which carriers pay quickly, which adjusters are difficult. That intelligence can feed back into the underwriting data and help the platform negotiate better terms with carriers over time. Luna: It's a flywheel. More data leads to better underwriting leads to lower premiums leads to more customers leads to more data. Lucas: That's the thesis. And it's why we're seeing private equity pour money into vertical SaaS platforms with embedded insurance capabilities. They see the unit economics improving over time as the data network effects kick in. Luna: I want to pause on something. You mentioned that vertical SaaS companies are embedding insurance, but a lot of listeners might think of this as just another feature add-on. What makes it truly transformational? Lucas: The transformation is that insurance moves from a separate, annual chore to an integrated, ongoing part of business operations. Instead of being a cost to minimize, it becomes a tool that's embedded in how the business runs. The restaurant owner can see their insurance coverage alongside their daily sales report. The contractor can see how safety incidents affect their premium in real time. That visibility changes behavior—and that's what insurers and platforms are betting on. Luna: So it's not just distribution. It's risk management as a service. Lucas: Exactly right. And that's where the real value creation happens. The software doesn't just sell insurance; it helps the customer avoid claims. Some platforms are already adding safety training modules, automated reminders for equipment inspections, and discounts for completing those tasks. That's a win for everyone—the business owner, the insurer, and the platform. Luna: It's interesting to think about where this goes next. Could we see embedded insurance for things like cyber liability for small businesses? Or even professional liability for consultants? Lucas: Absolutely. Cyber liability is a huge opportunity because most small businesses don't have it. Platforms like Shopify, which serves millions of e-commerce merchants, could easily embed a cyber policy that covers data breaches. The underwriting data is already there—transaction volume, customer data stored, security features enabled. It's a natural fit. Professional liability for freelancers and consultants is also ripe, especially through platforms like Gusto or QuickBooks that already handle payroll and invoicing. Luna: The key question is whether customers will trust the platform enough to buy insurance from them. For many small business owners, insurance is something they buy from a person they know, not a dashboard. Lucas: That trust barrier is real, but it's eroding. The same way people were hesitant to buy plane tickets online in the late 90s, now it's unthinkable to call a travel agent. Younger business owners, especially millennials and Gen Z, are completely comfortable transacting through software. They expect their business tools to be integrated. And they're more likely to trust a platform they use daily than an agent they've never met. Luna: So it's not just a distribution shift. It's a generational shift in how business owners think about purchasing financial products. Lucas: Exactly. And that's why every vertical SaaS company with a sticky product and good data should at least explore the insurance opportunity. It doesn't have to be a massive revenue line initially. But over five to ten years, it could become a significant profit center and a powerful moat. Luna: Alright, Lucas, let's bring it home. If someone is running a vertical SaaS company and wants to get started with embedded insurance, what's the first step? Lucas: Step one is understanding your customer's insurance needs. Talk to ten of them. Ask what policies they carry, what they pay, and what frustrates them about the process. Step two is finding the right insurance partner—a carrier or MGA that has an API and is willing to work with a platform of your size. Start with a single line of business in a single state. Prove the model before scaling. And step three is designing the user experience so that it feels like a natural extension of your product, not an upsell. Luna: It's a classic vertical SaaS playbook: start narrow, iterate fast, and use data to deepen the relationship. Lucas: And as the data accumulates, the moat gets wider. That's the beauty of embedding insurance. It's not just a new revenue stream—it's a strategic asset that compounds over time. Luna: That's a great note to end on. Thanks, Lucas. Lucas: Thanks, Luna. And thanks to everyone listening.