“How much will it cost?” is the first question almost every business asks about custom software, and the honest answer is: it depends. That is not a dodge. Two projects that both sound like “a customer portal” can differ in cost by an order of magnitude. This guide explains what actually drives the price, so you can budget sensibly and compare quotes fairly.
The five things that set the price
1. Scope: what the software has to do
Every feature adds design, development, testing and maintenance time. A simple internal tool with a login and a few forms is a very different project from a platform with payments, roles and permissions, reporting and integrations. The single most effective way to control cost is to be clear about what is essential for launch and what can wait for version two.
2. Integrations with other systems
Connecting to your accounting software, CRM, payment provider or an older internal system is often where hidden effort lives. Well-documented, modern APIs are quick to work with. Legacy systems, spreadsheets that act as a database, and tools with no API usually take longer.
3. Design and user experience
A clean, functional interface costs less than a heavily branded, animated one. Neither is wrong, but you should decide how much polish your users actually need. Software your staff use eight hours a day deserves careful usability work, because small frictions multiply.
4. Data and migration
If you are replacing an existing system, moving its data across cleanly takes planning. Messy or duplicated records have to be cleaned, mapped and checked. It is rarely glamorous, but skipping it causes problems after launch.
5. Security, compliance and hosting
Handling payments, health information or other sensitive data raises the bar for how the software is built, tested and hosted. Build these requirements in from the start. Adding them later costs more.
Common pricing models
- Fixed price: a set cost for a clearly defined scope. Good when requirements are well understood. Changes mid-project are handled as separate, agreed change requests.
- Time and materials: you pay for the effort spent. Flexible when requirements will evolve, but it needs good reporting so you can see where the budget is going.
- Retainer: a monthly arrangement for ongoing improvements and support after launch.
Neither model is automatically cheaper. What matters is that the quote matches how well the scope is defined.
Costs people forget
- Hosting, domain and third-party service subscriptions
- Ongoing maintenance, security updates and bug fixes
- Staff training and documentation
- Changes you will want once real users start using it
A useful rule of thumb is to plan for ongoing support and improvement as a normal part of owning software, not as a surprise.
How to get a quote you can trust
- Write down the problem, not just the solution. “Our team re-enters orders three times” is more useful than “we need a portal.”
- List must-haves and nice-to-haves separately.
- Ask what is not included in the quote, such as hosting, training and support.
- Ask for a timeline with milestones, so you can see progress each week.
- Compare like with like. A lower number that leaves things out is not cheaper.
The bottom line
Good software pricing starts with a conversation, not a rate card. The clearer you are about the problem you are solving, the more accurate and fair the quote will be. If you would like a second opinion on a scope or a quote you have received, we are happy to take a look.
