Pricing
There is no price list, and you should be suspicious of one.
Every quote here is written for the specific work. What we will do instead of publishing a table is tell you exactly how engagements are shaped, what moves the number, and what you get in writing before anyone starts.
Three shapes
Nearly everything lands in one of these.
The shape follows the work. A one-time build is priced differently from something we keep alive for you, and both are different from a subscription to a product that already exists.
Fixed-scope build
A defined piece of work with a written scope, a set of deliverables and a price agreed before it starts. Best when the outcome can be described clearly. Change requests are quoted separately rather than absorbed quietly.
Ongoing support
A recurring arrangement covering maintenance, updates, monitoring and a defined amount of change work each period. Best for something already live that has to stay live.
Subscription
Access to our platform, billed per period against a signed order. Configuration, data migration and training are quoted alongside it rather than assumed to be free.
What moves the number
Five things, in roughly this order.
None of these are surprises once you have seen a few projects. They are listed here so you can estimate your own position before you talk to us.
- 01How many kinds of user. One role is a tool. Six roles with different permissions is a system, and the permission design alone is real work.
- 02Whether it has to talk to something else. An integration is only as clean as the system on the other end, and some of them are not clean at all.
- 03What happens when someone is wrong. Corrections, approvals, overrides and audit history are usually half the build and almost never in the first description of it.
- 04Whether the data already exists. Migrating years of records out of a legacy system is its own project and gets its own line.
- 05Who has to be trained. Software a crew will not use is not cheaper, it is wasted. Rollout is scoped, not hoped for.
What you get before you commit
A written quote, and the terms it sits under.
No verbal numbers and no invoice that arrives larger than expected. The paperwork exists before the work does.
A quote names the scope, the deliverables, the price, the payment schedule and what is explicitly excluded. Ongoing arrangements name the renewal terms and the notice period.
Software subscriptions run under a Master Software-as-a-Service Agreement and a Sales Order. The Data Processing Addendum and Privacy Policy that agreement incorporates are published here and are the same documents for every customer.
Where no signed agreement exists, our Terms of Service apply.
Next step
Send us the problem and we will send you a number.
A few sentences is enough to start. If the work is not a good fit, or the honest answer is that you should buy something off the shelf instead, that is what you will hear.