Policy, underwriting and claims
Life, funeral, pet and short-term cover. Underwriting management, third-party administration and cell captive structures.
Core platforms built and supported since 2005.
Since 2005 we have built and supported platforms for insurers and regulated lenders in Africa, the United Kingdom and Europe. The work spans pricing, claims, collections and reporting.
Core platforms in continuous production since 2005
2005first platform live
Multiple carriersinsurers and regulated lenders
Africa & Europethree supervisory regimes
Rand & euromulti-currency administration
Client agreements limit what we can publish about core platforms. We describe the work here and can discuss relevant systems in more detail when permissions allow.
What sits behind a core platform.
A policy administration system is never one application. It is a quote engine. A rating structure holding every version of every product rule ever priced. An endorsement history that can reconstruct a policy exactly as it stood on any date a regulator asks about. A collection run that touches every account on the same morning and cannot be late.
Around it sit the brokers, the bureaus, the payment providers and the reinsurers—each with its own file format, its own settlement cycle and its own view of when a month ends. The platform has to make them agree, to the cent, before anyone opens a report.
That is the class of system we have built and run since 2005. The demanding engineering is rarely the screen. It is the reconciliation.
Insurance and lending work we know.
The work runs from product configuration through to regulatory reporting. It has to keep running while we change it.
Origination, servicing and collections
Platforms for regulated consumer lending: decision workflow, payment handling and arrears. Reporting shaped by regulatory requirements.
Partners, portals and APIs
Broker, adviser, affinity and aggregator models—connected by partner platforms, integration and daily reconciliation.
Long-term production responsibility
We do not hand over and leave. Architecture, migration, release and support continue for as long as the platform earns its place.
Types of programmes we undertake.
These examples show the kinds of programmes we undertake. We can discuss specific systems and outcomes when client agreements permit.
Replace the core without stopping the business
A carrier cannot pause renewals to change systems. We migrate in slices, reconcile every financial position and cut over in controlled cohorts.
Connect the lending lifecycle
Origination, servicing, collections and reporting on one operating model—shaped around the lender's products rather than a packaged workflow.
Make a multi-party model operate as one
Brokers, aggregators, bureaus and payment providers behave like separate businesses because they are. The platform has to make them settle as one.
One platform, several regulators
Data residency, consent, retention and reporting differ by market. We handle that per jurisdiction without forking the product into unmaintainable variants.
Questions to ask about our experience.
Production duration
How long the platform has operated and how it has continued to change.
Migration and reconciliation
How data, integrations and financial positions were moved and verified.
Operational consequence
Which processes depend on the system and what controls make that dependence safe.
Relationship continuity
How engineering context and responsibility were carried beyond the initial release.
Discuss experience relevant to your system.
Tell us the platform, operating model and risks you need a prospective engineering partner to understand.