As an early adopter of blockchain and a veteran advisor to countless FinTech startups, Nicholas Braiden has a unique vantage point on the evolution of financial technology. He has consistently championed technology’s power to redefine digital finance, and today, he offers his perspective on a new insurance accelerator from InsureMO and Digile. This solution aims to solve one of the industry’s most persistent headaches: modernizing core operations without the immense risk of a complete system overhaul. Our conversation explores how this “gradual, workflow-led” approach untangles fragmented underwriting and claims processes, the powerful synergy between microservices and enterprise automation, and how insurers can finally achieve scalability and innovation without embarking on another overwhelming transformation project.
Your new accelerator avoids full core system replacement using a “gradual, workflow-led” approach. Can you walk us through how combining InsureMO’s microservices with ServiceNow’s automation achieves this, perhaps by describing the first few steps an insurer would take?
It’s all about targeted evolution rather than a high-risk revolution. Insurers are understandably wary of multi-year, budget-breaking core replacement projects. This approach sidesteps that entirely. The first step for an insurer is to identify a single, critical pain point—say, a specific underwriting workflow that’s notoriously slow and manual. We don’t touch the core system of record. Instead, we use InsureMO’s library of composable insurance microservices to handle the specific business logic, like product configuration or underwriting rules, for that process. Then, we layer Digile’s ServiceNow expertise on top to orchestrate the end-to-end workflow, connecting the people and disparate systems involved. This creates an agile, automated process that sits on top of the legacy core, delivering immediate value and demonstrating the power of the model before tackling the next workflow.
The article mentions solving fragmented underwriting and claims workflows. Could you describe how the accelerator orchestrates these siloed processes end-to-end and what specific metrics an insurer might see improve, like cycle times or operational costs, after implementation?
Fragmentation is the silent killer of efficiency in insurance. You have underwriters in one system, claims adjusters in another, and customer service using something else entirely, with emails and spreadsheets plugging the gaps. It’s a mess. This accelerator acts as the central nervous system, creating a single, unified workflow that connects these traditionally siloed functions. For instance, when a claim is initiated, the platform can automatically pull policy data via an InsureMO API, assign tasks in ServiceNow, and provide a transparent, real-time view to everyone involved. The impact on metrics is profound. You would absolutely see a dramatic reduction in cycle times because you’re eliminating the manual handoffs and wait times. This directly translates to lower operational costs, as you’re automating repetitive tasks and freeing up skilled professionals to focus on value-added work.
Rajat Sharma noted the blend of InsureMO’s API-led architecture and Digile’s ServiceNow capability. Can you elaborate on how these two technologies complement each other and detail how they would practically handle a complex underwriting rule change for a new product?
It’s a perfect partnership of domain expertise and enterprise-wide execution. Think of InsureMO as the “insurance brain.” Its API-led architecture provides the granular, pre-built components for anything insurance-specific—product rules, rating, policy logic. It speaks the language of insurance. Digile’s ServiceNow capability is the “enterprise backbone.” It takes those insurance-specific functions and weaves them into a coherent, automated workflow that spans across departments. So, for a complex rule change, a business user could configure the new rule within InsureMO’s product tools. The moment it’s saved, that logic is available via an API. The ServiceNow workflow, designed by Digile, immediately ingests this new rule and applies it across the entire underwriting process, from quote to bind, without a single line of code needing to be rewritten in the core system. It’s the difference between remodeling the entire building versus simply hanging a new piece of art.
The solution promises scalable operations and a unified experience across channels. How does the accelerator help an insurer manage a sudden surge in claims volume while also providing improved visibility and collaboration tools for adjusters, underwriters, and management?
Scalability is where legacy systems truly falter, especially during a crisis like a major weather event. This accelerator is built on a modern, cloud-based foundation that can handle massive fluctuations in volume without breaking a sweat. When a surge hits, every claim, whether it comes from a web portal, a mobile app, or a call center, flows into the same unified ServiceNow workflow. This is a game-changer for visibility. Management gets a single, real-time dashboard showing the entire claims landscape—backlogs, cycle times, and resource allocation. For adjusters and underwriters, the collaborative tools mean they are no longer working in the dark. They can see all the case files, notes, and communications in one place, which eliminates redundant work and accelerates decision-making when every second counts.
Hitesh Sahijwaala said insurers want to avoid another “complex transformation program.” How does this accelerator’s design philosophy differ from traditional modernization projects, and what is the first major milestone a new client can typically expect to achieve?
His comment perfectly captures the industry’s fatigue with monolithic projects. The traditional approach is to spend years and millions of dollars on a “big bang” replacement that often fails to deliver on its promises. This accelerator’s philosophy is the polar opposite. It’s pragmatic, incremental, and focused on business value from day one. Instead of a five-year roadmap, we ask, “What is your biggest operational bottleneck right now?” The first major milestone for a client is typically conquering that specific challenge within months, not years. This might be fully automating the workflow for a single commercial insurance product or streamlining the first notice of loss process. Achieving that first win delivers a tangible ROI, builds confidence within the organization, and creates the momentum for tackling the next modernization priority in a manageable, low-risk way.
What is your forecast for underwriting automation in the next five years, particularly regarding the balance between replacing legacy core systems versus integrating innovative middleware like this?
My forecast is that the “rip and replace” model for core systems will become the exception, not the rule. The industry is shifting decisively toward a more pragmatic, hybrid approach. For the next five years, the dominant strategy will be to “wrap and extend” these legacy cores. Insurers will keep their core platforms as stable systems of record while layering agile, API-driven middleware like this accelerator on top to drive innovation. This allows them to achieve incredible speed and flexibility in areas like underwriting automation, product development, and customer experience, without taking on the monumental risk and expense of a full core transformation. The future isn’t about replacing the foundation; it’s about building a smarter, more connected structure on top of it.