Instead of ClickHome
Stop paying ClickHome per house. Own the system that runs every build.
Enterprise DNA shapes your version around your stages, your contracts and your trades, carries your ClickHome jobs and clients across, and runs it for you. Your volume goes up; the software line does not.
ClickHome lists A$225, A$375 and A$550 for each dwelling, minimum five jobs, plus A$100 a month (A$1,200 a year) for its customer portal.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
How the fee works
A licence fee on every slab you pour, for records that never change shape
ClickHome's plans page prices each dwelling once: A$225 on Build, A$375 on Manage, A$550 on Succeed, with a five-job minimum spend. The Connect portal adds A$100 a month, and Enterprise is priced on a sales call by volume. Whatever the tier, a home builder keeps the same things: clients, homes, contract stages, budgets, costs, orders, variations, claims, trades and a site diary.
A fee that grows with your order book
Every dwelling you enter is charged again. A good year of sales is also a bigger software year, though the records behind house twenty look exactly like the records behind house two.
Claims and variations held back a tier
Build at A$225 tracks the site. Raising progress claims, approving variations and tracking costs start on Manage at A$375 a home. The parts that bring the money in are the parts priced higher.
Margin control on the top plan only
Pricing variations and controlling margins are listed under Succeed at A$550 a dwelling. Knowing which home is losing money should not depend on which plan you picked at signup.
The client view as a monthly extra
Connect, the branded portal where clients see progress and lodge maintenance requests, is A$100 a month on top of the per-home fees: A$1,200 a year to show clients their own build.
Enterprise means a sales call
Hosted or on premise, with your own integrations, is per-build licensing with volume pricing and a Contact Sales button. The bigger the builder, the less the price is written down.
Ten years of homes behind a login
Defects, warranty claims and disputes arrive years after handover. If your history lives in the vendor's system, reaching it depends on your account. In your own database it is simply there.
What you get instead
Every home on one record, with no fee for starting the next one
Getting paid
Stage claims that cannot outrun the contract
Each claim carries its amount and due date and is tested against the contract before it leaves the office.
- check A claim that would take a home past its contract price plus approved variations is stopped, with no way to override it
- check Unpaid claims rise to the top of the morning list with the days overdue, and a firm chaser is drafted for you to send
- check Claim paperwork comes out in your brand, showing the stage, the total claimed to date and each approved variation
- check A home where costs keep landing but nothing has been claimed for 30 days is called out before it squeezes cash
Job cost
Budgets that count orders the day they are placed
The contract estimate becomes the budget for each home, and every purchase order holds money against its line from the moment it is raised.
- check Ordered but not yet invoiced is counted, so a line cannot look healthy while the bricks are still in transit
- check The moment a line tips over, you see the overrun in dollars and choose the cause: scope, price or waste
- check Every home ranked by forecast margin, weakest first, at today's numbers, not on a premium plan
- check Ask it which house type makes you money and which one does not, across every home you have built
On site
Variations in writing and trades with current cover
The shortcuts that end in a dispute are refused, and each refusal says why.
- check No variation work is started or claimed until it is approved in writing, with the name of the person who said yes
- check A trade whose public liability has expired cannot be put on a home, and cover expiring soon is flagged ahead
- check The site diary is one sentence to add, and in a dispute it is your record of what was said and when
- check Late tasks, quiet sites and orders open too long all land on the same list, so nothing slides for a month
Ownership
Your records, your database, no per-dwelling meter
Runs on one laptop to start, or on your company's own database for the whole office. It works through Claude Code and other AI assistants: the records are the product, the assistant is just how you ask.
- check Bring your ClickHome clients, homes and costs across: we map its export to your records, test run first
- check The first load doubles as an audit, flagging homes with no signed contract date and costs with no budget behind them
- check The rules it enforces sit in a plain file you can read and change to suit your contracts
- check Open source and yours: back it up, report on it from anything, and keep the full history of every home you built
Make it yours
Design your own ClickHome replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from ClickHome. 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 ClickHome data across and run it for you.
Switching
How to switch from ClickHome
A move usually involves exporting your records, mapping ClickHome's different columns, checking a test import, and running both systems side by side before you switch.
- 1
Export your records
Export the ClickHome records you want to bring across, including clients, jobs and cost history. ClickHome's export options are not documented in the available material, so export what your account allows, usually Excel, and check with ClickHome if you need help. Decide which history you need before you start the import.
- 2
Map and load the data
ClickHome's columns differ from the format the free version imports, so the records need to be matched to the replacement's fields before loading. Run a test import first, then load the data once the mapping is ready. If Enterprise DNA runs the setup, they handle mapping your ClickHome jobs, clients and costs and carry out the test run.
- 3
Check the import flags
Review what the import flags and resolve anything that needs attention. Checks can identify jobs without a signed contract date or costs without a budget line. Compare the imported records and numbers with ClickHome, and make sure the fields and history you chose have come across as expected. Do not treat a completed import as proof that every record is correct.
- 4
Run both systems side by side
Keep ClickHome and the replacement in use together for a short period. Use that time to check the records and numbers against ClickHome and confirm your team can find what it needs in the database through Claude Code. Keep track of anything that does not match or is missing, and correct it before you stop relying on ClickHome.
- 5
Switch off ClickHome
Once the checks are complete and your team can work from the replacement, move your day-to-day work across and stop using ClickHome. Keep the exported records you need for your own reference. The replacement has no web front end, so your team works with the database through Claude Code in plain language.
Where the real effort goes
The real work is matching ClickHome's different columns to the replacement's fields, setting up your own stages and claim terms, and deciding how much history to bring across. ClickHome's export options also need checking with ClickHome. Enterprise DNA handles the mapping and test run when you have them run the setup.
Not ready for a call?
Get your ClickHome switch plan by email
We will send you the step-by-step plan for moving your business off ClickHome, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your ClickHome switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to run it
Set it up yourself, or have it set up and 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 /attention
- 4 Map your ClickHome exports to the import and point it at your own database
Omni by Enterprise DNA
Have Enterprise DNA build and run your version
One setup fee, then a monthly retainer
- check We bring your ClickHome clients, homes, contract values and cost history across, checked against the old system
- check We set it up around your contract stages, your claim terms, your house types and your trades
- check A client view, a site screen for supervisors or a link to your accounts, built when your business needs one
- check It runs inside Omni, our managed Command Centre, beside the rest of your business
Questions
Instead of ClickHome, answered
We build a lot of homes a year. Does the cost change with volume? expand_more
No. The free version has no per-home fee at all, and the version Enterprise DNA builds is a setup fee then a retainer. Starting another home adds a row to your records, not a line to an invoice.
ClickHome ties claims to required inspections. Can this? expand_more
The free version already refuses a claim that passes the contract plus approved variations, and refuses variation work nobody approved in writing. Tying each stage claim to your own inspections is set up when Enterprise DNA builds your version around your contract stages.
Can we bring our history out of ClickHome? expand_more
Yes, but be clear on how. The free version imports Buildxact's export format, and ClickHome's export has different columns. Mapping your ClickHome jobs, clients and costs across is part of what Enterprise DNA does when we build your version, with a test run first and the numbers checked against ClickHome before you stop paying for it.
Our supervisors live on the iPad app and clients use the portal. What happens to those? expand_more
The free version is run from the office, in plain language. When a supervisor screen or a client view earns its keep, Enterprise DNA builds it into your version over the same records, with no monthly portal add-on.
What does the version Enterprise DNA builds include? expand_more
Your ClickHome data carried across, your stages, claim terms and house types set up, your claim and variation paperwork in your brand, your team shown how to ask it for what they need, and someone to call in week one. It runs alongside everything else Enterprise DNA runs for you.
Build more homes without a bigger software bill
30 minutes with Sam. We look at what ClickHome costs you across a year of homes, what your records actually hold, and what your own version would look like. If it is a fit, we build it and run it. If it is not, take the free version and run it yourself.
Builders for Claude Code is free and open source, published by Enterprise DNA.
Done paying for ClickHome?
Get your version built