Insurance Hub is one operating layer between your channels and your insurance partners — advice, distribution, servicing, claims and reporting, configured by your own teams.
Runs on your infrastructure. Your data and your models never leave the bank.
Banks want to grow insurance distribution without starting a new technology project for every insurer, product and journey. Today, growth adds cost faster than it adds premium.
New integrations. New journeys. New testing. New releases.
Months between a commercial decision and a sellable product.The bank sells the policy, but proving what was advised and why can be difficult.
Complaints defended on memory rather than record.A customer takes a loan, and the moment to offer relevant protection passes unused.
Premium never written, on business already on the books.Relationship managers navigate insurer systems and institutional memory.
Renewals and recoverable collections quietly lost.Multiple portals. Multiple workflows. Multiple operating models.
Distribution capacity spent on administration.Policy, premium, renewal, claims and commission data sit across systems.
Decisions made on last month's numbers.Each insurer arrives with its own portal, its own journey and its own way of working. The bank stitches them together with people.
One operating layer. Your channels sit above it, your insurance partners sit below it, and the bank owns everything in between — the customer, the journey, the evidence and the book.
Understand the need, compare the panel on that customer's own details, record the advice and issue the policy — with the reasons written down.
Offer relevant protection inside the loan journey, priced on the balance outstanding, with declines recorded rather than lost.
Collections, grace periods, endorsements, renewals, documents and customer messages — on rules the bank sets.
Claims with separated assessment and approval, payouts, commission, reconciliation and reporting that traces back to the row it came from.
Quote. Needs captured once, the whole panel priced on that customer’s own details, side by side.
Products, pricing, suitability, journeys, rules and controls are configuration — changed by your teams under approval, not by a vendor ticket in the next release window.
A loan is the clearest moment a customer has a protection need — and the moment most banks miss, because insurance lives in a different system.
Reducing-balance cover on what the borrower actually owes, over the loan's own tenure — not the sanctioned amount.
Products declare the lending lines they attach to, so the wrong cover is never offered against the wrong loan.
Declines are recorded with a reason, and an uncovered loan lands on a follow-up queue with an owner against it.
Where cover needs the insurer’s decision, the counter is told in plain words that the loan is not covered yet. The loan is marked as covered only when approval lands. It is a small sentence that prevents the most common complaint in this channel.
Insurance Hub reads the book every morning and turns it into the things a person should actually do today — renewals to price, collections still recoverable, loans without cover, applications waiting on an insurer. Every number is computed. Nothing is done unattended.
Disbursed loans carrying no protection, with the lending line and the balance outstanding against each.
Renewals falling due with no offer made, offers the customer has not answered, premiums overdue but still recoverable, policies past grace, loans with no cover, applications sitting with an insurer.
Price every due renewal, chase every unanswered offer, retry every recoverable collection — in bulk, on request. The alert a person reads and the button that acts are the same list, so it can never touch a case the alert did not show.
Where the desk is set up in a way that costs money — a lending line attaching far below the rest of the book, a referral rule that has never once declined — with the evidence, the change, and what it should be worth.
Plain questions about the book, answered from the bank's own records with the underlying figures shown. A question it cannot answer from data is refused rather than guessed.
A rule is a trigger, an action, and a limit. Below the limit it acts. Above it, the case is written onto that customer’s file with the reason it stopped.
Move the limit. The sentence and the split change with it — this is the preview a bank sees before switching a rule on.
“When a premium is overdue and the policy is still inside grace, retry the collection — unless the exposure crosses ₹1,00,000. Then tell a person.”
Every figure in Insurance Hub is computed and traceable. AI is used to draft language and surface work — never to produce a number, and never to make a decision on a customer.
It runs on the bank’s own model server. Every generated paragraph can show exactly what it was given. And the platform works with AI switched off entirely.
Insurance touches money, advice and customer data. Insurance Hub is designed so a supervisor, an auditor or a complaints officer can reconstruct what happened without asking anyone.
The platform and its database run on the bank's own infrastructure. No customer data is sent to a third-party service.
Models run on the bank's own server. The bank chooses which model does language work, from those it has installed — or none.
The bank distributes and advises; the insurance partner underwrites and approves product changes. Neither can perform the other's act.
Documents are captured at issue and never rewritten. Advice records the version, the actor and the disclosures confirmed.
Manual, bulk and automated actions all write to the policy's own history — including the cases a rule declined to act on.
Product versions and commission terms carry effective dates, so what applied on a given day is always recoverable.
Insurance Hub deploys as a single application and database on infrastructure the bank controls, on-premise or in the bank’s own cloud tenancy. We are happy to work through your security review before any commercial conversation.
We would rather be measured on one number in one quarter than sell a platform programme.
One lending journey, or one advised product.
One branch cluster — enough volume to be real.
One or two insurance partners.
One measurable result, agreed in writing before we begin.
Example outcome: increase the insurance attach rate at lending.
Baseline X% → with Insurance Hub Y%Both agreed with the bank before the pilot starts.
Alongside it we track customer conversion, branch and relationship-manager effort, time to launch a product, advice and evidence completion, and servicing effort.
Insurance Hub is early. That means direct access to the people building it, influence over the roadmap, and pricing that reflects being first. It also means we will tell you plainly what is built, what is not, and what a first deployment involves.
A paid 90-day pilot: one lending journey, one branch cluster, one or two insurance partners, and a single measurable outcome agreed before we start.