BuildinganIntegratedCustomerandPartnerPlatformforManipalCignaHealthInsurance

Context

ManipalCigna Health Insurance is a joint venture between Manipal Group and Cigna Corporation operating in the Indian health insurance market. The business operates under IRDAI regulatory oversight and serves both direct customers and a partner channel through which policies are distributed by intermediaries.

Managing this dual-channel model requires separate operational environments for customers and partners, each with distinct workflows, data requirements, and access boundaries. It also requires integration with the CRM, payment, support, and marketing systems that the business depends on. Not as a convenience, but as an operational necessity. In insurance, fragmented systems create compliance risk, data inconsistency, and partner friction that directly affects policy distribution.

What Changed

ManipalCigna required a unified platform architecture that could support its customer portal, partner portal, and commission management system within a single integrated environment, while maintaining the regulatory compliance obligations imposed by IRDAI. Existing systems were not integrated at the level required to support the operational and compliance demands of the business at scale.

The engagement required Envigo to design and build the system from the ground up within a five-month delivery window.

Envigo’s Responsibility

Envigo was responsible for UX design, custom platform development, and systems integration across the full scope of the engagement. This included the customer portal, partner portal, partner commission system, gamification layer, Salesforce integration, payment gateway integration, marketing automation integration, custom CRM build, Freshdesk integration, and IRDAI compliance implementation. Envigo owned all architecture, integration, and development decisions.

Strategic Decisions

Decision 1: Design the customer and partner portals as distinct environments within a single platform

The customer portal and partner portal serve structurally different users with different data access requirements, workflow needs, and compliance obligations. Envigo chose to build both within a single platform architecture with enforced environment separation rather than deploying two independent systems. The two separate platforms would have created data synchronisation requirements between them, increased maintenance overhead, and introduced inconsistency risks in a regulated environment where data integrity is a compliance matter.

Decision 2: Integrate Salesforce as the system of record rather than building a parallel CRM

ManipalCigna’s commercial operations were already anchored to Salesforce. Envigo chose to integrate Salesforce as the authoritative CRM rather than building a parallel data layer that would have required ongoing synchronisation. The custom CRM layer Envigo built was designed to serve specific operational workflows not covered by Salesforce’s standard configuration, while keeping Salesforce as the source of truth for customer and partner data. Building a full replacement CRM was rejected because it would have introduced a data ownership conflict without resolving the operational gaps.

Decision 3: Build IRDAI compliance requirements into the platform architecture

Regulatory compliance in insurance requires that specific data handling, audit trail, and access control requirements are embedded in how the system operates rather than applied as restrictions on top of a system built without them. Envigo chose to design the platform with IRDAI compliance requirements as first-order architectural constraints. Retrofitting compliance onto a completed platform was rejected because in regulated industries, compliance overlays create both technical debt and audit exposure.

Decision 4: Implement a partner commission system with payment gateway integration to remove manual settlement dependencies

Partner channel management in insurance historically involves manual commission calculation and settlement processes that create delays, errors, and partner friction. Envigo built a commission system integrated with the payment gateway to automate calculation and settlement within the platform. Manual processes were rejected because they create operational risk at scale and damage partner relationships through settlement delays and disputes.

System Design

The platform integrated six external systems: Salesforce, payment gateway, Freshdesk, marketing automation, custom CRM, and the IRDAI compliance framework within a single operational environment. Each integration was designed so that data flowed between systems without manual intervention, and so that the compliance requirements of the regulated environment were met by the platform’s normal operation instead of requiring separate compliance processes.

The gamification layer was applied to the partner portal to support partner engagement and performance incentivisation within the same environment as commission management and policy distribution. This allowed partner motivation and partner operations to be managed from a single surface rather than through separate tools.

Outcomes

The platform was delivered in five months, encompassing customer portal, partner portal, partner commission system, six system integrations, and full IRDAI compliance implementation within a single architecture.

Scope Expansion

The partnership has continued since 2016. The long duration reflects both the operational criticality of the platform to ManipalCigna’s distribution model and the ongoing evolution of its compliance, integration, and partner management requirements.

Closing Reflection

In regulated industries, the relationship between operational complexity and compliance is structural. Systems built to serve partner channels, customer journeys, and regulatory requirements simultaneously are most durable when those requirements are treated as architectural inputs from the start rather than constraints applied to a completed build.