UPI took something that was broken, paper-heavy, and out of reach for most Indians and turned it into one system that everyone could use. Bima Sugam is trying to do the same thing for insurance. One platform where anyone can compare, buy, manage, and claim any policy from any insurer in the country.
The goal is big. So is the work. Sixty plus insurers, thousands of middlemen, decades of old systems, and a brand new digital platform all need to work together before a single customer can log in and do anything useful. The Insurance Regulatory and Development Authority of India (IRDAI) has set a rollout schedule by product type, starting with motor, then health, then life.
And the deadline has already moved before.
But something happens inside companies every time the date shifts. Something quiet. And quietly expensive.
You're not wrong to feel relieved. But relief has a price.
When a deadline moves, the first reaction is to slow down. Shift focus. Deal with what's in front of you. That's human. That's normal.
But here's what years of Bima Sugam delays have quietly taught teams. The deadline will probably move again. So there's no real urgency. And that's where things start to go wrong.
Some teams don't work to the IRDAI date at all. They work to their own. How long does this actually take? That's their question. Every extension just gives them more breathing room. It doesn't change what they're doing or how fast.
Other teams are tied to the calendar. When the date moves, everything moves with it. Clean-up work slips. Partner calls get rescheduled. Contingency plans get shelved. There's still time, after all.
Both teams are working. But not at the same pace. And that gap gets wider every time the deadline shifts.
The clock on the actual work doesn't reset when IRDAI moves the date.
Four things that have to be true before you go live
Ask your team the honest question: what would we be unable to finish if the current IRDAI deadline held? The answer shows up in four places. Each one looks like a workstream. Each one decides whether that workstream means anything.
Customer data clean-up
Pehchan ID mapping is in most project plans. What is not in most plans is the work that has to happen before mapping can even start. Cleaning up broken customer records across old core systems, CRM (Customer Relationship Management) tools, and partner databases that were never built to talk to each other is not a small job.
The plan assumes the data will be ready when the mapping layer needs it. That assumption is rarely checked. When it breaks, it breaks late, at the point where everything else is built and waiting. Fixing it at that stage is not a quick technical patch. It is weeks of clean-up work that was always going to take weeks, just left to happen at the worst possible time.
Bank partner readiness
Your plan shows your internal readiness date. Your actual go-live date is decided by the slowest partner in your bank network.
For large insurers that network spans dozens of relationships, each with its own tech team, its own sign-off process, and its own idea of what ready means. Picture week eleven of a twelve-week timeline. A partner's internal approval is held up. Their API environment is not certified. The date you have been telling the board is now sitting in someone else's hands. The partner lagging the most rarely gets mentioned in status calls. But they are the one who decides whether your launch date is real.
Bima Sugam India Federation (BSIF) sign-off
Sign-off appears in most plans as a single box between build and go-live. What most plans don't have is a backup for what happens when the first attempt fails. Failing on the first try is not unusual. Most teams only find out how long the retry actually takes when they are already in the middle of it.
The build choice your team is making right now
The first three are readiness risks. This one is different, and in my view the most important. It is a technical implementation choice being made right now, without being flagged up, that will decide what Bima Sugam costs you to run in year two.
Teams connecting bank partners to the platform have two options. One central connection point means one place to fix things when the platform changes. A separate connection for each bank is faster to set up today. Which makes it the easy choice when a deadline feels far away.
Bima Sugam has already changed since it was first set out. IRDAI has flagged roughly a dozen more changes coming in the next few months. An insurer running twenty separate connections at that point has twenty separate fixes, twenty timelines, twenty sets of sign-offs. The Bima Vistaar rollout, which got stuck as insurers tried to coordinate through a single shared change, is a live example of what that looks like in practice.
The cost of that architecture lands on whoever runs the platform in year two. This decision belongs with the technology leader, because the long-term cost is theirs to carry. And the window to change it closes when the build is done.
The question worth asking in your next team meeting
Not: are we on track? That question gets a confident answer that reflects what each team owns individually, not the gaps between them. The gaps live between teams. They only show up when someone asks across all of them at once.
For each of the four things above, who is the named person accountable, what is their current status, and when does their work need to be done for your timeline to hold?
If you can answer that for all four without being passed to another team first, you are managing the risk. If the answer needs a hand-off before it can be given, that is where the risk sits, whether or not the deadline moves.
The window that is still open
The tech leaders in the best position right now didn't start earlier because they saw something others didn't. They started because someone decided, before the pressure arrived, to treat the actual time the work takes as the real limit, and the IRDAI calendar as secondary to that.
The work has a floor that doesn't move just because the deadline does.
The gap is real. The person who exhaled when the last deadline moved is now two months behind the one who didn't. That distance is still closeable. But not for much longer.
If any of the four questions don't have a clean answer yet, that's what the webinar is for. Register here
Top comments (0)