Why an Australian claims-intelligence platform beats the North American incumbents on their own ground - and why they cannot simply localise their way back.
The established platforms sell speed and fraud detection to North American carriers. Imported unchanged, that pitch lands in the middle of an Australian enforcement cycle pointed in precisely the opposite direction.
The pressure here is on delay, denial, and the inability to explain a decision. Australians lodged roughly 119,949 complaints with AFCA in 2025–26 - the third consecutive year above 100,000. The three most-complained-about issues were delay in claim handling, service quality, and claim rejection. Motor claim delays alone account for around one in four general insurance complaints referred to AFCA.
Meanwhile ASIC's 2026 enforcement priorities name insurance claims handling and complaints processes directly, and APRA's April 2026 letter to regulated entities identified third-party AI risk - models embedded in vendor platforms with opaque upstream dependencies - as the biggest gap it found.
That is the whole thesis. The underlying capability - read the claim file, reconcile what the documents say, surface where they disagree - is the same capability they sell. What changes is the output contract: not a signal, but a reconciliation with both sides attached and a human making the call.
The first four engines are parity plays - necessary, not differentiating. Clockwork and Ledger are the moat, and neither can be retrofitted onto a product built against another country's regulator.
| Engine | What it does | Category parity | Status in build |
|---|---|---|---|
| Casefile | Document understanding, Australian corpus | Table stakes | Specified |
| Signal | Cross-document integrity examination, anchored | Table stakes | Built · tested |
| Ask | Cited claim Q&A - no anchor, no assertion | Table stakes | Specified |
| Enrich | Australian external context, onshore sources | Table stakes | Specified |
| Clockwork | Obligation engine - Code, RG 271, 8 jurisdictions | — none — | Built · tested |
| Ledger | Decision provenance, APP 1 & CPS 230 artefacts | — none — | Specified |
Four instruments change what an Australian claims function must be able to prove. Each one is a dated, unavoidable reason to have this conversation now rather than next year.
These are invariants in the data model and the test suite, not commitments in a policy document. A promise that survives a roadmap argument is the only kind worth putting in a contract - and each one answers a question an Australian board will ask unprompted.
Cannot decline a claim. Declines, reductions and recovery actions are recommender-only. There is no configuration flag that changes this.
Cannot assert without a source. A finding requires at least two anchors from two distinct documents. Unanchored extractions are discarded, not downgraded.
Cannot use a vulnerability disclosure against a claimant. Family violence, hardship and mental-health signals are firewalled from every integrity and recovery path. A breach raises a runtime error.
Cannot move data offshore. Claim content stays in Australian regions, including at inference time.
Cannot train on customer claims. Contractual, not best-effort.
Cannot bill for a denial. Priced on claims under management - never on savings share, recoveries or declines. A vendor whose revenue rises when claims are denied is indefensible at AFCA.
Where the incumbents lead with round multiples and headline percentages, we publish nothing until a pilot produces it. A six-week engagement on one portfolio, measured against a matched control cohort on numbers agreed before the start:
Leading with a stated methodology against a competitor leading with round numbers is itself the positioning. In a market where the regulator is actively asking carriers to justify their claims outcomes, the vendor who shows their working is the safer signature.
Verification note. Regulatory references are drawn from public sources as at August 2026 and are indicative, not legal advice. The General Insurance Code of Practice is mid-redraft; proposed obligations - including automatic acceptance at 12 months - are modelled as forward exposure only and are never reported as current breaches. Every obligation rule in the shipped engine carries an explicit verification flag against its primary instrument, and unverified rules are surfaced as unverified in the interface rather than presented as authoritative. No performance statistics appear in this brief or in the product because no pilot has yet produced any. Characterisations of competing platforms are drawn from their own published marketing material.