Instead of JAVLN
JAVLN rents you a screen around your own renewal cycle. Keep the cycle.
Broking for Claude Code is an open-source broker system that is just Postgres and Claude Code. Clients, policies and sections, the renewal cycle at sixty, thirty and fourteen days, quotes, endorsements, claims, advice records and brokerage, asked for in plain language. No seats, no tiers, no modules. Your trust account stays where it is.
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.
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.
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.
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.
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.
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.
Your own history, in their schema
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 Postgres, your paperwork, your rules
Plain tables 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 brand.json
- 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
What it looks like
Real commands, real answers
Three runs on the demo data that ships with Broking for Claude Code. Type the command in Claude Code, or ask for it in your own words.
Renewals inside 14 days (6, $52,947 premium, $8,422 brokerage at risk) ====================================================================== EXPIRED 1 policies, $3,696, 1 with no client contact Policy Client Class Insurer Expires In Stage Spoke Qs Premium Broker --------- -------------- ----- ------- ---------- ------ ----------- ----- -- ------- ---------- POL-20020 Janet Whitmore home Vero 2026-09-06 9d ago not started NEVER 0 $3,696 Priya Nair 14 DAY 5 policies, $49,251, 3 with no client contact Policy Client Class Insurer Expires In Stage Spoke Qs Premium Broker --------- ------------------------ --------------------- ------- ---------- --- ----------- ------- -- ------- ----------- POL-20012 Coastal Storage Ltd material damage Ando 2026-09-20 5d not started NEVER 0 $13,017 Priya Nair POL-20001 Kauri Joinery Ltd material damage NZI 2026-09-24 9d in market 21d ago 1 $21,384 Hine Rawiri POL-20002 Kauri Joinery Ltd business interruption NZI 2026-09-24 9d in market 21d ago 0 $7,206 Hine Rawiri POL-20005 Blue Duck Cafe Group Ltd general liability Ando 2026-09-27 12d not started NEVER 0 $2,438 Priya Nair POL-20006 Blue Duck Cafe Group Ltd material damage Ando 2026-09-27 12d not started NEVER 0 $5,207 Priya Nair
Open claims (7, $360,800 reserved, 2 where the client has not been told anything for a fortnight)
=================================================================================================
Claim Client Class Status Open Client told Reserve Insurer Broker
--------- ------------------------------ -------------------- -------------------- ---- ----------- -------- ------------------ -----------
CLM-26001 Southern Cross Freight Ltd motor fleet assessing 34d 26d ago $48,000 QBE Tom Baxter
CLM-26004 Harbourview Apartments Body... material damage assessing 120d 20d ago $156,000 Vero Tom Baxter
CLM-26008 Kirkwood Engineering Ltd general liability acknowledged 15d 8d ago $12,000 QBE Tom Baxter
CLM-26002 Rangitoto Civil Ltd contract works notified 9d 7d ago $26,000 Vero Tom Baxter
CLM-26003 Tui Orchards Ltd rural settlement offered 61d 5d ago $84,000 Rosser Underwri... Tom Baxter
CLM-26005 Pemberton Legal Ltd professional inde... information reque... 45d 3d ago $30,000 Delta Insurance Grant Milne
CLM-26010 Delacourt Property Ltd material damage notified 3d 2d ago $4,800 Chubb Tom Baxter
Overdue updates (Insurance Brokers Code of Practice 7.1(a): keep clients informed in a timely manner)
CLM-26001 Southern Cross Freight Ltd: 26 days since anyone told them anything
CLM-26004 Harbourview Apartments Body Corporate: 20 days since anyone told them anything Compliance check
================
Rule Breaches Worst Source
-------------------------------------------------------- -------- ---------------------- --------------------------------------------------------------------------
Contact the client at least fourteen days before expiry 3 POL-20012 (5d) Insurance Brokers Code of Practice 2022, clause 7.2(a)
Terms of engagement in writing before you act 2 Blue Duck (700d) Insurance Brokers Code of Practice 2022, clause 4.2(a)
Disclose what you earn to individuals and small business 2 POL-20021 (254d) Insurance Brokers Code of Practice 2022, clauses 6.1(a) to 6.1(c)
An advice record for every placement 9 POL-20034 (61d) FMC Act 2013 ss 431I to 431P and FAP licence standard condition 1; Corp...
Record the nature and scope of the advice, and its li... 1 POL-20012 (272d) FMC Act 2013 s 431J; Code of Professional Conduct for Financial Advice ...
Record the reasons the advice is suitable 0 Code of Professional Conduct for Financial Advice Services, standard 3
Disclosure given at the point the advice is given 1 POL-20032 (124d) Financial Markets Conduct Regulations 2014, regulations 229C to 229F
Keep clients informed on the progress of a claim 2 CLM-26001 (26d) Insurance Brokers Code of Practice 2022, clause 7.1(a)
Acknowledge, update every ten business days, resolve ... 1 complaint 05 Aug (41d) Insurance Brokers Code of Practice 2022, clauses 9.2(b) and 9.4(b); ASI...
Contact the client at least fourteen days before expiry (Insurance Brokers Code of Practice 2022, clause 7.2(a))
POL-20012 Coastal Storage Ltd Expires 20 Sep and no contact is recorded
POL-20005 Blue Duck Cafe Group Ltd Expires 27 Sep and no contact is recorded
POL-20006 Blue Duck Cafe Group Ltd Expires 27 Sep and no contact is recorded
Terms of engagement in writing before you act (Insurance Brokers Code of Practice 2022, clause 4.2(a))
Blue Duck Blue Duck Cafe Group Ltd On cover with no signed terms of engagement
Rob and Alice Ngatai Rob and Alice Ngatai On cover with no signed terms of engagement
Disclose what you earn to individuals and small business (Insurance Brokers Code of Practice 2022, clauses 6.1(a) to 6.1(c))
POL-20021 Janet Whitmore Advice given with no remuneration disclosure on file
POL-20032 Rob and Alice Ngatai Advice given with no remuneration disclosure on file 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.
Honest trade-offs
What you give up
- remove_circle No insurer feeds and no multi quote aggregator. You record what the market quoted, you do not rate through this. If your brokerage places most of its business down a direct connection into an insurer, keep that connection and use this for the cycle, the file and the reporting.
- remove_circle No trust accounting, and that is deliberate. Premium receipts, client money and the broking trust account stay in the system that holds them today, under the Insurance Intermediaries Act 1994 and Division 7.8 of the Corporations Act 2001. This holds the policy lifecycle, the advice, the claims and the brokerage you earn.
- remove_circle No client portal and no phone app. Documents and dashboards are HTML pages you print or send, not screens a client logs into. There is no drag and drop board and nothing updates live while two people watch it.
Two ways to run it
Run it yourself, or have it run for you
Open source
Run it yourself
Free
- 1 Clone the repo
- 2 npm run demo, then open the folder in Claude Code
- 3 Type /renewals-due
- 4 Import your JAVLN export and point it at your own Postgres
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
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 repo, 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 one command lists every gap with the clause it breaches. What no software can do is make the advice good. Read docs/compliance.md: 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 CSV, run one import command, and it lands in your own Postgres with the client links and the expiry dates intact. Run it with --dry-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 docs/replace-javln.md 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 runs the right one. The slash commands are there so the same question gets the same answer every time, in the words your industry uses: /renewals-due, /claims-open, /endorse, /advice-record. 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 repo and run it yourself.
Broking for Claude Code is MIT licensed and published by Enterprise DNA at github.com/Enterprise-DNA-OS/broking-for-claude-code.