Enterprise DNA

Instead of JAVLN

Stop renting JAVLN. Own your insurance broking system.

We build your version around how you quote, renew and manage claims, bring your JAVLN data across, and run it for you. No plan tiers, and the system is yours.

JAVLN prices per user per month, quotes the platform on application, and charges separately for modules and implementation.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What you are paying for

Most of a broker system bill is the front end

The clients, the policies, the expiry dates and the claims are yours. The screens around them are what you rent, and the rent is set per user, per month, before the implementation fee and the modules.

paid

A seat for everyone who touches a policy

JAVLN prices per user per month and quotes the platform on application. The account executive, the claims broker, the support person who looks up a schedule and the principal who reads the renewal list are four seats, whether they log in every day or once a fortnight.

layers

Modules you buy one at a time

Quoting, renewals, client management, claims, financial management and compliance are sold as parts of one platform. The audit trail and the compliance reporting sit in the tier above the one a five person brokerage would otherwise buy.

build

Implementation, and every change after it

A project fee before anyone logs in. Reviewers on Capterra say the configuration process is still too manual for an application that size, and that improvements take longer than expected. Every time your renewal process changes, it is a change request.

hub

The insurer connections you do not have

Quote aggregators and direct insurer feeds are the vendor's to build. The markets that are not connected are the ones your team re-keys into an underwriter portal, twice, once for the quote and once for the bind.

dashboard

Reports somebody else designed

The renewal list, the claims board and the brokerage report come as the vendor drew them. The question you actually have is a change request, or an export to Excel that someone rebuilds every month.

lock

Your own history, in their format

Twenty years of policies, claims and correspondence sit in a database you cannot query. Leaving means asking the vendor for an export of data you created, and paying to have it moved.

What you get instead

A broker system you talk to

The cycle

Renewals at sixty, thirty and fourteen days

A renewal is a workflow row with stages, not a date on a policy. One command shows every policy coming up, where each one has got to, and who has not been spoken to.

  • check Banded the way a brokerage runs the week: sixty, thirty, fourteen, expired
  • check Premium and brokerage at risk in each band, so the biggest untouched client is the first call
  • check Every renewal stuck in market past the date the underwriter promised terms, named with the days
  • check A policy that expired and is still marked in force goes to the top of the list, not into a report nobody opens

The file

Advice records, and the Code checked against them

Scope, recommendation, reasons, alternatives, risks, limitations and remuneration are separate fields, and a command checks the file against the rules the brokerage lives under.

  • check One command finds every placement in the last year with no advice record behind it
  • check Every rule cites its clause: Insurance Brokers Code of Practice 7.2(a) for the fourteen day contact, 6.1 for remuneration, 7.1(a) for claim updates, 9.4(b) for complaints
  • check The New Zealand side cites the Financial Markets Conduct Act sections 431I to 431P, the disclosure regulations 229C to 229F, and the Code of Professional Conduct standards 3 and 4
  • check Change a rule in plain language and the check changes with it

Claims

A board sorted by who has not been told anything

Every claim event is a row. The board is not sorted by date opened, it is sorted by how long since anyone spoke to the client, because that is the complaint that arrives.

  • check Days since the last client update on every open claim, next to the reserve
  • check Claims notified to an insurer with no acknowledgement on file, named with the market
  • check The whole history of a claim in one read, oldest event to newest
  • check A progress update drafted from the record, into drafts/, for a person to send

Yours

Your database, your paperwork, your rules

Plain records you own, branded documents rendered from them, and read-only pages for the week. No client money anywhere: the broking trust account stays in the system that holds it.

  • check Renewal summaries, portfolio schedules and claim updates rendered in your colours from one set of brand settings
  • check Read-only HTML dashboards for the week and the renewal cycle, no server to run
  • check Brokerage earned by month and by insurer, and what has been accrued for sixty days and never reconciled
  • check Import from a JAVLN, Insight or WinBEAT export in one command, with a dry run first

Make it yours

Design your own JAVLN replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your JAVLN 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 JAVLN 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 Broking for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Broking for Claude Code

Connected to your own database

Which policies are renewing in the next 14 days?

Renewals inside 14 days (6, $52,947 premium, $8,422 brokerage at risk)

EXPIRED 1 policies, $3,696, 1 with no client contact

POL-20020

Client
Janet Whitmore
Class
home
Insurer
Vero
Expires
2026-09-06
In
9d ago
Stage
not started
Spoke
NEVER
Qs
0
Premium
$3,696
Broker
Priya Nair

14 DAY 5 policies, $49,251, 3 with no client contact

POL-20012

Client
Coastal Storage Ltd
Class
material damage
Insurer
Ando
Expires
2026-09-20
In
5d
Stage
not started
Spoke
NEVER
Qs
0
Premium
$13,017
Broker
Priya Nair

POL-20001

Client
Kauri Joinery Ltd
Class
material damage
Insurer
NZI
Expires
2026-09-24
In
9d
Stage
in market
Spoke
21d ago
Qs
1
Premium
$21,384
Broker
Hine Rawiri

POL-20002

Client
Kauri Joinery Ltd
Class
business interruption
Insurer
NZI
Expires
2026-09-24
In
9d
Stage
in market
Spoke
21d ago
Qs
0
Premium
$7,206
Broker
Hine Rawiri

POL-20005

Client
Blue Duck Cafe Group Ltd
Class
general liability
Insurer
Ando
Expires
2026-09-27
In
12d
Stage
not started
Spoke
NEVER
Qs
0
Premium
$2,438
Broker
Priya Nair

POL-20006

Client
Blue Duck Cafe Group Ltd
Class
material damage
Insurer
Ando
Expires
2026-09-27
In
12d
Stage
not started
Spoke
NEVER
Qs
0
Premium
$5,207
Broker
Priya Nair

