Pricing
Priced by what you run, not by who logs in.
Two things have a price: the environments you run, and the people who build with Fusion. We do not license the people who use what you build, at any number of users.
What you run
Scales with your workload
Hosting and monitoring are optional. If you run the environments yourself, at any provider or on your own servers, we remove those two lines.
Who builds with it
A delivery team, not your user base
A typical delivery team is a small number of people. The application they build has no seat fee.
Any number of people can use the software you build: ten, ten thousand, or everyone you serve. None of them is licensed. The seats above are for the few people who build with Fusion. That rule is the full difference between Fusion and a platform that charges you for each person who logs in.
On this page, “no per-seat licensing” has one meaning. The seats above license the few people who build with Fusion. We never charge anybody to use the software you build. Growth in your user base is not a pricing event.
List prices are yearly. We set prices in Australian dollars. The US dollar figures are rounded equivalents, not a live conversion, and the agreement fixes the rate. We quote delivery services for each engagement. The amount you pay depends on how many environments you run and how many people build with Fusion. Treat these prices as the basis of a quote, not the quote itself.
How to start
Start with one real initiative.
No transformation programme is necessary at the start. Prove Fusion on one live initiative, then decide.
Readiness Assessment
Fixed-scope diagnostic
The assessment maps where your delivery splits into fragments and where the trace breaks. The assessment also finds the highest-value place to start.
Start hereDelivery Pilot
4–6 weeks, one live initiative
We run the initiative through discovery, blueprint and assurance. You receive evidence that you can show to your executive team.
Start hereOperating Model Sprint
8–12 weeks, after the pilot
After the pilot proves value, we redesign how work moves from idea to production across the organisation.
Start hereDo you need to replace a legacy system?
A legacy replacement is a different engagement from the three above. The engagement starts with a fixed-scope discovery and design, sets a five-year TCO baseline, and quotes the build from the scope. A value-based deal on the TCO savings is open for discussion. Save up to 90% on five-year TCO.
Do you run Salesforce, ServiceNow or Dynamics 365?
Escape SaaS is a different engagement from the three above. We read your system from the platform's metadata, then rebuild it on Fusion. In the same work, we fix the pain points, rewrite the user guides and close the compliance gaps.
No lock-in
Here is exactly what it costs you to leave.
Every platform claims there is no lock-in. Almost none of them will tell you what an exit involves. So here is the honest ledger, before you sign, not after.
You keep
-
Your documents
Your documents are the discovery, the design decisions, and the delivery record. They are plain files in your repository. They stay readable with or without us.
-
Your business logic
Your business logic is the models and the rules that describe how your organisation works. The business logic is the result of the design work. Its code is ordinary Rails that any Rails developer can maintain.
-
Your database, and everything in it
You keep a standard PostgreSQL database with a standard schema. The database is not a file export that you must reassemble. You keep the live database, in operation, with your data in it.
You must replace
-
The interface
Fusion generates your screens. If you remove Fusion, you also remove the screens, so you must build your own. This rebuild is the real cost of an exit, and we do not pretend it is small.
-
The AI-assisted pipeline
The pipeline is the path from discovery to delivery, and the conventions that keep AI output as reviewable work. If you remove Fusion, you return to the process you used before.
The exit is a practical route out, not a full system replacement. You rebuild an interface, not a system.
Now compare it with an exit from a rented platform
Your data leaves as a file export that somebody must reassemble into a system that works. You wrote your business rules in a language that runs nowhere else. Your screens were configuration inside a product that you can no longer access. The platform gives you no route out. The lock-in is the commercial model. To rebuild a Salesforce, ServiceNow or Dynamics 365 system on Fusion, see Escape SaaS.
Decide with software that works, not a proposal.
Start with Idea to Impact on one of your workflows, and compare real screens with these prices before you commit to anything.