The honest answer: it depends on a lot of factors, and we price every project individually, after a conversation. Below we set out what really decides the price and how to work out whether it pays off against subscriptions — so you know what to ask about and what to expect. We give you a concrete figure only once we know the scope.
An hourly rate rewards working slowly — the longer the project runs, the bigger the invoice. So we price a defined scope instead: we agree what is to be built and quote a price for delivering it, however many hours it takes us.
The practical consequence for you: the cost is known before we start, and the risk of the project overrunning sits with us, not with you. If it turns out along the way that the scope needs widening, we discuss that separately rather than adding hours to the invoice.
There are no per-user fees. Adding more people to the system does not raise the bill, because it is your system, not our subscription. Once it is live, running costs come down to the server and any external services — in one CRM implementation for a sales team, the ongoing licence cost is zero a month.
Ordered by how heavily they weigh. Knowing these points, you can estimate the order of magnitude before you even speak to us.
A simple calculation you can do today, without us:
One more thing worth putting into the sum: subscriptions grow with the number of users and with every price rise from the vendor. The cost of your own system is one-off, and running it does not depend on how many employees you have.
Time is the best publicly available indicator of a project's scale — and the only one we can give without breaching the confidentiality of our quotes.
Migrations can take longer — the largest so far covered 43,943 orders and finished with no discrepancies in the data and no loss of search rankings.
Because with custom software, any figure given upfront would mislead you. The price depends on many factors at once — the number of integrations, the extent of the data migration, the number of roles, multiple languages, how unusual the process is — and the difference between a simple system and one that ties together four external services and carries over history from two legacy tools is not a few per cent, it is a different order of magnitude. A range wide enough to cover both cases would tell you nothing useful.
So instead of a price list we suggest a conversation: describe the process and you will get a quote for a defined scope, together with a delivery date. Free of charge and with no obligation. If your description shows that a cheaper off-the-shelf tool does the job, we will say so in our first reply rather than booking you in for a demo.
The more precisely you describe the process and the integrations, the narrower and more reliable the quote. We answer concretely — with a price, a date and a note on what we are deliberately not doing within that scope.