Instead of InsuredHQ
Step off InsuredHQ. Keep your book in your own hands.
Enterprise DNA builds your version around the way your office renews, places and follows up claims, maps your InsuredHQ records across, and runs it for you. Your ledger keeps running in Xero.
InsuredHQ publishes no price. Its own site describes an implementation cost and a pay-as-you-go fee structure, and offers a demo or a chat instead of a price list. Checked 25 October 2026.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the InsuredHQ quote pays for
A platform sized for insurers, priced in private
InsuredHQ sells one cloud system to insurance companies, managing agents, brokers and startups. A broking office pays for the platform's reach, not only for the parts it opens each day. From insuredhq.com, checked 25 October 2026.
A fee you only hear in a demo
There is no price page. The site points you to a free demo or a chat, and the fee follows from that conversation.
Pay as you go, on their meter
InsuredHQ describes its fees as pay-as-you-go. Ask what the meter is tied to, because a fee that tracks your activity grows as your book does.
An implementation cost up front
The solutions page names an implementation cost alongside the ongoing fee, so the bill starts before anyone in your office logs in.
Insurer features a brokerage may never use
Reinsurance accounting, small-ticket insurance rating and multi-branch, multi-currency set-up sit in the same platform as your renewal list.
A second ledger beside Xero
InsuredHQ keeps its own debtors ledger and posts to Xero or another general ledger through a journal engine. That is two places to reconcile.
Records reached through their screens
Your clients and policies sit on InsuredHQ's servers. Getting a full copy out in a form you can query is something to ask about before you sign.
What you get instead
Only the broking, and all of it yours
Renewals
Every expiry with a stage and a name beside it
A renewal is not just a date on a policy. Each one carries where it is up to and who owns the next step, so the Monday meeting starts from one list.
- check Policies expiring this month with no client contact logged, largest premium first
- check Renewals waiting on underwriter terms past the date they were promised
- check Covers that lapsed but still show as active, raised before a claim finds them
- check Which broker holds which renewals, so a sick day does not stall the week
Claims
Claims followed up before the client has to chase
Each claim keeps its events in order, and the follow-up list is ranked by the silence, not by the claim number.
- check Open claims where the client has heard nothing in fourteen days
- check Claims lodged with an insurer and never acknowledged, with the insurer named
- check A plain-English update drafted from the claim history for a broker to check and send
- check The whole history of a claim, oldest event to newest, in one answer
Advice
Advice files that stand up to a review
What was asked for, what was recommended and why, the options set aside and how the brokerage is paid are each kept as their own field, then checked against the rules.
- check Placements with no advice record behind them, found in one question
- check Checks written against the Financial Markets Conduct Act duties and the Code of Professional Conduct for Financial Advice Services
- check A rule changed in plain words, and the next check uses it
- check Disclosure gaps listed so they are fixed before an audit
Owned
Your records, your documents, your accounting left alone
The book lives in a database the brokerage owns. Branded documents come straight from it, and the money side stays in the accounting system already doing that job.
- check Renewal summaries and claim letters in your own colours and name
- check Brokerage earned by insurer and by month, ready to tie back to Xero
- check Read-only pages for the week and the renewal cycle
- check No premium receipts or client money held here, ever
Make it yours
Design your own InsuredHQ replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from InsuredHQ. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your InsuredHQ data across and run it for you.
Switching
How to switch from InsuredHQ
The move involves exporting the records you need, mapping InsuredHQ’s columns, checking the imported data, and running both systems side by side before you switch.
- 1
Export your records
Export what InsuredHQ’s reports let you take as spreadsheets, and check with InsuredHQ about the options available on your account. Include the clients, contacts, policies and claims you want to move, plus any history you need. If the reports do not give you a full copy, ask InsuredHQ for one.
- 2
Map and load the data
Map InsuredHQ’s columns to the records Broking for Claude Code reads, then load the data into its database. The columns differ from the ones the free version reads by default, so check the mapping before loading. Run the import’s test first. It should count every client, policy and claim against the totals in your InsuredHQ records.
- 3
Review the test results
Check the test counts against InsuredHQ and review anything the import marks for attention. Confirm that the records you chose to bring across are represented as expected, and resolve mapping issues before loading the data for real. If you cannot account for a difference, check the source records or ask InsuredHQ for a fuller copy before moving on.
- 4
Run both systems side by side
Keep InsuredHQ available while you use Broking for Claude Code with your team. For a short period, check the records and work in both systems so you can confirm the imported information is usable and spot anything that needs correcting. Agree which system is the record you update during this period, so changes do not get lost between them.
- 5
Switch off InsuredHQ
Once you have checked the imported records and your team is ready to work in Broking for Claude Code, make it the place you update your brokerage records. Confirm that the information you need is there before you stop using InsuredHQ. Then arrange to close or switch off your InsuredHQ account directly with InsuredHQ.
Where the real effort goes
The real work is usually matching InsuredHQ’s columns to your records, adapting fields and rules to the way your brokerage works, and deciding how much history to bring across. You do not have to move every record if you do not need it. If you have Enterprise DNA install and run the system, they handle the mapping and migration work with you.
Not ready for a call?
Get your InsuredHQ switch plan by email
We will send you the step-by-step plan for moving your business off InsuredHQ, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your InsuredHQ switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Test the free version yourself, or let Enterprise DNA build and run your own
Open source
Run it yourself
Free
- 1 Download Broking for Claude Code from GitHub
- 2 Start the sample brokerage and open the folder in Claude Code
- 3 Ask which policies expire in the next thirty days with no contact logged
- 4 Export your InsuredHQ reports to CSV and ask Claude Code to map the columns
Omni by Enterprise DNA
Have Enterprise DNA build it for you
One setup fee, then a monthly retainer
- check We bring your InsuredHQ clients, policies, claims and contacts across and match every count
- check We leave your ledger in Xero and tie brokerage back to it
- check We set up your classes of business, renewal stages and advice checks
- check It runs inside Omni, our managed Command Center, next to the rest of your business
Questions
Instead of InsuredHQ, answered
What does InsuredHQ cost? expand_more
InsuredHQ does not publish a figure. Its site describes an implementation cost and a pay-as-you-go fee, and offers a free demo or a chat instead of a price list. Bring your current invoice to the call and Sam will total a year of it with you.
InsuredHQ also does billing and a debtors ledger. Where does that go? expand_more
Into Xero, the accounting system InsuredHQ itself connects to. Your own version records policies, renewals, claims, advice and brokerage earned. It never holds client money or a trust account. Enterprise DNA ties the brokerage figures back to your accounting so you reconcile in one place.
Can we get our records out of InsuredHQ? expand_more
Export what its reports let you take as spreadsheets, and ask InsuredHQ for a full copy if you need more. Its columns differ from the ones the free version reads by default, so Enterprise DNA maps them for you, with a test run first that counts every client, policy and claim against what you had.
We have a client portal on InsuredHQ. Do we lose it? expand_more
The free version has no portal. If your clients use one to see their policies or lodge a claim, Enterprise DNA builds that into your version, reading from the same database your brokers work from.
Is this only for big brokerages? expand_more
No. It suits a broking office of a few people as well as a larger one, because there is no charge per broker and no insurer features to carry. You pay one setup fee and a monthly retainer for the system built around your office.
Find out what the meter is really costing you
30 minutes with Sam. Bring your InsuredHQ invoice. We look at what you pay in a year, which parts your brokers open every week, where your ledger would sit, and what your own version would look like. If staying on InsuredHQ is the better call, Sam will tell you.
Broking for Claude Code is free and open source, published by Enterprise DNA.
Done paying for InsuredHQ?
Get your version built