Insurance

Underwrite risks – with evidence for the supervisor.

Mila connects application data, policy and the applicable law from VVG to VAG. She shows you where to look more closely – every statement with a source.

Experience it live · free
The problem

Application, policy, supervisor – the obligation sits in between.

Application data, policies, VVG, VAG and sanctions lists: for every underwriting case and every claim, you pull it all together by hand. And the supervisor asks why you decided the way you did.

The question

You ask Mila – in one sentence.

Instead of pulling everything together by hand, you simply ask. Mila shows what is being checked – step by step, across all sources.

The evidenced answer

Every finding comes with its source.

Every statement names the source it comes from. What cannot be evidenced, the agent flags as open.

The next step

Mila prepares – you approve.

The underwriting stays your decision. It is only carried out once you approve it.

Hello, I'm Mila – your AI agent for insurance. I keep an eye on applications, policies and the applicable law, and let you know when something stands out.
Three points on a commercial application stood out to me today:
Signals · today
SharePointCommercial client application Meridian Bau
c:node GraphVVG § 19 · disclosure obligation open
c:node GraphSimilar name on EU sanctions list
@Mila, can we underwrite this commercial application as is – compliant with supervisory requirements?
I'm checking all sources:
  • Application data read
  • Pre-contractual disclosure obligation under VVG § 19 checked
  • Beneficial owners identified
  • EU financial sanctions list matched
  • Obligations under VAG checked
Underwriting possible – but with one query.
  • Information plausible, disclosure obligation met in principle
  • One risk-relevant detail is missing – query the client before issuing the policy (VVG § 19)
  • Similar name on the EU financial sanctions list (84 %) – clarify before acceptance
Application p. 1–2VVG § 19VAGEU financial sanctions list
I've prepared the next step:
Draft · Query to Meridian Bau + sanctions clarification
Query on the missing risk-relevant detail plus a match of the sanctions hit against the date of birth. The case has been created for approval.
ApproveEditNothing goes out without approval

Example case with example data · legal bases real · not legal advice.

Sales booklet

Insurance — the whole picture as a PDF.

Use cases, packages, roll-out and the business case behind it — compact, to take with you and pass on.

Open booklet (PDF)
Get started

Your next step.

See c:node on your own case – or check where it runs and how it keeps things secure.

See a demo on your case

Give c:node a small test run with a real question from your everyday work – evidenced, step by step.

Book a demo →

See security

Where c:node runs, how you approve and what is evidenced – EU cloud Frankfurt or your own server.

See security →
FAQ

Frequently asked questions

Does c:node replace our underwriting decision?

No. c:node prepares the review – it connects application, policy and applicable law and backs every finding with a source. Underwriting only happens after your approval.

Where do the sources come from?

From your own documents and the c:node Graph – VVG, VAG, registers and sanctions lists. Every statement carries its source; where there is none, c:node says so openly.

Where does our data run?

In the EU cloud Frankfurt or on your own server, up to air-gapped. Application and policy data does not leave the EU or your premises – and your data is not used for training.

Is this fit for supervision?

Yes. c:node records a source and legal basis for every finding and produces an audit trail you can show to a supervisor or auditor.