How to Build an Insurance Marketplace in India (IRDAI Web Aggregator Guide)
AI Summary: Building an insurance marketplace in India involves choosing the right business model, obtaining the required IRDAI registration, and developing a secure platform for comparing and purchasing insurance policies. This guide covers licensing requirements, essential features, technology integrations, development costs, and revenue opportunities to help you plan your insurance marketplace. |
An insurance marketplace looks simple from the outside: a user enters a few details, compares plans from several insurers and buys one. Behind it sits one of India's most regulated distribution models. Comparing and selling insurance online is an intermediary activity under the Insurance Regulatory and Development Authority of India (IRDAI), and the licence you choose decides what your platform may do.
This guide covers the IRDAI roles you can choose from, the web aggregator rules that shape the product, where Bima Sugam fits, the modules and insurer integrations you need, and the factors that drive cost and timeline.
For licences across other regulated fintech products and markets, see our Fintech Licensing Requirements 2026 guide.
Which IRDAI role fits your marketplace
Role | What it can do (in outline) | Fits when |
Insurance web aggregator | Runs a website that compares prices and product information from different insurers, generates leads and can facilitate the sale under its regulations | Your core product is online comparison |
Insurance broker | Represents the customer, advises across insurers and arranges cover | You want to advise, handle complex or commercial lines and service claims |
Corporate agent | Distributes products of a limited number of tied insurers | You are a bank, NBFC or platform selling insurance alongside other products |
Technology partner | Builds and runs software for a licensed intermediary or insurer | You want to sell the platform, not insurance |
Each role has its own IRDAI regulations, capital rules and code of conduct, and the rules on remuneration and on what each role may do change from time to time. Check the current regulations on irdai.gov.in and take legal advice before you choose.
Many fintechs start as a technology partner or a corporate agent and add a broking or web aggregator licence later. If comparison across many insurers is the heart of your product, the web aggregator route is the natural fit, so the rest of this guide focuses on it.
IRDAI web aggregator rules that shape the product
Web aggregators are governed by the IRDAI (Insurance Web Aggregators) Regulations, 2017, in force from 13 April 2017. These provisions affect your build most directly.
Capital and net worth
An applicant needs a minimum paid-up capital (or LLP contribution) of ₹25 lakh. For a company, the capital must be equity shares; for an LLP, partners' contributions must be in cash. The shares held as capital must stay unencumbered. Net worth must never fall below 100% of that minimum, and it has to be reviewed every half year, as at 30 September and 31 March. Your finance reporting should make that review easy.
Registration
The application is made in Form A with the documents the regulations list. IRDAI's policyholder site lists a non-refundable application fee of ₹10,000. IRDAI looks at the applicant's promoters, key management and fit-and-proper status.
Key management personnel
The regulations name the CEO, COO, CMO, CFO, Head – Technical and Head – IT as key management personnel. Technology leadership is part of the regulatory picture, not just the org chart.
Leads and the lead management system
The regulations define a "lead" as the details of a person who used the aggregator's website and submitted contact information to get prices, features or benefits of insurance products. They also define a Lead Management System (LMS): the software that records, filters, validates, grades, distributes, follows up and closes leads. In other words, IRDAI expects the LMS to exist and to keep a full record. It is a core module of your platform.
Telemarketing and distance marketing
If you sell by phone, SMS, email or online, the regulations treat it as distance marketing. Calls must be made by authorised verifiers who have completed the training and examination IRDAI specifies. Your contact-centre tools need call recording, verifier identity on every call, and links between calls and leads.
Outsourcing and records
The regulations limit which activities an aggregator may outsource. Keep a register of vendors and what they do, and store records of leads, comparisons, sales and complaints in a form you can produce for inspection.
Where Bima Sugam fits
IRDAI notified regulations in 2024 for Bima Sugam, a digital insurance marketplace being built as shared infrastructure for insurers, intermediaries and customers. It does not replace the web aggregator regulations. For a private marketplace, the practical question is how to integrate with Bima Sugam as it rolls out, not whether to compete with it. Keep your policy and customer data model flexible enough to connect to it later.
Core modules
Module | What it does |
Product catalogue | Plans, riders, eligibility and features from each insurer, kept up to date |
Quote engine | Collects user inputs and fetches real-time premiums from insurer APIs |
Comparison UI | Side-by-side plans with clear, neutral information |
Lead management system | Captures, validates, grades, distributes and closes leads, with a full audit trail |
Proposal and KYC | Proposal forms, KYC checks and document uploads |
Payments | Premium collection through the insurer's payment route or a payment partner |
Policy issuance | Receives policy documents from insurers and stores them for the customer |
Renewals | Reminders and renewal quotes |
Claims assistance | Guidance and tracking, with handover to the insurer |
Contact centre | Call routing, recording and verifier records |
Compliance and reporting | Records, complaints, net-worth reporting, regulatory returns |
CRM | Customer history across products. See our guide to insurance CRM software |
Insurer integrations and APIs
Most of the engineering effort goes into insurer integrations:
Quote APIs for real-time premiums, one per insurer and often one per product line
Proposal and policy APIs to submit proposals, collect payments and issue policies
Document APIs for policy PDFs and endorsements
Renewal and claims status APIs where insurers offer them
KYC and identity checks, including CKYC
Payments through UPI, cards and net banking
Insurer APIs vary widely in format and quality. Build an integration layer that maps each insurer's API to one internal model, so adding an insurer means writing an adapter, not changing the product. Our guide to the Policybazaar API shows what an aggregator-side integration looks like for term, health and motor insurance.
Planning to Build an Insurance Marketplace in India? Start with the Right Technology and Compliance Strategy
Compliance-by-design checklist
Requirement | Feature to build |
Lead records under the regulations | LMS with lead source, timestamps, status history and closure reason |
Neutral comparison | Ranking logic you can explain, with no hidden insurer bias |
Distance marketing | Call recording, authorised-verifier IDs, consent capture |
Customer consent for data sharing | Consent screens and records before sharing data with insurers |
Grievances | Complaint intake, tracking and escalation; IRDAI's Bima Bharosa route shown to customers |
Net worth reviews | Finance reports for 30 September and 31 March |
Outsourcing limits | Vendor register and contracts mapped to permitted activities |
Data protection | Encryption, access control and logging for personal and health data |
Designing a comparison users and IRDAI can trust
Comparison is the product, so the way you present it matters as much as the data behind it.
Like-for-like inputs. Use the same sum insured, term, add-ons and deductibles for every insurer in a comparison, and show the user what was assumed.
Clear premium breakdowns. Show base premium, riders, taxes and any discounts separately, so the final price is not a surprise at checkout.
Explainable ranking. If you sort by price, claim-settlement data or features, say so on the page. Avoid "recommended" badges that cannot be explained.
Fresh data. Product features and premiums change. Pull live quotes where insurers allow it, and date-stamp anything cached.
Plain-language features. Waiting periods, exclusions and co-payments drive claims disputes later. Put them in the comparison, not only in the policy wording.
Security and data protection
Insurance marketplaces handle health conditions, family details, vehicle data and payment information. Plan for:
Encryption of personal and health data at rest and in transit
Role-based access for contact-centre staff, so agents see only the leads assigned to them
Masking of sensitive fields in call-centre screens and logs
Consent records before sharing a customer's data with each insurer
Data retention rules that match your regulatory record-keeping duties and India's Digital Personal Data Protection Act, 2023 as its rules apply
Regular security testing of the website, apps and insurer integrations
Common mistakes
Treating the LMS as a sales CRM only. It is a regulatory record. Lead status changes, assignment and closure must be logged and kept.
One-off insurer integrations. Without an adapter layer, each new insurer becomes a project of its own.
Selling before the licence is in place. Run the product as a pilot with a licensed partner until your own registration comes through.
Ignoring renewals. Renewals are where most of the long-term revenue sits, so build reminders and renewal quotes early.
Cost and timeline drivers
We do not quote fixed prices without a scope. The biggest drivers are:
Number of insurers and product lines: every insurer API adds build and testing time
Lines of business: motor, health, term and travel each have different questions, rules and documents
Real-time vs offline quotes: real-time quotes need stable insurer APIs and caching
Contact centre: telemarketing adds telephony, recording and verifier tools
Licensing route: the IRDAI registration process runs alongside the build and sets your launch date
A phased plan
Choose your IRDAI role and start the registration work.
Build the catalogue, quote engine and comparison for one line of business with a few insurers.
Add the LMS, proposal, payment and policy issuance flows.
Add renewals, claims assistance and the contact centre.
Add more insurers and lines through the adapter layer.
Build your insurance marketplace with Fintegration
Fintegration builds insurance and fintech platforms in India and the US, from quote engines and insurer integrations to lead management and CRM. Talk to our team to plan your marketplace.
FAQ
1. What is an insurance marketplace in India?
An insurance marketplace is a digital platform where users can compare insurance plans, check premiums, and buy policies from different insurers in one place.
2. Do I need an IRDAI licence to start an insurance marketplace?
Yes, if you operate as an insurance web aggregator, you need to obtain the required registration from IRDAI and meet its regulatory requirements.
3. How much does it cost to build an insurance marketplace in India?
The cost depends on features, integrations, compliance requirements, and platform complexity. A basic marketplace will cost less than a fully automated insurance platform.
4. What features should an insurance marketplace include?
It should offer policy comparisons, premium calculators, customer registration, insurer integrations, online payments, policy management, and a secure admin dashboard.
5. How does an insurance marketplace earn revenue?
A registered insurance web aggregator can earn commissions from insurers for eligible policies, subject to IRDAI's prescribed commission and regulatory guidelines.
