Enterprise DNA

Instead of Origami Risk

Stop renting Origami Risk. Own your insurance programme.

We build your version around your companies, your policies and your broker, bring your Origami Risk policies, claims and locations across and run it for you. Start with this quarter's renewals and open claims.

Origami Risk does not publish a price. Its risk management system is an annual subscription quoted to each organisation, and the price varies with the size and complexity of the setup.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The recurring bill

What your Origami Risk subscription pays for

Origami Risk is quoted privately. Here is what that subscription covers, set against owning the records your finance and risk team already keep.

Layers

A price set by the size of the setup

The subscription is quoted on the size and complexity of your implementation. More companies, more locations and more modules mean a bigger quote for the same kind of records.

FileText

Your policy schedule, on their platform

Policies, periods, limits, excesses and premiums are typed in from your broker's documents. You pay to keep your own programme history on someone else's system.

Building2

The schedule of values

Locations and declared values sit in the system so they can go to the insurer at renewal. The same list, with the latest valuation beside it, answers whether you are underinsured.

ClipboardList

Claims administration

First notice, notes, reserves and payments. Each is a record with a date, and the questions that matter are about the dates: who has not been told, and who has gone quiet.

BarChart3

Dashboards and premium allocation

Charts of spend and losses, and premiums shared across your companies. Each one is a question your own records answer directly, in the words you would use to ask it.

Database

History that has to come back out

Every renewal asks for five years of claims and every change since last year. Renting means that history sits under the vendor's agreement.

Your insurance programme

The renewal and claims meeting, run from your own records

Renewals

No renewal without the disclosure done

Every policy carries its renewal date and the changes since the last one.

  • check Renewals in the next 120 days, with what is still owed to the broker
  • check A renewal cannot be recorded while a change of that class is untold
  • check The renewal information drafted from your records, ready to check and send
  • check Premium change on every renewal, policy by policy

Disclosure

Every material change, owned by someone

A new site, a new market, a new truck or a bigger sum insured is logged the day it happens.

  • check Adding an asset or changing a sum insured logs the change for the insurer
  • check Each change tied to the policy and the renewal it must be told by
  • check The date and the person it was told to, kept on record
  • check A list of every change no insurer has heard about yet

Claims

No loss left unreported

A loss goes on record with the date the insurer must hear by, worked out from your policy.

  • check Losses the insurer has not been told about, and how late
  • check Open claims with no update in four weeks
  • check A claim cannot close before the insurer was told
  • check Claims against premium by class over three years

Your group

Answers your current reports were never built for

Ask in plain words and get the answer from your own history, with the rule behind every flag.

  • check Buildings declared under the average clause, and the shortfall
  • check Valuations more than three years old
  • check Contractors on site with no certificate, an expired one or too low a limit
  • check Each company's share of every premium for the month-end journals

Make it yours

Design your own Origami Risk replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Origami Risk. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Origami Risk replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Origami Risk data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Insurance Programme for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Insurance Programme for Claude Code

Connected to your own database

What needs attention across our insurance this week?

1

Item
PRP-25
Rule
undisclosed change before renewal
Detail
CH-001: Leased and fitted out a new warehouse...
Days
60

1

Item
PL-25
Rule
undisclosed change before renewal
Detail
CH-002: Started exporting frozen meals to Jap...
Days
40

1

Item
PRP-25
Rule
renewal disclosure not sent
Detail
Material damage and business interruption 202...
Days
35

1

Item
CYB-25
Rule
cover expired, no renewal
Detail
Cyber 2025-26 with Ironbark Specialty ended 2...
Days
7

1

Item
CL-002
Rule
claim not notified
Detail
Customer reports a foreign object in a frozen...
Days
6

1

Item
A-001
Rule
underinsured
Detail
Auckland factory building declared at 77.1% o...

2

Item
PL-25
Rule
renewal coming
Detail
Public and products liability 2025-26 ends 20...
Days
65

2

Item
CL-001
Rule
claim gone quiet
Detail
Forklift struck racking in the Hamilton depot...
Days
45

2

Item
CO-002
Rule
contractor certificate expired
Detail
Rapid Refrigeration Services (refrigeration):...
Days
12

2

