Insurance technology consulting covers policy administration, agent hierarchies, commission calculation, renewals and claims workflow. For most agencies and brokerages the work is replacing a critical spreadsheet, the one holding commission logic that a single person understands, with a system that computes it, records why, and survives that person leaving.
Insurance businesses run on rules that grew by accretion. Commission splits negotiated per agent, overrides for a hierarchy three levels deep, renewal terms that differ by product and vintage. None of it is complicated individually. All of it lives in one spreadsheet, maintained by one person, and nobody else can explain it.
That is not a technology problem until the person is on leave during renewal season. Then it is the only problem.
A policy ERP that models the business as it actually operates: products with their own terms, an agent hierarchy that reflects real reporting lines, and commission calculated by rules that are written down, versioned and auditable rather than embedded in formulas.
Around it, an agent portal so the field stops phoning head office for statements, renewal tracking that surfaces lapses before they happen, and a claims workflow with a status any party can see.
A customised dashboard covering book value, persistency, agent performance and commission liability, computed from the same records the operational system runs on. One version of the truth, rather than a monthly reconciliation between two.
This was the shape of the ERP built for CV Financial Architect: a single portal covering the whole insurance operation, with the dashboard on top rather than beside it.
The platform had been half-built on an ageing CodeIgniter 3 codebase with an unoptimised schema, no documentation and pending integrations with external verification partners. We redesigned the data model, rebuilt the application on CodeIgniter 4, and reworked every investor flow behind encrypted APIs.
Anything not answered here, ask me directly on the call.
Yes, and complexity is the normal case rather than the exception. Multi-level hierarchies, per-product rates, overrides, clawbacks on early lapse and grandfathered terms all get modelled as versioned rules, so a historical calculation can still be explained two years later.
Because the insurer portals show you their slice. Nothing shows you the book across every insurer you place business with, which is where agency-level questions about persistency, agent performance and commission liability actually get answered.
It gets migrated, and the migration is where the real work is. Spreadsheets accumulate exceptions that were never written down, so extracting the rules from the formulas and confirming them with whoever maintains them is part of the engagement, not an afterthought.
Four to twelve weeks to a first usable release, depending on how many products and how much history is being migrated. Policy administration and commission usually come first, because they are where the operational pain concentrates.
Thirty minutes, no pitch. Describe what is not working and I will tell you whether the pattern above is yours, and what the first move should be.
