BramForgeLabs / Products / Insurance AI Radar

Available — 192-page PDF

Insurance · AI Solutions

Where AI is actually running in insurance.
And how to build the cells that aren't.

Not another market report. A two-layer radar: scan the value chain for production vs theatre, then take a buildable agent spec into a POC that would survive an audit. Life-first. Vendor-neutral. Regulation designed in.

$89 CAD one-time · 192-page PDF · 39 use cases · 8 domains · 30-day guarantee · no DRM


39Use Cases
8Domains
6Production
20Pilot
13Theatre
24Regulation-heavy

Insurance does not have an AI-ideas problem

It has a production problem. Most "AI in insurance" writing is a model-type essay or a vendor brochure. Neither tells a chief underwriter, claims lead, or CRO where to start — or how to build something a regulator can reconstruct six months later.

Scan the chain. Then build the cell.

Layer 1 · Compact

The Radar

  • 39 use cases across 8 value-chain domains
  • Each cell tagged Theatre / Pilot / Production
  • High Value · Quick Win · Regulation-heavy
  • POC effort: Easy, Medium, Complex
  • A pane-level read: what is real, what is not
Layer 2 · Detailed

The build spec

  • Full 11-section spec for every use case
  • Agent roles, inputs, outputs, success criteria
  • House pattern: retrieve → synthesize → verify → escalate
  • Failure modes, POC scope, path to production
  • Mandatory Section 11: how to build it

The interesting number is not 39 ideas. It is 6 in production and 13 that should not be built as autonomous agents yet. The Radar's job is to stop a year spent in theatre.

The house pattern, applied to an APS

Every detailed spec uses the same orchestration the IT playbook uses for knowledge work — retrieval, synthesis, verification, escalation — because insurance AI that cannot cite its source is not a system, it is a liability.

Retrieval Agent → Synthesis Agent → Verification Agent → (low confidence / ungrounded / automated-decision risk) → Escalation Agent

Worked example — Use Case 1.4 APS Retrieval & Clinical Summarization. The agent does not issue, decline, or rate. It produces a cited clinical packet a human underwriter can use.

AgentResponsibilityOutput
RetrievalPage-aware chunks from the APS and e-App impairmentsTop-k spans, page numbers, source hashes
SynthesisStructured clinical packet from retrieved context onlyJSON + narrative; every finding has a source span
VerificationGrounding, purpose-limitation, prohibited fieldsVerified packet, or escalate with reason
EscalationHuman UW queue when confidence is low or Law 25 is in playWork item + immutable trace
Sequential pipeline Validation / critique Human-in-the-loop No rating field on this packet
Read the full spec →

39 use cases across 8 domains

Depth is life insurance, with a Canadian regulatory overlay. P&C is a second pane, not a second book.

Theatre — would not survive an audit Pilot — human in the loop, limited book Production — in-force, reconstructable
#DomainUse casesn
01New Business & UnderwritingApp triage, KYC/AML, evidence procurement, APS summarization, risk synthesis, Law 25 disclosure, STOLI detection7
02ClaimsFNOL triage, document ingestion, adjudication assist, SIU/fraud, leakage/subrogation, settlement explanation6
03Policy ServicingRequest orchestration, billing exceptions, loans/withdrawals, beneficiary change, contract assembly5
04Distribution & AdvisorLicensing/commission, illustration assist, suitability check, case-status communication4
05Actuarial & ReservingExperience-study narrative, assumption packs, IFRS 17 commentary (human-signed)3
06Customer, Retention & ConductLapse/save, complaint/TCF routing, consent-limited next-best-action, fairness monitoring4
07Risk, Compliance & GovernanceE-23 inventory, model drift, shadow AI, Law 25 consent/PIA, sanctions/PEP5
08P&C OperationsCV damage assessment, cat-event surge, telematics, repair-cycle, contents inventory5

If you only build three

01 · UC 1.4APS clinical summarization

High value, medium effort, audit-friendly. The house pattern. Free preview on this site.

02 · UC 2.1FNOL intake & routing

Production-shaped, easy, visible to operations in two weeks.

03 · UC 7.1AI use-case risk pack

The E-23 evidence cell that makes the other two defensible.

MethodHow specs are written

The 11-section template and the house pattern, without the private fleet roster. Open Method →

People who have to put AI into a regulated book

Chief underwriters & NB operations

Packets, not copilots. Cited findings a human can sign.

Claims & SIU leads

FNOL and fraud that already work; coverage agents that can point at the policy.

CROs, model risk, privacy

E-23, Law 25, purpose limitation, and an audit trail as the design, not the appendix.

Independent consultants

A reusable radar + spec set. One purchase, every carrier engagement.

What this is not

See the format for yourself

Free sample: Use Case 1.4, compact + detailed

No email required. The full APS summarization spec — agent table, failure modes, Section 11 how-to-build.

Read the free sample →

One purchase. No subscriptions.

$89 CAD

One-time · 192-page PDF · no DRM

  • Compact radar — all 39 use cases, Theatre / Pilot / Production
  • Complete 11-section specs for every cell
  • Regulatory overlay, POC charter, prioritization, stack map, maturity
  • House-pattern reference code (Retrieve → Synthesize → Verify → Escalate)
  • Vendor-neutral — any LLM, no affiliate stack
  • 30-day money-back guarantee
Request the PDF — $89 CAD

Email checkout until Lemon Squeezy is wired · same 30-day guarantee as the IT playbook

D·A·D subscribers get first notice when card checkout goes live. Subscribe free →