Why So Many Life Insurance Policies Lapse in India — And What Agencies Can Actually Do About It

Persistency is the least glamorous number in Indian life insurance, and it's also the one that decides whether an agency is actually building something or just running in place. It measures the share of policies (or premium) still active at fixed checkpoints — the 13th month, the 25th, the 37th, the 49th, the 61st. In FY25, industry-wide 13th-month persistency for private insurers sat somewhere around 65-70%. Read that the other way: up to a third of policies sold don't survive their first renewal.

By the 61st month — five years in — that figure drops further, to roughly 45-55% for many insurers. Even the strongest performers show real decay over time. Tata AIA posted the best 13th-month persistency in FY25 industry-wide, at 88.05%, and its own five-year survival number was 56.7%. If the best insurer in the country loses close to half its book by year five, the industry-wide picture is sobering. In raw numbers, about 86 lakh individual non-linked policies lapsed across all life insurers in a single financial year.

What a lapse actually costs

It's worth being precise about what's lost when a policy lapses, because the damage compounds in a way that isn't obvious from the outside.

• The client loses coverage exactly when they've paid the most to acquire it and the least to keep it — the first year or two is when acquisition cost is heaviest relative to premium paid in.
• The agent loses the renewal commission trail, which for most life products is where the real long-term earning is, not the first-year commission.
• The insurer's own persistency ratio takes a hit, which affects everything from its cost of capital to how regulators and analysts view the book's quality.
• The agency loses the customer relationship entirely, often for good — a lapsed client rarely comes back to buy a fresh policy from the same agent who let the old one lapse.

None of that requires the client to have decided insurance wasn't worth it. Almost none of it does, in fact.

Lapses are mostly a process failure, not a decision

It's tempting to read a lapse as a customer choosing to stop paying — buyer's remorse, a cash crunch, a competitor's better offer. Sometimes that's true. But talk to agents who've actually worked a lapse-recovery list, and the far more common story is duller and more fixable: a renewal notice went to an old email address, a due date came during a month the agent was buried in new business and didn't circle back, a customer meant to pay but the reminder came once and got buried in a WhatsApp thread with forty other unread messages.

That's a tracking and follow-up problem, not a product or pricing problem — and it shows up most sharply in exactly the agencies that are busiest. An agent selling across six or seven insurers is juggling six or seven different portals, six or seven different due-date conventions, and usually one shared spreadsheet trying to hold all of it together. The bigger and more successful the book gets, the easier it becomes for any single renewal to slip through.

What the data says about where to focus

The persistency curve itself tells you where the leverage is. The steepest drop is almost always between the first and second year — the 13th-month mark. That's the single highest-value renewal to protect, because a policy that survives its first renewal is meaningfully more likely to keep surviving the ones after it. An agency with limited time and attention gets more out of tightening the 30/15/7-day renewal-reminder window around year-one policies than spreading equal effort across the whole book.

The second pattern worth noting: persistency doesn't fail evenly. It fails hardest exactly where administrative friction is highest — multi-insurer books, sub-agent networks where nobody owns follow-up clearly, and agencies still tracking renewal dates by memory or a shared Excel sheet nobody fully trusts.

What actually moves the number

The insurers with the best persistency aren't succeeding because their products are dramatically better than everyone else's. They're succeeding because renewal follow-up is systematic rather than dependent on any one person remembering. For an agency, the equivalent is having every policy's due date tracked automatically — regardless of which of a dozen insurers it's with — and reminders that go out on a fixed schedule (30, 15, 7 days out is the industry-standard cadence) whether or not the agent personally remembered to check.

This is exactly the gap GridGrowth was built to close: it reads the policy documents an agency already has, tracks every renewal date across every insurer in one place, and fires reminders automatically instead of leaving it to memory or a spreadsheet nobody opens on the right day. For an agency, protecting persistency isn't really a sales problem — it's an operations problem, and it's one that compounds in the agency's favor every single year a policy survives its renewal.