Insurance is a financial system.
INTX is built to run it.
What is INTX?
INTX provides dedicated technology for both sides of the reinsurance transaction: INTX ReinsureConnect for ceded, INTX Re for assumed.
With INTX Core, its P&C insurance operating platform, it connects underwriting, policy administration, reinsurance, claims, financial operations and reporting in one modern operating environment.
The problem.
Underwriting in the System, Claims in another.
Reinsurance held together across spreadsheets.
One data model. Reinsurance that executes instead of reconciles.
That is a real answer to a real problem. The question every Bermuda and Cayman CIO asks next is who supports it here.
70%+
of insurers still run critical processes on Excel or homegrown systems, with over half of policy workflows needing manual intervention.*
3–8%+
of ceded premium is the value at risk once you count structuring, treaty execution, accounting accuracy and capital utilisation.*
2-3
disconnected core systems is what a single platform is replacing, which is also what makes the migration the hard part.*
*Source: INTX
WERE WE COME IN
BESPOKE KNOWS THE MARKET
BSCR, EBS and CISSA in Bermuda. CIMA Class B and C in Cayman.
We have worked to this filing calendar for twenty years, so scoping starts at the second question rather than the first.
WE KNOW THE BUSINESS
Treaty structures, loss corridors, bordereaux, commissions, the quarterly close. You will not spend the first three weeks explaining a loss corridor to your implementation team.
WE KNOW THE DATA
We know the source systems running on this island, what they hold, and what they will and will not hand a new core. Twenty years of moving Bermuda and Cayman insurance data between them.
WE ARE HERE
On-island support in your hours, for implementation and for everything after it. Not a ticket queue in another hemisphere
Across the whole software lifecycle
01
IMPLEMENT
Readiness, data mapping, migration of history, cutover.
We find what your systems will not give INTX while it is still cheap to fix.
02
RUN
Quarter-end support, reconciliations, change requests, and someone on-island who picks up. The period most partners treat as handover is the period we treat as the job.
03
EXTEND
New lines, new products, new entities. Growing what INTX covers for you without a second implementation.
Why on-island matters at quarter-end
Reporting problems do not surface in a sprint review. They surface at close, against a filing date, at the end of a week that is already long. At that moment what matters is whether your support partner is awake, whether they know your data model, and whether they can be in the room. The people who built yours are on the same island, in the same hour.
AND THE NUMBERS STILL HAVE TO BE DEFENSIBLE
One data model is what INTX gives you going forward.
The evidence trail behind it comes from the migration, the reconciliation of history, and the lineage from source to filing.
We build that in during the implementation, because the first quarter after go-live brings the same three questions it always brings.
-
Where did this number come from.
-
Who changed it.
-
Why does it differ from last quarter.
WHAT CHANGES
Before
After
Quarter-end is a review run against a documented lineage anyone on the team can follow.
Reporting is built once and re-pointed when sources move.
Quarter-end is a fire drill run by three people who know where the bodies are.
“We think it's right.”
Reporting is rebuilt every time a source system changes.
“Here is where it came from, here is what changed, here is who signed it.”
WHERE IT STARTS
A two-week readiness assessment, before anyone commits to a migration plan.
Week 01
We map what your systems will actually
give INTX
Policy, claims, treaty, general ledger, actuarial. We find the gaps while they are still cheap to fix.
Week 02
You get the assessment, the sequence, and an honest answer on timing
A written readiness assessment, a sequenced implementation plan, and a recommendation you can act on or sit on.
Fixed scope. Fixed fee. If the answer is that you are not ready this year, we will say so in writing.
