August 07, 2024
By Winter Gao
The insurance industry is at an inflection point for digital transformation. Companies have recognised the need for modern core systems to stay competitive – by making accommodation for new margin scrutiny and adapting to changing customer demands and expectations.
Many have acknowledged their legacy systems have reached end-of-life and present mounting operational risks.
This is now an era of core modernisation and establishing design principles for insurers’ core architecture is critical for evaluating business needs and any overarching technology strategy.
One of these design principles highlights how insurers will achieve their architecture blueprint.
Avoid reinventing the wheel
Breaking down the terminology
OOTB software comes with configurable options alongside pre-packaged sets of features and functionalities. This allows the assembly of existing features and modules more quickly, removing the need for code development thus, accelerating the foundation of a modern core system.
These components have configurable workflows that allow functionalities to be aligned to modern practices at a lower cost. Depending on the maturity of the configurable settings, insurers may be able to set up the system for their unique business requirements without incurring time-consuming and costly customisations.
Being able to configure settings at earlier parts of the value chain – ie, product configuration – means they will be directly linked and integrated into business logic that flows through sales, policy servicing and claims, transforming capabilities into a true end-to-end system.
The scope of OOTB capabilities and functional coverage will minimize the growth of future technical debt from stale customisation, making it appealing to insurers looking for swift digitisation.
Custom-built functionalities are commonly designed from the ground up to fulfil an insurance company’s specific requirements, in particular around gaps where existing solutions have not worked. This requires sourcing expertise, often in-house or externally on a one-off basis, which creates complexity and challenges for future maintenance and adaption for an ever-changing landscape of technical and functional user needs.
This means the build phase involves starting from scratch and crafting a solution tailored to the insurer’s exact specifications. Over time, trade-offs may be sanctioned in order to meet tangible milestones, which can compromise the original vision.
That said, customisation can solve the insurers’ immediate needs exactly, but it will come at a cost. The process is costly, demands specialised expertise, and is time-consuming, posing a risk that the resulting system may be obsolete before its launch.
Better by design
At face value, OOTB solutions appear to be a better fit than a custom build. OOTB not only meets the fundamental functional requirements by allowing customisation through configuration and accelerating the speed-to-market, but introduces new concepts to address the actual requirements.
Most of these requirements are broken down by configurability, API aggregation and the integration of plug-ins. While nothing matches the flexibility of customisation (assuming no budget or time constraints), OOTB solutions reduce initial investments and future customisation efforts for evolving needs. They also give insurers greater control over the shape and evolution of solution as the project matures.
In turn, this helps to deal with the problems of return on investment (ROI) that are unavoidable in a custom build.
However, there will always be certain areas of the insurer’s business that are considered unique – points of differentiation or unsuitable for the configurability offered by OOTB solutions. In these cases, a more granular, custom-built solution may be necessary.
How this is identified and integrated into the project is an important part of the design process.
Important considerations - Measure twice, cut once
Balancing custom-built solutions with the benefits of OOTB configurability is crucial. An 80:20 ratio – where 80% of functionalities are covered by OOTB solutions and 20% involve minimal customisation or “last mile customisations” – has proven to be a popular strategy for insurers seeking speed-to-market and adaptability. This may be localisation or integration to legacy, other custom solutions, or other third-party products.
Establishing the optimal core design principles is not about just driving efficiency. It is also a strategic attempt to drive growth and elevate customer satisfaction to ensure lasting engagement and retention.
The insurer must determine and align on which parts of the organisation and core processes are part of the 80%. This involves addressing three critical aspects:
Technology: What are the overarching strategic needs and priorities? Which capabilities does the business need to differentiate? Which areas will require custom technologies to be built and how do we do that? Which of these capabilities will require ongoing enhancements? Where does flexibility of re-configuration need to be?
Long-term operating context: Where do we find sufficient IT talent, capabilities and resource for the areas we control? How much control do we need over unique functionalities in technology that differentiates us? What is the implied long-term capex and opex cost?
Delivering modernization: What Is our budget? How urgent is our need for modernisation? How quickly do we need to go to market? How do we manage BAU roadmaps and systems vs new system requirements and delivery?
Before determining whether custom-built or OOTB solutions will be most appropriate, there are a few key criteria to consider:
Speed-to-market: Insurers looking for rapid digitization should opt for OOTB as they are faster to deploy than custom-built alternatives.
Budget constraints: Custom built solutions often require high investments for development, testing, and ongoing maintenance, making them unsuitable for those with limited financial resources. OOTB offers cost efficiency, as its configurability minimises the need for extensive customization, reducing development expenses.
Integration needs: If you require seamless integration with multiple systems – CRM, financial systems, third-party data providers, etc – OOTB systems with a broad ecosystem of solution providers may be advantageous.
Scalability: What does the future hold? Custom built solutions can be tailored to accommodate future expansion, while OOTB solutions may offer scalability features suitable for smaller to mid-sized insurers.
End-user experience: Customers demand seamless experiences. OOTB solutions often come with user-friendly interfaces and features that enhance both customer and employee experiences.
Maintenance and support: Custom-built systems may require more intensive care, whereas OOTB systems often come with vendor provided support.
In many cases, OOTB solutions emerge as the clear winner over pure custom-built solutions, not only for those seeking rapid digitalisation, but also for insurers aiming to retain control over development and future enhancement costs. Considerations such as project timeline, financial resources, flexibility and customisation, scalability and adaptability, ongoing support, and maintenance collectively contribute to OOTB’s superiority in achieving digital transformation goals over custom-built solutions.
Case study: Prudential Thailand
Futureproofing is essential
Focusing on the right core design principles for your insurance architecture incorporating OOTB and understanding upgradability helps to futureproof operations and keep you ahead in the industry.
Solutions with wider coverage of OOTB configuration and offer upgradability empower insurers to seamlessly integrate their business logic across sales, policy servicing, and claims processes. With frequent release cycles, new functional capabilities and technological features become swiftly available to customers without causing operational disruptions.
This adaptability places insurers at the forefront of insurance innovation, maintaining a modern and secure tech stack. It eliminates the need for extensive patchwork customisations over the years, ensuring a streamlined and efficient system for the long term. Instead, only a minimal amount of customisation is needed to address for last mile of specialised needs.
Interested in learning how to optimise your core system with Graphene? Get in touch with us here.
Whitepaper
Successfully turning digital leads into high value sales
Whitepaper
Leveraging AI to automate processes and mitigate fraud