Budget6 min
What a custom business system costs, and what actually drives it
The quote does not move with the number of users, but with how many exceptions your process has, how many systems it must talk to, and how much history.
It is the first question in every first call, and it is a fair one. The honest answer is that a custom system has no price list, but it does have three variables that explain almost all the difference between a six-week project and a nine-month one.
The three things that move the quote
- Process exceptions. A linear order cycle is modelled in days; one with per-customer pricing, tiered discounts, commissions and partial returns is modelled in weeks.
- Systems to connect. Every integration is a project inside the project: understanding how the other system exposes its data, handling failures, deciding who wins in a conflict.
- Historical data. Importing five years of messy records costs more than building the module that will use them.
Why the user count is beside the point
In licensed software the price grows with seats, because that is how the vendor makes money. In a custom system the cost is the build: the tenth user costs nothing, the tenth process costs. Which is why it pays to count processes, not people.
How to spend less without cutting the project
By releasing area by area. The first usable module can go live within weeks and start returning value while the rest is being built. That pushes part of the spend later and, more importantly, puts something real in users' hands before the specification goes stale.
An order of magnitude
A vertical module over one well-defined process lands in a few weeks of work. A system covering the full order-to-cash and purchase cycle, with two or three integrations and a migration, lands in four to six months. Any number more precise than that, given before anyone has seen the processes, is a made-up number.