How we price
What you would be paying for, and when
Three stages, priced three different ways, with the boundaries stated before any work starts. What is not on this page is a number — and the reason for that is on this page too.
How engagements are priced
The review is a fixed price
Agreed before it starts, and it does not move. You receive a map of your systems, the cost of the manual handling, a target architecture and a sequenced plan — and you keep all of it whether we build it, your team builds it, or someone else does.
The build is fixed against what the review scoped
Not against a guess made on a phone call. Anything genuinely discovered later is quoted and agreed before it is started, rather than appearing on an invoice. That is only possible because the review happened first.
Cutover and the weeks after go-live are inside the build price
Not billed on top. They are the two stages that get quoted separately and the two where an integration actually fails, so pricing them as extras would put our interests on the wrong side of yours.
Support is month to month
Thirty days’ notice, no minimum term and no exit fee. There is nothing to lock you into, because there is nothing you would have to leave behind — the system runs in your account either way.
No platform licence and no per-message charge
You are not renting a runtime from us and you are not metered on volume. A busy quarter costs you no more than a quiet one, which means growing your order book is never a conversation with us about pricing.
You pay the cloud provider directly, at cost
The infrastructure sits in your own account and that bill goes to the provider, not through us. There is no margin on it and you can audit every line. We estimate it during the review and tell you which services drive it.
Quoted in AUD. No GST is charged. Support is month to month — no minimum term, and cancelling does not cost you anything you already own.
Why there are no prices on this page
Because we would have to make them up. Integration scope is discovered rather than specified — that is the whole reason the review is paid work rather than a free proposal. A firm that publishes a build price before seeing your systems is quoting a number it will later need to renegotiate, and you are the one who pays when that guess is wrong. After the review you get a fixed price, in writing, against a scope you have read.
What moves the number
What makes one project bigger than another
Not page counts and not message volume. These are the things that genuinely change how long the work takes, in roughly the order they matter.
- How many systems have to agree with each other, and whether any of them are closed
- How many trading partners, and whether each has its own format and certification cycle
- How many document types are in scope — an order is not the same job as a despatch advice
- Whether amendments, cancellations and returns are in scope, which is where the real complexity lives
- How clean the underlying data is: one product barcode standard, or four
- Whether anything has to run in parallel with a system you are also replacing
Before you call
Tell us what you run
We are not going to price a build from a form — nobody honestly can, and that is what the review is for. This just means the first conversation starts from your situation rather than from scratch.
Ask what your situation would cost
The review is where that question gets a real answer, and the first conversation is where we work out whether a review is even the right next step.