Part 1 argued that insurers price everybody else's risk and have never priced their own, and that two unmeasured limits, a cost floor and a fixed product mould, now decide how much of the market they can reach. This part is about the five people who have to agree before either limit moves, and the single operating model all five can say yes to. It closes with one page any carrier can lay over its own operation before speaking to anyone.
The argument in 60 seconds
- Part 1 left two engines stalled: affordability (the floor) and customisability (the mould). Both are set by structure, legacy systems and the time it takes people to decide. This part is about the third.
- Five people must agree to any change in how an insurer works. Each protects something real, and "not yet" is a rational answer for all of them, because none of them has the two numbers that would settle it: what the work costs, and how long it takes to change.
- Write down what would change each answer and you get one specification: a configuration layer where a product is parameters rather than code, governed AI agents running the work against those rules, and continuous optimisation on live behaviour. It sits beside the existing core and can be switched off without a migration.
- The evidence is public. One listed digital insurer added 1.2 million customers since late 2022 while its headcount fell 6%.
- The ask is the Reach Canvas, printed here in full. Fill it for one line of business, then talk to us about what it shows.
Seventy per cent
You have heard the number: seventy per cent of transformations fail. It turns up in steering committees, in board papers, and in the careful email explaining why the pilot will not be extended this year.
It has no evidence behind it. The figure comes from a 1993 book on business re-engineering, where the authors offered what they called their "unscientific estimate" that 50 to 70 per cent of re-engineering efforts fell short of the dramatic results intended. Two years later one of them, writing with a co-author, called it a descriptive observation that had been distorted into a rule. In 2011 a peer-reviewed study traced five published versions of the claim back to their sources and found no valid, reliable empirical basis for any of them.1
Thirty years and thousands of citations later, an unmeasured number is still being repeated as a reason not to act. I cannot tell you how many decisions it has changed, and I will not pretend to. I can tell you I have heard it quoted in the room, more than once, by people with no idea where it came from. An industry that has never measured its own cost of change is being steered by a statistic nobody measured either.
Part 1 ended on three layers (structure, legacy, and the time it takes people to decide) and promised that the third would be the subject of this piece. So, into the room where those decisions are made.
01The five people in the room
Every meaningful decision about how an insurer works passes at least five chairs. There are usually more, a group function, a joint-venture partner, a distribution head with a view, but these five recur, and the same five sit inside every administrator, claims operator and reinsurer in the chain.
I have sat across from all of them. None is a blocker. Each protects something that needs protecting, and each answer is correct when judged by what that person is measured on. The right-hand side of each card is a specification, and the orange line beneath it describes what meets it. An interest to declare: Gangkhar builds an operating layer of this kind, which is why what follows is written as configurations and use cases rather than as a product pitch. If the mechanism is wrong, the vendor does not matter.
"We ran a programme like this. Three years, eight figures, and we are still reconciling in spreadsheets."
Measured on: stability, delivery against plan, and never being the reason the quarter went wrong.
What changes the answer: something that runs alongside the existing core, proves itself on one workflow, and can be switched off without a migration.
In practice: a configuration and operating layer beside the policy administration system, reading from it and writing back. One workflow first, the core untouched, nothing migrated."Show me what this does to next year's numbers, not the ones after I have gone."
Measured on: results inside a shrinking horizon. Average global CEO tenure fell to 7.1 years in 2025, from 8.3 in 2021.2 A four-year payback is somebody else's payback.
What changes the answer: a result inside four quarters, in the units the board already uses, with the option to stop after the first.
In practice: one product, one channel, one quarter, reported as cost per policy-year, attachment, retention and service levels."If this works, the business gets the credit. If it fails, it is my name on the incident report."
Measured on: losses that happen, never opportunities that do not. No risk officer was ever promoted for a policy written faster.
What changes the answer: automation that is governed: every decision logged, every rule checked against live product terms, a human in the loop where it matters.
In practice: decision rights, validation against the filed rules at the moment of each decision, escalation thresholds, and an audit trail written by default."It works today. I know exactly what it costs me in people, and I know what happens the week it breaks."
Measured on: service levels, backlog, the absence of complaints. The only person in the room who knows how the work actually flows.
What changes the answer: running the new beside the old on live volume, with their own team judging the result. Their people move to the work that needs judgement.
In practice: one queue (renewals, servicing or first notice of loss) run in parallel, with the team's own output as the benchmark and the team deciding whether it passed."Show me how you would explain this to the regulator, in writing, a year from now."
Measured on: defensibility, and they are right to be careful. In a 2026 survey of around 100 insurance executives, 44% said governance or compliance problems had contributed to an AI project failing or underperforming, and only 24% were very confident of passing an independent AI governance review within 90 days.3
What changes the answer: governance built into the machinery, with decision rights, evidence and escalation inside the system.
In practice: every automated action carries its rule, its evidence and its approver, so the file a regulator asks for next year exists on the day the decision is taken.Read the "what changes the answer" lines end to end and you have a single specification: beside the core, one workflow first, governed, measured in the board's units, and reversible. Nothing in it is exotic, and nothing in it requires replacing a core system.
02Why five right answers make a wrong one
Put those five in a room and something quietly illogical happens. Each protects their own exposure, five reasonable cautions add up to a veto, and the outcome nobody chose becomes the outcome everybody gets. This is not a failure of character. It is a well-documented feature of how people decide.
The pull of the default
In 1988 two economists showed that people stick disproportionately with whatever is presented as the existing arrangement, and that the advantage of the status quo grows as the number of alternatives rises.4 The more options a committee is shown, the likelier it is to choose none of them.
Insurance has seen this at scale. When New Jersey and Pennsylvania offered drivers a choice of motor cover in the early 1990s, each with a different default, only about one New Jersey driver in five and about one Pennsylvania driver in four moved off the default they were given, despite real differences in price and cover.4 The industry has relied on that behaviour ever since; it is part of why renewal books are as sticky as they are. We have been earning from our customers' status quo bias for thirty years while being governed by it ourselves.
Everyone thinks the room agrees with them
BCG's research into how change works, drawing on 6,000 executives and employees across fifteen countries, identifies false consensus as one of the behavioural traps behind stalled change: leaders assume their own view is widely shared. In that research 68% of executives, against 45% of employees, said they felt positive about change in their organisation.5
Read that beside the five chairs. Everyone leaves the meeting believing the others are broadly on board, and each waits for someone else to move. Nothing is refused and nothing happens, which is the most expensive outcome available and the only one that never appears in the management accounts.
So the useful question is what single piece of evidence would answer all five at once, and what would have to exist for that evidence to be worth having.
03The engine, in configurations
One operating model answers all five chairs, which is why it can get through the room at all. Every "what changes the answer" above is a property of the same engine: beside the core, one workflow at a time, governed and reversible.
It does not involve replacing the core. Core replacement is where the first chair earned their scars, and lowering the floor no longer requires touching it. Three layers of capability now sit above whatever a carrier already runs. Part 1 promised an engine built in modules, where a new product shape is assembled rather than rebuilt, so that customisation stops raising the cost of a policy. The clearest way to describe it is by what can be configured in it.
A product becomes parameters: coverages, rules, pricing, eligibility, partner and channel, defined once and changed in days, with the operation behind it configured in the same place. A new variant stops being a build, so customisation stops raising the floor.
Quote, issue, service, first notice of loss, claim and renewal run as operating modules, executed by AI agents that are checked against the product rules, with decision rights, audit trail and human escalation designed in. This is what takes the fixed cost out of a small policy, and it answers chairs three and five.
Price, offer, message, journey and workflow are tested continuously against live behaviour instead of being set once a year and defended. The results are reported in the units the second chair asked for.
At Gangkhar these three layers are Sherpa+ (product configuration and rules), Sherpa+Works (the governed agent fleet) and Sherpa+Lens (continuous optimisation). The mechanism matters more than the names, so the rest of this section stays with the mechanism.
What is actually configurable
"Configuration" has been used loosely enough in this industry to mean very little. Concretely, these are the nine surfaces that stop being code and become parameters, each editable, versioned, and checked against the filed product before it goes live. Unlike the use cases further down, this list is meant to be complete: between them the nine cover the life of a policy from definition to reporting. Any step in your operation that falls outside all nine is exactly where a launch will stop.
| Surface | What becomes a parameter |
|---|---|
| Coverage and benefits | Perils, limits, sub-limits, deductibles, waiting periods and exclusions, added, removed or resized independently |
| Eligibility and underwriting | Question sets, acceptance rules, referral thresholds, evidence requirements, auto-accept bands |
| Rating and pricing | Factors, tables, loadings, discounts, the signals feeding them and how often they are re-read |
| Duration and trigger | When cover starts and stops, and what attaches it: a trip, a shift, a delivery, a season, a contract, a life event |
| Channel and partner | Endpoints, journeys, quote and attach logic, branding and commission terms, per partner |
| Servicing and lifecycle | Endorsements, beneficiary changes, payment holidays, reinstatement, renewal offers |
| Claims adjudication | Evidence rules, auto-pay thresholds, fraud checks, exception routing, human-in-the-loop points |
| Collection and settlement | Frequency, method, retry logic, currency, reconciliation and commission disbursement |
| Reporting feeds | Partner, regulatory, bordereaux and delegated-authority reporting, generated from the same rule set |
A product is the combination of the nine, not a block of code. Change one surface and nothing else has to be rebuilt, which is the whole of the modularity claim, stated so it can be tested.
Six use cases, and the Part 1 problem each answers
Configuration matters only for what it lets an insurer sell and run that it could not before. These six were chosen because each closes a gap named in Part 1. The better ones usually come from inside a book someone already knows.
Configured: cover per shift, trip or contract, eligibility read from the platform's own data, premium collected inside the transaction, and cover that ends without a cancellation process.
Answers the 91% critical-illness protection gap among platform workers in Singapore, and a floor that exists because a policy costs much the same to administer at S$900 as at S$9.Configured: one benefit module covering a single band (a co-payment range, a deductible, a network shortfall), eligibility keyed to the base plan already held, and a premium far below that of a full policy.
Answers the second letter in Part 1. A household whose cover was trimmed is offered nothing between "full plan" and "no plan". This is the smaller slice it would take.Configured: one rule set and four parameter sets (direct, bancassurance, employer scheme, and embedded at a partner's checkout), each with its own limits, journey, pricing and commission, none a separate build.
Answers the shelf problem. One new life policy in ten in Singapore is bought online for 1.2% of premium because the online shelf carries one small shape. This is how it gets stocked.Configured: rating factors fed by live signals rather than a one-off declaration, the re-rate cadence, caps on price movement, and the fairness and filing limits every movement stays inside.
Answers the risk priced on a form filled in three years ago. The limits are themselves a configuration, so the regulator's question is answered by the same mechanism.Configured: adjudication rules, evidence thresholds, the value below which a claim pays automatically, what routes to a person and when, and the audit record each step writes.
Answers risk one, the cost of the work, and produces the cost of a claim from notice to payment as a by-product rather than a study.Configured: the reporting feed itself, its schema, frequency and the mapping from live policy and claim events to the bordereaux each capacity provider expects, generated from the rule set instead of assembled by hand each month.
Answers risk two, the business never written. Capacity follows visibility: a book that can be watched live can be backed more heavily.None of this requires the policy administration system to change. It needs a layer that reads from the core, writes back to it and runs the work around it, which is why a first workflow can go live in weeks or a few quarters rather than years (about six weeks of technical build for an embedded programme, longer for an enterprise back-office workflow), and why it can be stopped without a migration.
That last property is the one that makes "yes" available to someone who has said "not yet" for a decade. It is also what Part 1 asked for: a floor that can be lowered and a mould that can be broken in the same programme, because the engine was built in modules.
04The proof, and the arithmetic
None of what follows is a forecast. Every figure was published by the organisation that produced it, and where a number is company-reported rather than independently audited, I say so.
The floor moving, in public
The clearest evidence sits in a listed company's shareholder letter. Between the third quarter of 2022 and the end of 2025, Lemonade, a digital insurer, added 1.2 million customers while its headcount fell 6%. Its customer count grew from about 1.78 million to 2.98 million over that period, in-force premium reached US$1.24 billion, up 31% year on year, and premium per customer rose 7%.6
Read together, that is what Part 1 said rarely happens in insurance: far more customers, served by fewer people. Cost per customer did not fall because somebody negotiated harder with suppliers. It fell because the work changed shape.
Source: Lemonade Inc., Q4 2025 shareholder letter. Company-reported.
Speed, at scale, in this region
Ping An Life reports that 93% of its policies are underwritten within seconds, and that its quick-claims service closes an average life and health claim in 7.4 minutes.7 These are company-reported figures from a group serving more than 250 million retail customers.
Set that against the benchmark from Part 1: an average of 40.7 days to final payment on US homeowners' property claims in J.D. Power's 2026 study, and that after a year of improvement.9 Different lines and different markets, so the comparison is not like for like. It still shows how far apart the two operating models are.
And it is not only the digital natives
Zurich has reported cutting underwriting triage time from around 75 minutes to around 15 in an agentic AI rollout across five countries. At Sabadell Seguros, its Spanish joint venture, a voice-analytics tool is credited with lifting customer retention by close to 20%.8 Both figures are company-reported, and they show a direction of travel rather than a guarantee. The retention figure matters most here, because it is growth: the same book, kept.
An illustration, not a forecast
Take a hypothetical Singapore carrier administering 500,000 policies with 400 people in operations, at a fully loaded cost of S$120 per policy-year (S$60 million a year). Suppose it grows its book by 40%, a more cautious pace than Lemonade's 68% customer growth over the period above, while operating cost stays flat and headcount drifts down 6% through attrition. It would then serve around 700,000 policies with about 375 people.
Cost per policy would fall to roughly S$86, a 28% reduction. On Part 1's argument that is the floor dropping 28%, which brings every household whose premium sits in that band inside the addressable market for the first time.
Assumptions, stated plainly: the 500,000 policies, 400 staff, S$120 cost per policy-year and 40% growth are illustrative. No Singapore carrier publishes these figures, which is why the canvas below asks for them. Lemonade operates in a different market, product mix and regulatory regime, so its ratio will not transfer cleanly. This shows the shape of the opportunity, not a projection of anyone's results.
The honest position is this. The evidence that the floor can move is public. What nobody can yet say is how far it moves in this market, for this product mix, under this regulator, because the starting point has never been measured, by us or by anyone else. That is what the next page is for.
05The Reach Canvas
Everything above remains an argument until someone lays it over their own operation. Here is the instrument in full, with nothing held back for a meeting.
One page, one line of business, one working session. Read it left to right along the top: the floor, then the mould, then where the two together put you. Below sits what is holding it, then what it costs you and what you would do about it. Fill it with all five chairs in the room. The point is less the answer than all five looking at the same page at the same time.
- Fully loaded cost to run one policy for one year
- Cost to take one claim from notice to payment
- The premium below which neither is covered
- Days from decision to first policy sold
- Time to change one rule and have it live
- Configurations against builds, last 24 months
- What was proposed and never shipped
- Structure: the economics did not work at the size it needed
- Legacy: the systems could not carry it in time
- Decision: it simply never got decided
- One segment not served today, by income, employment shape, business size, or a need too small for the shelf
- Its population, the premium it would bear, the cover it would want
- That premium set against the floor in 01
- Which coverage modules, which eligibility rules
- What trigger and duration, which channel
- What claims path, what reporting
Six blocks, one page. Part 1 closed with three questions; this is what they become when taken seriously. Nothing on it requires a vendor, a budget or a decision.
If the canvas comes back with a low floor, a short time to market, an empty never-shipped list and a small unreached segment, the argument in these two pieces does not apply to you, and I would like to meet you for an entirely different reason. If it does not, you are holding something the industry has rarely had in writing: the shape of your own unpriced risk, on one line of business, on one page.
06 · What we are asking
Fill the canvas for one line of business, then talk to us about what it says.
The canvas needs nobody's permission and no budget, and everything written on it belongs to you. We would like to be in the room when it is read, because the conversation that follows a measured floor is very different from the one that follows a proposal. Two things can follow, and both are optional.
Add your page to a market baseline. We are building four readings that no market publishes today: what it costs to run one policy for one year; what it costs to take one claim from notice to payment; how many days pass between a risk being bound and its reinsurer seeing it; and where each dollar of health claims goes. Each is paired with the time it takes to change what it measures. Each comes from a fixed method applied to a participant's own ledgers in a working session. You get your own result back, on the same definitions as everyone else, set against the anonymised distribution. Only the aggregate is published.
Or test the specification. Take what you wrote in block 06 (one product, one channel, one quarter) and run it beside your core, with your own operations team as the judge. If the floor does not move, you switch it off. That is the offer to all five chairs at once.
Both start the same way: an Operations Discovery that maps your highest-value workflows and the cost each one carries.
Book an Operations DiscoveryFive people in a room, each of them right, is how an industry stands still for twenty years. One engine that answers all five is how that stops.
Which chair are you sitting in?
Key takeaways
- The most quoted statistic in corporate change, that 70% of transformations fail, has no empirical basis. It began as an "unscientific estimate" about re-engineering in 1993.
- Five people must agree, and all five are right. Five reasonable cautions add up to a veto nobody voted for.
- What would change each of their answers adds up to one specification: beside the core, proven on one workflow, governed, and stoppable without a migration. A configuration layer, a governed agent layer and an optimisation layer meet it.
- Nine configuration surfaces make a product a combination rather than a build. Six use cases, of many, show how each closes a gap named in Part 1.
- The floor can move, and reach moves with it: one listed insurer added 1.2 million customers while headcount fell 6%. How far it moves in your market is unknown, because nobody has measured the starting point.
- The Reach Canvas measures it: your floor, your mould, where the two put you, what is holding it, the market you cannot reach, and one specification. One page, one line of business, no vendor required.
Also in this series
Part 1: Insured Against Everything But This
Why the protection gap widens when the need for cover peaks, and the three risks insurers have never priced: the cost of their own work, the business never written, and the decision not taken.
Sources
Written by the author. Research, source-checking and graphics were prepared with AI assistance, and every figure was traced to its original publication. Company-reported figures are labelled as such. The illustration in section 04 is arithmetic on stated assumptions, not a projection.
- M. Hammer and J. Champy, Reengineering the Corporation, HarperBusiness, 1993; M. Hammer and S. Stanton, The Reengineering Revolution, HarperBusiness, 1995; M. Hughes, "Do 70 per cent of all organizational change initiatives really fail?", Journal of Change Management 11(4), 2011, research.brighton.ac.uk.
- Russell Reynolds Associates, Global CEO Turnover Index, 2025 annual review, russellreynolds.com.
- Grant Thornton, "Insurance insights: 2026 AI Impact Survey report", April 2026 (insurance subset of around 100 executives), grantthornton.com.
- W. Samuelson and R. Zeckhauser, "Status Quo Bias in Decision Making", Journal of Risk and Uncertainty 1, 1988, scholar.harvard.edu; E. Johnson, J. Hershey, J. Meszaros and H. Kunreuther, "Framing, Probability Distortions, and Insurance Decisions", Journal of Risk and Uncertainty 7, 1993, ideas.repec.org.
- BCG, "How Change Really Works: Seven Science-Based Principles for Successful Change", bcg.com; J. Dhar et al., Fortune, 19 May 2026, fortune.com.
- Lemonade Inc., Q4 2025 Letter to Shareholders, 19 February 2026, sec.gov; Q3 2022 Letter to Shareholders (customer base of 1,775,824), sec.gov. Company-reported.
- Ping An Group, "Driving Innovation with Generative AI", 2025, group.pingan.com; Ping An 2025 annual results, group.pingan.com. Company-reported.
- Zurich Insurance Group, "AI at Zurich", zurich.com; FinTech Global, "Zurich expands agentic AI rollout with Cytora partnership", 18 May 2026, fintech.global; insuranceNEWS.com.au on Sabadell Seguros VoiceIQ, insurancenews.com.au. Company-reported.
- J.D. Power, 2026 U.S. Property Claims Satisfaction Study; Life Insurance Association Singapore, 2025 industry results; Life Insurance Association Singapore, Protection Gap Study 2022. Full references in Part 1.