Value tree · Insurance

The insurance value tree

Insurance value is underwriting result plus investment return. The tree separates the two, then splits underwriting into the price you charged for a risk and what that risk actually cost.

Drivers 24 across four branches See also Insurance Metrics 12 linked

01 The same tree, this industry

Where the money is made and lost here

The structure does not change: value is profit plus how well that profit becomes cash, profit is revenue minus cost, and revenue is price times quantity. What changes is which drivers sit underneath each branch, and which system holds them. If you have not read the general version, start with the Enterprise Value Tree and come back.

What is different here

The distinguishing feature here is time. You set the price before you know the cost, sometimes years before, so every branch of this tree is really a question about the quality of an estimate — and about how quickly you learn that the estimate was wrong.

Every driver below names the metric it lands on. Follow one and you get its formula, the system the number lives in, and the ways it is commonly misread.

06 Where the numbers live

The systems behind the branches

A value tree is only usable once each box maps to a system and a record. These are the six that matter most in insurance: what each one is actually for, the records inside it the tree depends on, and which branch it feeds.

SystemWhat it holdsKey recordsFeeds
Policy administrationThe contract of record: cover, terms, endorsements and the premium actually charged.Policy, Risk, Endorsement, Premium, Cover sectionPrice, quantity, cash
ClaimsNotification through settlement, with the reserve movements that drive reported result.Claim, Reserve movement, Payment, Recovery, PerilCost, cash
Rating and underwriting engineThe technical price and the appetite rules, against which every written price is a deviation.Rating factor, Technical price, Referral, DeclinePrice
Broker / distributionWho placed what, on which terms, and the commission and bordereaux behind it.Intermediary, Agreement, Bordereau, CommissionPrice, quantity, cash
Actuarial and reservingDevelopment triangles, IBNR and the assumptions the balance sheet rests on.Triangle, Cohort, Assumption set, Model runCost, cash
Finance and regulatoryThe ledger and the solvency returns, which have to reconcile to all of the above.GL account, Solvency return, Capital requirementCash

Almost every hard question in insurance needs two of these joined. That join — not the calculation — is the work.

07 Where it leaks

Value lost between two systems

These are the losses that no single system can see, because the evidence is split across two of them. Each one is a real number that stays invisible until the join exists — which is why the tree is an integration exercise before it is an analysis one.

Where value leaksWhy it happensThe join that finds it
The policyholder who is also the claimant, twicePolicy and claims systems hold the same person under different identities, so cross-policy fraud patterns and true customer profitability are both invisible.Resolve party identity across policy, claim and intermediary records
Technical price versus written priceThe rating engine produces a price; the front line writes another. The deviation is the margin story and it is rarely reported as a distribution.Join technical price to written premium at policy level, every renewal
Broker performance measured on volumeCommission is paid on premium written while profitability depends on the claims that follow, two systems and eighteen months later.Join intermediary agreements to developed loss ratio by cohort
Claims leakage invisible between handlersSettlement variation by handler, peril and region is a large, recoverable cost that no single claim reveals.Join settlement amounts to reserve history, handler and claim characteristics
Reserving learns slower than pricing needsPricing is refreshed annually from data the actuarial cycle has not yet developed, so last year's error is repeated before it is known.Join emerging claim experience back to the rating factors that priced it

08 Worked example

Growth that arrived as loss ratio

In practice

Gross written premium grew 11% and the combined ratio worsened by two points. The tree separates it: the growth came through one channel writing consistently below technical price, retention was bought with discount on the profitable segment, and the reserve development on the prior year turned adverse in the same peril.

ComponentEffectWhat sits behind it
Premium growth+€8.9m11% growth, concentrated in one channel
Rate against technical−€3.6mWritten consistently below the rating engine
Renewal discounting−€1.8mApplied to the profitable segment
Claims frequency−€2.9mSegment mix, not weather
Prior year development−€2.2mAdverse on the same peril
Net−€1.6mGrowth that cost two points of combined ratio

Illustrative figures, shown to demonstrate the split. The point is the shape of the walk, not the numbers — on your own data the same bridge is built from your ledger.

09 Diagnostics

Six questions to ask in insurance

Ask them of your own team before anyone asks them of you. In most organisations at least two of these cannot be answered without a manual exercise, and those two are the plan.

  • What is the distribution of written price against technical price, by channel?
  • Can you measure profitability by intermediary on developed losses rather than on premium written?
  • Do policy and claims systems agree on who the customer is?
  • How quickly does emerging claims experience reach the pricing team — in weeks or in annual cycles?
  • What proportion of claims cost is leakage, and could you evidence that number?
  • Which segments are growing, and are they the segments your reserve development says are profitable?

11 Questions

Frequently asked

Why does insurance need entity resolution so badly?

Because the same party appears as a policyholder, a claimant, a driver and sometimes a beneficiary, across systems that were never designed to agree. Fraud detection, customer profitability and cross-sell all depend on that resolution being right.

Is the pricing branch really about data quality?

Largely, yes. Rate adequacy depends on knowing the risk you wrote, and that knowledge lives in the completeness and accuracy of the risk data captured at quote. Missing or defaulted rating factors are priced as if they were average, and they are not.

How does the cash branch differ from other sectors?

The cash arrives before the cost is known, which inverts the usual working capital question. The scarce resource is capital held against uncertainty, so reserve accuracy is a cash metric as much as an accounting one.

Where do most insurers start?

With the party record, then with technical price against written price. The first makes every other analysis possible; the second usually pays for the programme within a renewal cycle.

See this tree on your own data

Connect the systems above, define each box once, and the tree stops being a slide.

Book a live demo