Priced on what you deploy, not what you might
Two kinds of work, priced two ways. Both are quoted after we understand the scope, because a number given before that is a guess dressed as a commitment.
Products — licensed
A licence covers the product, the sites you run it at, and the people who use it. Start with one system and add others later; they are separate products and are bought separately. Hosting is yours or ours.
Services — by engagement
Custom development, automation, integration, test engineering and ongoing maintenance are priced by the engagement rather than by the hour, with scope agreed in stages so it can change as you learn.
Included with every product
- Role-based access control and two-factor authentication
- Audit logging of who changed what
- Encrypted backups with a tested restore
- Standard support and continuing updates
- Your data, exportable, whenever you ask
Priced separately
- Additional sites, entities or business units
- Integration with systems you already run
- Data migration from what you are replacing
- Onboarding and training for your team
- Managed hosting, if you would rather not run it
- A standing maintenance team
Pricing questions we are actually asked
Why is there no price list?
Because the honest number depends on how many sites you run, what you are replacing and what has to integrate. We would rather scope it in one conversation than publish a figure that turns out to be wrong for you.
Can we buy one product rather than the whole catalogue?
Yes. Each is sold and deployed on its own. They share an engineering platform, so they fit together if you buy more than one, and none of them requires that you do.
Do we own the software and the data?
You own your data outright, and for custom work you own the source code and can take it in-house. For licensed products you own your data and can export it at any time.
How long does a deployment take?
It depends on migration scope more than on the software. We scope a phased rollout during the demo and put it in the proposal, rather than quoting a timeline before seeing your data.
What happens if we want to leave?
You export your data and go. For custom work the source is already yours. We would rather you stayed because the software earns its place.