Item
CO-003
Rule
contractor limit too low
Detail
SafeLift Forklift Hire (forklift hire and ser...

2

Item
CO-004
Rule
no contractor certificate
Detail
Kiwi Clean Commercial (cleaning): no certific...

3

Item
A-001
Rule
valuation out of date
Detail
Auckland factory building last valued 2022-10...
Days
1480

3

Item
CO-006
Rule
contractor certificate expiring
Detail
Harbour Security Patrols: public liability ex...
Days
20

Ask it anything

Ten questions your insurance records answer

These run against the working demonstration today. Your own version asks them of your companies, your policies and your history.

chat_bubble Which changes since the last renewal have we not told our insurers about?
chat_bubble Which renewals are due in the next 90 days, and has the renewal information gone for each?
chat_bubble Is any of our cover expired with nothing in its place?
chat_bubble Which buildings are declared below the average clause, and how much short are we?
chat_bubble Which assets have not been valued in three years?
chat_bubble Which losses has the insurer not been told about yet, and how late are we?
chat_bubble Which open claims have had no update from the insurer in a month?
chat_bubble Which contractors on site have no current certificate, or a limit below what we require?
chat_bubble How is each premium shared across our companies, and what does each one owe this year?
chat_bubble Which class of cover has cost the insurer more in claims than we paid in premium over three years?

Switching

How to switch from Origami Risk

The move involves exporting three reports, mapping your setup’s columns, checking unmatched rows, and running both registers side by side before you retire Origami Risk.

  1. 1

    Export your three reports

    Request the policy schedule, claims list, and schedule of values reports from Origami Risk. These are the reports the import reads. Export what your account allows, usually CSV or Excel, and check with Origami Risk if you cannot find the reports or are unsure how to export them.

  2. 2

    Load the reports in a test run

    Load the three reports into the import process and run its test first. The import reads the policy schedule, claims list, and schedule of values. It recognises common column names, and Claude Code can map other column names. Treat this as a check before bringing the records into the new database, not as a completed move.

  3. 3

    Review every flagged row

    Check the rows the test reports as unmatched, then fix the data or column mapping and run the test again. The import reports every row it cannot match. Check that policy periods link to the right policy years, since the import uses the policy number to carry renewal history forward. Do not proceed until you understand the remaining flags.

  4. 4

    Run both registers side by side

    Keep Origami Risk available for a short period while you use the new register. Check that the policies, claims, values, and renewal history you rely on are present and make sense. Use this time to spot missing records or mapping issues before you depend on the new database for day-to-day work.

  5. 5

    Switch off Origami Risk

    Once you have checked the migrated records and are ready to work from the new register, arrange to end your Origami Risk subscription. Confirm that you have kept the records and history your business needs before you give up access. Your broker still places cover and handles the insurer, so this move is about your records, not replacing your broker.

construction

Where the real effort goes

The import covers the policy schedule, claims list, and schedule of values, but the real work is usually matching your own Origami Risk column names and rules, then deciding how much history to bring. Notes and documents also need attention. If Enterprise DNA installs and runs the system for you, it handles the mapping, notes, and documents as part of that work.

Not ready for a call?

Get your Origami Risk switch plan by email

We will send you the step-by-step plan for moving your business off Origami Risk, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask what needs attention
  3. 3 Add your companies and policies, then test your Origami Risk exports with a dry run
  4. 4 Put your logo on the allocation statements and schedules of values in brand.json
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your companies, policies and broker set up, with the clauses and deadlines from your wordings
  • check Your Origami Risk policies, claims and locations mapped and checked
  • check A page where contractors send their certificates, or a web front end if your team wants one
  • check Your insurer's claims report brought in on a schedule
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and ownership agreed
  • check The renewal information prepared for your broker each year
  • check Unreported losses, quiet claims and expired certificates chased the same week
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book an insurance records review

Questions

Instead of Origami Risk, answered

What does Origami Risk cost compared with this? expand_more

Origami Risk does not publish a price, so bring your own agreement. Its subscription is quoted on the size and complexity of your setup. The free version has no licence fee; hosting and your agent subscription are separate. Enterprise DNA builds and runs your version for one setup fee, then a retainer.

Can you bring our Origami Risk records across? expand_more

Yes. The free version reads three Origami Risk report exports: the policy schedule, the claims list and the schedule of values. It reports every row it cannot match and does a test run first, and it links each policy year to the one before it, so your renewal history comes across. Every Origami setup names its columns differently, so mapping yours, along with notes and documents, is part of what we do for an installed version.

Does this replace our broker? expand_more

No. Your broker still places the cover and handles the insurer. This keeps the records your business is accountable for: what you told the insurer and when, what you declared, what you claimed. It drafts the renewal information and claim notices for your broker; a person sends them.

Does this keep us on the right side of the duty of disclosure? expand_more

It keeps the record you need to show you met it. Every material change is logged, tied to the policy and renewal it belongs to, and a renewal cannot be recorded until each one has been told to the insurer. It also checks claim notice, average clauses, valuations and contractor cover, and each check cites the rule it comes from. It supports your own judgement and your broker's advice; it does not decide what is material for you.

What do we keep if we stop working with you? expand_more

Everything. The database, your version and the full history of policies, values, changes, claims and certificates are yours. A complete copy exports in one step, and we agree access, backups and recovery with you when it is set up.

Bring your programme and your Origami Risk agreement

Spend 30 minutes with Sam. We will look at how your renewals, claims and contractor certificates are kept today, what your broker asks you for each year, and what your own version should do first.

Insurance Programme for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Origami Risk?

Get your version built