Pricing
Priced by what you run, not by who logs in.
Two things carry a price: the environments you run, and the people who build with Fusion. The people who use what you build are not licensed at all — however many of them there are.
What you run
Scales with your workload
Hosting and monitoring are optional. Run the environments yourself, at any provider or on your own servers, and those two lines come off.
Who builds with it
A delivery team, not your user base
A typical delivery is a handful of people. The application they build carries no seat fee at all.
However many people use the software you build — ten, ten thousand, everyone you serve — none of them is licensed. The seats above are for the few people who build with Fusion, and that is the whole difference between this and a platform that charges you for every person who logs in.
That is what “no per-seat licensing” means on this page: the seats above licence the few people who build with Fusion, and nobody is ever charged for using what they built. Growing your user base is not a pricing event.
List prices per year. Prices are set in Australian dollars; the US dollar figures are rounded equivalents, not a live conversion, and the rate is fixed in the agreement. Delivery services are quoted per engagement. What you actually pay depends on how many environments you run and how many people build with Fusion, so treat this as the basis of a quote rather than the quote itself.
How to start
Start with one real initiative.
No transformation programme up front. Prove Fusion on one live initiative, then decide.
Readiness Assessment
Fixed-scope diagnostic
Map where your delivery fragments, where the trace breaks, and the highest-value place to start.
Start hereDelivery Pilot
4–6 weeks, one live initiative
Run the initiative through discovery, blueprint and assurance — with evidence you can put in front of your exec team.
Start hereOperating Model Sprint
8–12 weeks, after the pilot
Once the pilot proves value, redesign how work moves from idea to production across the organisation.
Start hereNo lock-in
Here is exactly what it would cost you to leave.
Every platform claims there is no lock-in. Almost none of them will tell you what walking away actually involves. So here is the honest ledger, before you sign anything rather than after.
You keep
-
Your documents
The discovery, the design decisions, the delivery record. They are plain files sitting in your repository, and they stay readable with or without us.
-
Your business logic
The models and the rules that describe how your organisation actually works. That is the part that took the thinking, and it is ordinary Rails that any Rails developer can pick up.
-
Your database, and everything in it
A standard PostgreSQL database with a standard schema. Not a file export you have to reassemble — the live thing, running, with your data in it.
You would have to replace
-
The interface
Fusion generates your screens. Take Fusion out and the screens go with it, so you would build your own. This is the real cost of leaving and we are not going to pretend it is small.
-
The AI-assisted pipeline
The path from discovery to delivery, and the conventions that keep AI output as reviewable work. You would go back to whatever you were doing before.
That is a viable escape hatch, not a full system replacement. You would be rebuilding an interface, not rebuilding a system.
Now weigh it against leaving a rented platform
Your data comes out as a file export that somebody has to reassemble into a working system. Your business rules were written in a language that runs nowhere else. Your screens were configuration inside a product you no longer have access to. There is no escape hatch, viable or otherwise — and that is not an oversight in the design. It is the commercial model.
Decide with working software, not a proposal.
Take the Challenge with a workflow of yours, and put real screens next to these prices before you commit to anything.