Core vs Configuration
Understanding Core vs Configured
When following this guide, it's important to distinguish between Core and Configured functionality.
Core Functionality:
Core Functionality refers to the standard set of features and capabilities that are deployed for every client using the Insureflow platform. Developed according to a continually evolving roadmap, these features provide the fundamental infrastructure and architecture upon which the platform operates.
Characteristics:
Consistency: Core functionality remains consistent across the system and is not affected by specific configurations tailored to individual business needs or insurance products.
Ongoing Development: Subject to regular updates and enhancements, ensuring that all clients benefit from the latest advancements.
Universal: Available to all clients upon deployment, forming the base layer of the platform.
Configured Functionality:
Configured Functionality pertains to the bespoke features and processes tailored specifically for the client and its range of insurance products. These features are configured within the Insureflow Product Builder.
Characteristics:
Customisable: Adapted to meet the particular requirements of your insurance products, including questions, workflows, and document templates.
Flexible: Enables individual products to have their own unique processes and workflows, allowing for a customised customer journey.
Low-Code: Employs a low-code approach, making it easier for your team to adapt and create new products without requiring extensive technical skills.
Key Difference:
The primary difference lies in personalisation. Core Functionality serves as the stable foundation of the platform, while Configured Functionality allows for the tailoring of specific aspects, such as the Draft Risk process, which can present varying questions and choices depending on the product managed or created within the platform.
Last updated