Insurance · Sydney

AI for insurance in Sydney.

We help Australian general, life and health insurers ship AI that moves the loss ratio and clears APRA review. Claims automation, underwriting support and conduct surveillance, designed with your risk team in the room.

Claims automationUnderwritingConduct riskAPRA CPS 234CPS 230

Why insurers call us

Where the loss ratio and the regulator both matter.

"Claims volume tripled after the storms. Adjuster headcount did not. Touch time per claim is crushing our NPS."
"Conduct review is one person sampling 2% of calls. We found a breach in month fourteen we should have caught in month three."
"Our underwriting model works in pilot. Legal will not sign off until someone owns the bias testing."

Regulation map

Six rules that shape every insurance AI build.

How hard it shapes the design
APRA

CPS 234

Information security

Claims documents, medical records and policy data flowing to a model make that model an information asset. It needs tested controls and a named owner.

What we build in
Asset registerControl testingVendor review
APRA

CPS 230

Operational risk management

If claims triage depends on a model provider, that provider may be material. You need fallbacks and tolerance levels for when it is slow or down.

What we build in
Fallback pathsProvider mappingTolerance tests
Industry codes

Claims codes

General Insurance and Life Insurance Codes of Practice

Claims decisions carry timeframes and fairness duties. AI can approve simple claims and speed up the rest, but declines go to a person.

What we build in
Decline routingSLA timersReason codes
ASIC

DDO

Design and distribution obligations

Products must reach the target market they were designed for. Underwriting and pricing models need monitoring for drift away from it.

What we build in
Drift monitorsSegment testsReview triggers
ASIC

Anti-hawking

Conduct and sales rules

Unsolicited selling is restricted and sales calls are scrutinised. Surveillance AI must flag risk without becoming a black box.

What we build in
Call coverageLanguage flagsEvidence packs
OAIC

Privacy Act

Australian Privacy Principles

Health and claims data is sensitive. New transparency rules for automated decisions start in December 2026.

What we build in
PII maskingPurpose limitsDecision notices

This is a design guide, not legal advice. Your compliance and legal teams make the final call. We give them the evidence to make it quickly.

Use cases

Five insurance workloads we know how to ship.

Ranges are typical of what we see once a workload is in production. Your baseline decides your number, so we measure it first.

01

Claims automation

Agents read claim forms, invoices and photos, match them to cover, check for fraud signals and settle simple claims. Complex ones reach an adjuster with a summary.

Typical40 to 60%less handler touch time on simple travel and motor claims
02

Underwriting support

Explainable models that help underwriters price and accept risk faster, with drift monitoring and bias testing your actuaries can review.

Typical30 to 50%faster quote turnaround on standard risks
03

Conduct risk monitoring

Every sales and service call reviewed, with hawking language flagged and evidence your compliance team can act on.

Typical100%call coverage, up from a 2 to 5% sample
04

Fraud detection

Graph and machine learning models alongside your rules, so investigators chase real fraud instead of false alarms.

Typical3 to 5xbetter true positive rate than rules alone
05

Claims and portfolio reporting

Actuarial, claims and distribution dashboards on open-source Superset and ClickHouse, hosted in Australia.

Typical30 to 40%lower BI licensing at 100+ users

How we keep it compliant

One architecture your risk team can read in five minutes.

Every build follows the same path. Data stays onshore, a person signs off on decisions that touch a customer, and every step leaves a record.

Sydney region · ap-southeast-2
01
Your systemsPolicy admin, claims, documents and call recordings stay where they are.
02
Redaction gatewayNames, health details and policy numbers masked before any model sees them.
03
Model in SydneyHosted in ap-southeast-2. Your data is never used for training.
04
Evaluation gateEach output scored against tests and claims rules before it counts.
05
Human adjusterA named adjuster decides every decline and any complex claim.
06
Action and recordClaim settled or routed, reasons stored.
Nothing leaves AustraliaCustomer data, prompts, outputs and logs all stay inside the boundary.
Audit trailappend-only · 7-year retention
10:02:11claim.classified motor/simpleagent:claims-v2.1sha 3b1e..c7
10:02:12eval.passed score=0.97gate:claims-rules-8sha a4d0..5f
10:02:12fraud.signals nonemodel:graph-mlsha 66c2..18
10:09:40settlement.approvedadjuster:m.patelsha e91f..3d
Onshore by defaultModels, data and logs live in the Sydney region. Every data flow is drawn and documented.
Human in the loopAI prepares and recommends. A named person decides on anything that touches a customer.
Audit trailEvery input, output, score and approval is written to an append-only log you own.
Model evaluationTest sets, policy checks and drift monitors run before launch and every day after.

Ways to engage

Start with one workload. Prove it. Scale it.

Sprint

Regulated AI Sprint

Two weeks: one claims or underwriting workload taken to an evaluated prototype, with the evidence your risk team will ask for.

from A$10K

Get a proposal
Build

Production build

Six to ten weeks: the workload live in your cloud, Sydney region, with evals, audit trail and human review wired in.

from A$50K

Get a proposal
Embedded

Embedded AI team

A squad that works alongside your claims, underwriting and risk teams, two to four days a week, with quarterly outcomes.

from A$12K/mo

Get a proposal

Questions

What risk and compliance teams ask us.

Can AI decline a claim?

We design for AI to recommend and a person to decide on every decline. Simple approvals can be automated if your claims philosophy allows it.

Can our data stay in Australia?

Yes. Models and data are hosted in the Sydney region, and every data flow is documented for your CPS 234 register.

How do you handle bias in underwriting models?

We test outcomes across customer segments before launch, monitor drift in production, and keep the reasons behind each decision so they can be explained.

Which models do you use?

Claude, GPT and open-weight models, chosen per workload on accuracy, cost and where they can be hosted. We do not resell any vendor.

Where do you start?

Usually claims. It has the clearest baseline, the fastest payback and a regulator story that is easy to tell.

Start a conversation

Tell us what you are working on.

A few lines is enough. A senior person reads every message and replies with a next step, not a sales sequence.

We reply within one business day.

What can we help with?
We only use your details to reply.