Nobody can price software from a one-line description, and any company that gives you a firm number for 'we need a management system' is guessing. That does not mean the cost is unknowable. It means the cost is a function of decisions that have not been made yet.
The eight things that actually move the number
1. Number of distinct user roles
Each role is a separate set of screens, permissions and test cases. A system with one admin is not half the work of a system with admin, manager, agent and customer — it is closer to a quarter.
2. Integrations with other systems
A payment gateway, a courier API, an accounting package, an SMS provider. Each one adds development, error handling, reconciliation and a permanent maintenance obligation when the provider changes their API. Integrations are the most commonly underestimated line in any quote.
3. Whether data has to move
Migrating years of records out of spreadsheets or an old system is real engineering: cleaning, deduplicating, mapping fields that were used inconsistently, and proving nothing was lost. On a replacement project this is often ten to twenty per cent of the budget.
4. Reporting depth
A list you can export is cheap. A dashboard that compares this month to last month, filters by branch, and stays fast when the table has two million rows is not. Decide early which reports the business will actually act on, and build only those first.
5. Mobile app or not
A responsive web application covers most needs. A published app adds design, store submission, device testing, offline handling and an update cycle. Ask whether your users genuinely need to work without a browser before adding it to scope.
6. How specific the requirements are
Vague requirements are priced with a risk margin, and the margin is large because the vendor is carrying the uncertainty. A written specification does not just prevent arguments later — it usually lowers the quote.
7. Expected load and uptime
Fifty internal users on office hours is a different engineering problem from fifty thousand customers at midnight during a campaign. Caching, queues, database design and monitoring all scale with the answer.
8. Who maintains it afterwards
Software that another team will inherit needs documentation, tests and a conventional structure. That work is real, it costs money, and skipping it is why so many businesses end up paying to rebuild a two-year-old system.
The costs that continue after launch
- Hosting, domain, SSL and backups
- Third-party services — SMS credits, gateway fees, AI or map API usage
- Security updates and framework upgrades
- Support for the people using it, especially in the first three months
- Small changes, which every live system generates continuously
How to get a number you can trust
- 01Write the list of things a user must be able to do, in plain sentences — one line each
- 02Mark each line as must-have, should-have or later
- 03Name every external system it has to talk to
- 04Say how many users, of which roles, and roughly how much data exists today
- 05Ask for a module-by-module estimate rather than one total, so you can see where the money goes
- 06Ask what is excluded — that answer tells you more about a vendor than the price does
A good vendor will happily reduce your scope. If a company agrees to everything you ask for without ever suggesting something be dropped or deferred, they are selling, not planning — and the difference will show up in month four.