I build systems for insurance intermediaries — brokers, corporate agents and agency networks: policy and renewal tracking, commission reconciliation across insurers, client servicing records and audit-ready compliance trails.
What is a broking desk’s actual asset?
The renewal book. Not the new business pipeline, not the relationships in the abstract — the specific list of policies coming up for renewal, with enough lead time to act. Almost every broking business is worth roughly what its renewal book is worth, and almost every broking business manages that book in Excel with reminders held in one person’s head.
The consequences arrive in three forms. Renewals slip, and a lapsed policy is a client who has learned they can survive without you. Commissions arrive from six insurers in six formats and reconcile to none of them, so the gap between what you earned and what you received is never measured. And claims support lives in call memory, which means the thing clients judge you on most has the weakest record behind it.
The commission gap deserves particular attention, because it is the quietest loss in this trade: money you have already earned, on business you have already placed, unreceived because nobody compared expected against actual. It requires no selling to recover — only arithmetic.
What does the system cover?
- Policy register. Every policy, every endorsement, every renewal date, with escalating reminders that begin early enough to matter. Multi-line desks get per-line rhythms rather than one template.
- Commission reconciliation. Expected — computed from rates against premiums — against received, per insurer statement, with gaps queued and chased with evidence. Statement normalisation across insurers is built in, because that is the actual obstacle.
- Client servicing timeline. Every interaction, document and instruction logged per client, so claims support becomes a record rather than a recollection.
- Claims tracking. Status, documents and follow-ups against the policy, through to settlement.
- Sub-agent and POSP networks. Hierarchies with their own splits, tracked and settled on statements both sides can read.
- Compliance trail. Solicitation records, disclosures and communications organised in the shape an IRDAI query expects.
Why renewals and commissions are the same problem
Both are failures of a list that nobody owns. The renewal list exists in principle — the data is in the policy records — but without a system generating it daily and assigning it, it becomes whoever-remembers work, and it competes with new business, which feels more urgent and is more fun. The commission list is identical: the expected figure is computable from data you already hold, but comparing it to six insurer statements every month is nobody’s preferred afternoon.
That is the structural insight worth acting on. Neither problem needs judgment, negotiation or skill. Both need a list produced automatically, sorted by value and age, with a name against each line. It is the least glamorous kind of systems work and, in this trade, the most directly profitable — because you are collecting revenue you have already earned and retaining clients you have already won.
The reconciliation discipline I bring to payments applies almost unchanged here: normalise the feeds, match automatically, queue the exceptions with reasons, and age them visibly. An insurer statement is just a settlement file with different column names.
The same is true of the renewal book: it is a maturity schedule, and maturity schedules are exactly what lending systems manage well. Neither problem is novel — they are simply unattended, because attending to them by hand is nobody’s afternoon.
Related reading
/industries/financial — the money-first umbrella · /industries/subscriptions — recurring-revenue mechanics · /blog/reconciliation-at-scale — the matching method · /products/whatsapp-automation — renewal reminders clients actually read
How many renewals slipped last quarter?
If the answer is “pata nahi”, that number is both your churn and your recoverable revenue — and it funds the system on its own. /contact.
Questions I actually get
Can it normalise statements from six different insurers?
Yes — and doing so is roughly half the product's job. Every insurer exports commission statements in its own dialect, and reconciling them by hand is why commission gaps go unnoticed. Once normalised into one comparison plane, expected against received becomes a report rather than a project.
POSP and sub-agent networks?
Sub-agent hierarchies with their own commission splits, tracked to the rupee, with statements they can read. Network disputes are ledger disputes; a shared ledger settles them faster than any phone call.
How hard is migration from Excel?
The renewal book imports in days and the reminders start immediately, which is the fastest payback in this vertical. Historical commission reconciliation can follow once the forward-looking book is safe.
Does it help with IRDAI compliance?
It maintains the records a query expects — solicitation trails, disclosures, policy documents and client communications, organised per policy. Your compliance owner handles the filings; the system makes the evidence retrievable rather than reconstructable.
What about claims support?
Claims are tracked as a timeline against the policy, with documents attached and status recorded. Claims support is where broking relationships are actually won, and it is usually the least systematised part of the desk.
Multi-line desks — motor, health, corporate?
Each line has its own renewal rhythm, commission structure and documentation, handled per line rather than forced into one template. A motor book and a corporate group-health book have almost nothing operationally in common.