Ask it anything

Questions JAVLN cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which clients pay us less brokerage than the claims work they generate, and which of those renew inside ninety days?
chat_bubble Which insurer is slowest between a submission going out and terms coming back, by class of business?
chat_bubble Which policies have carried the same sum insured across three renewals while the premium moved more than fifteen percent?
chat_bubble What would the book earn if every brokerage rate matched the agency agreement, against what it actually earns?
chat_bubble Which placements were bound with no advice record written in the thirty days around them, and who wrote them?
chat_bubble Which clients are on cover and have not been spoken to in six months, ranked by premium at risk?
chat_bubble How many days sit between an insurer's last move on a claim and the client being told, by broker?
chat_bubble Which classes of business earn the most per renewal, once you count the quotes we asked for and lost?
chat_bubble Which endorsements went effective before the insurer confirmed them, and for how many days was the client uncovered on paper?
chat_bubble If a broker left tomorrow, which clients, expiring premium and open claims move, and how many renew inside sixty days?

Switching

How to switch from JAVLN

Moving off JAVLN means exporting what you have, loading it with one command, checking what did not carry across, and running the two side by side until you trust the new one.

  1. 1

    Export your book from JAVLN

    Export clients, policies, contacts and claims from JAVLN as CSV. If your JAVLN account limits what you can export, take what it allows, usually CSV or Excel, and check with JAVLN support if you need more. This is the record that comes across: client links, policy details, contacts and claims history.

  2. 2

    Run the import, dry run first

    In Broking for Claude Code, start the import from JAVLN using your four exported files and do a test run first. It reports exactly what it would create and which rows it would skip, before anything touches your database. Fix what needs fixing in the export, then run the import again for real.

  3. 3

    Check what the import skipped

    Read the import's own report of what it created and what it skipped. Advice records and policy sections do not come across, because most broker systems, JAVLN included, do not hold them as fields. The guide lists everything else that does not carry, so you know what to rebuild by hand and what you can leave behind.

  4. 4

    Run both systems side by side

    Keep JAVLN running while you use Broking for Claude Code for real work: renewals, claims, quotes. Compare the renewal list and the claims board against JAVLN for a short period so everyone still trusts the numbers before it becomes the only record. This is where you catch a missed row or a mapping that needs fixing.

  5. 5

    Switch off JAVLN

    Once the two systems agree and your brokers are working from Broking for Claude Code without needing to check JAVLN, cancel it. Your data sits in plain records you own, so nothing about the switch depends on JAVLN anymore.

construction

Where the real effort goes

The export and the import command handle the mechanical part. The real work is deciding which of your own fields, renewal bands and compliance rules to carry across, and how much claims and policy history is worth rebuilding by hand since advice records and policy sections do not import. Enterprise DNA does this mapping and the migration itself when they install and run it for you.

Not ready for a call?

Get your JAVLN switch plan by email

We will send you the step-by-step plan for moving your business off JAVLN, 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.

Two ways to run it

Run it yourself, or have it run for you

Open source

Run it yourself

Free

  1. 1 Clone the repo
  2. 2 npm run demo, then open the folder in Claude Code
  3. 3 Type /renewals-due
  4. 4 Import your JAVLN export and point it at your own database
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA install it

One setup fee, then a monthly retainer

  • check We migrate your JAVLN, Insight or WinBEAT clients, policies, contacts and claims
  • check We connect it to your mail, your accounting system and the trust account you already run
  • check We write the commands and the compliance rules for your licence and your classes
  • check It runs inside Omni, our managed Command Center, with the rest of your business
Book a discovery call

Questions

Instead of JAVLN, answered

Where does the trust account go? expand_more

It stays exactly where it is. This system never holds client money, never records a premium receipt and never reconciles a trust account. That is a regulated obligation with an auditor attached, and it belongs in the accounting system that already carries it. What moves here is the policy lifecycle, the advice record, the claims, the tasks and the brokerage your business earns. The boundary is written into the free version, not bolted on.

Will this stand up in an FMA or ASIC review? expand_more

The records will, because they are better records than most brokerages keep. Every advice record has scope, reasons, alternatives, risks, limitations and remuneration in separate fields, and it lists every gap with the clause it breaches. What no software can do is make the advice good. Read the guide: ten rules, each with the section or clause it comes from. It is your rule book pointed at your data, not legal advice, and you change it to match your own licence conditions.

What happens to twenty years of policy and claims history? expand_more

It comes with you. Export clients, policies, contacts and claims from JAVLN as a simple spreadsheet file, start the import, and it lands in your own database with the client links and the expiry dates intact. Do a test run first and it tells you exactly what it would create and every row it would skip. Advice records and policy sections do not come across, because most broker systems do not hold them as fields, and the guide says so plainly along with everything else that does not carry.

Our brokers are not technical. Who types the commands? expand_more

Nobody types commands. You say "what is expiring in the next month and who have we not spoken to" and Claude Code gives you the right answer. The system always answers the same question the same way, using the words your industry uses. A broker who can write an email can run this. The one thing it will not do is guess: if a name matches two clients it lists both and asks.

What does the installed version add? expand_more

Installation, the migration off JAVLN, Insight or WinBEAT, the connection to your mail and your accounting system, commands written for your classes and your process, the compliance rules checked against your own licence conditions, and someone to call. It runs alongside everything else Enterprise DNA runs for you, inside Omni.

Stop paying per seat to look at your own expiry dates

30 minutes with Sam. We look at what you pay for your broker system, what your team actually uses in a week, and what the installed version would look like for your brokerage. If it is a fit, we install it. If it is not, take the free version and run it yourself.

Book a discovery call Get the free version

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

Done paying for JAVLN?

Get your version built