Perpetual licence
- Best for
- Capex / long-term commitment
- Upfront
- Licence plus implementation
- Ongoing
- Annual AMC from year two
- Term
- Licence does not expire; AMC is annual
- Users
- Named-user band
Commercial models
Three ways to buy. The same product.
Product capability does not change across commercial models — only the investment structure does. Sales sizes user bands and quotes against your edition. No list prices are published here, and there is a reason for that.
Model chooser
The right structure depends on your balance sheet, not the software
You get the same product either way. Pick the priority that matches your internal conversation and see which structure it points to — and why.
What matters most to your finance team?
Pick the one that sounds most like the conversation you are having internally.
Flat annual
- Best for
- Predictable OPEX
- Upfront
- Implementation only
- Ongoing
- One annual fee, support and updates included
- Term
- Multi-year engagement
- Users
- None within the agreed band
Subscription
- Best for
- Pay as you grow
- Upfront
- Implementation separate
- Ongoing
- Recurring licence, support and updates included
- Term
- Minimum twelve months
- Users
- Named users on progressive slabs
What is deliberately not on this page
A published price would have to assume your edition, user band, hosting and implementation scope. Every one of those moves the number, so a list price is a guess you would end up unpicking during negotiation. We would rather quote once, against something real.
Implementation is always quoted separately. It is real work — data, masters, training and cutover — and bundling it into a licence figure hides what you are actually buying.
Customisation is scoped as change requests. Approved, estimated and tracked, so it never becomes an open-ended line.
Community is subscription only. B1 and Enterprise offer all three models.
Cloud is the default conversation. Self-hosted stays a first-class option for controlled infrastructure or remote sites.
Next step
Ask us to model it against your team.
Share your edition interest, rough team size and hosting preference. You get a commercial structure with the assumptions written down — so your finance team can compare it against anything else on the table.
- 1
You send a note
Two lines on your projects and where control leaks today. No form marathon — the optional fields exist only to make the first call sharper.
- 2
A 20–40 minute walkthrough
We narrate the Procurement to Pay cycle against how you actually work. It is your process on the screen, not a feature tour.
- 3
A written recap
Scope, edition fit and what a sensible first phase would cover — in writing, so you can circulate it internally.
Request a structure
Perpetual, flat annual or subscription — costed against the same scope so the comparison is fair.
Request a walkthroughNo obligation and no procurement process to start a conversation.