The first question is always "what does a management system cost?", and the only honest answer is that nobody knows before knowing what you need. That sounds evasive, so this article sets out what the number is actually made of — enough for you to estimate for yourself and to read a quote critically.
You are not buying a product, you are buying people's time
This is the fundamental difference from buying machinery. Almost all of the cost is time: analysis, design, development, testing, revisions after feedback, training, warranty.
So anything that increases the hours increases the price, and anything that reduces them reduces it — including things that seem unrelated to software, such as whether someone on your side has the authority to settle a requirement quickly.
Five factors that drive the number
The number of screens and business processes. The largest factor and the easiest to estimate. A system with 8 screens costs far less than one with 30, close to proportionally.
The number of integrations. Accounting software, payment gateways, messaging, time clocks, weighbridges — each connection is its own line item, and each usually costs more than estimated because it depends on the other party's documentation.
How complex the business rules are. "Pick by lot" is one sentence. "Pick by lot, earliest expiry first, unless the customer specifies a lot, and anything within 30 days of expiry needs supervisor approval" is four nested rules — a very different cost on the same screen.
The number of user roles. A system with three roles and properly separated permissions takes considerably more testing than one where everyone sees everything.
Non-functional requirements. Running on phones in a dusty warehouse, working over an unreliable connection, multiple languages, a full audit trail. Each of these affects the whole system rather than sitting inside one screen.
Three costs usually missing from the budget
Your own team's time. The person who understands your operation best will spend many sessions describing it and accepting the result. That is a real cost; it just is not in the quote.
Initial data entry. Item masters, customers and opening balances have to be loaded and cleaned. Where the existing data is spread across many spreadsheets, this step sometimes costs more than a module.
Annual running costs. Servers, domains, backups, and a budget for small changes as the business changes. Ask for the year-two figure, not just year one.
How to read a quote
A single line reading "warehouse management software: $X" gives you nothing to compare against and nothing to cut. Ask for it broken into line items, each one a group of functionality that can be accepted independently.
That does two things: you can see where the money goes, and you can defer what is not needed into a second phase. In most projects we survey, roughly a third of the functionality named at the first meeting can be postponed without affecting whether the system works.
Also ask about three things quotes usually omit: how a mid-project change of requirements is handled, who owns the source code after acceptance, and what the warranty covers and for how long.
A rough range for planning
A core internal system — a few functional groups, one or two integrations, basic permissions — typically takes 2 to 4 months. Larger plant systems, such as full production management or warehouse management, sit in a different bracket and should be delivered in phases.
Treat that as a planning range, not a quote. The custom software page describes how we survey and break work into line items. If a survey shows an off-the-shelf product solves your problem, we will say so — that is the cheaper answer for you.