Everyone who requests a quote wants to hear one number, and any developer who gives that number without asking questions first is guessing. Asking about custom software development cost is a fair question. The answer is only reliable once five things are on the table.
The cost of custom software is set by the size of the application, the number of integrations with other systems, the complexity of the business rules, the quality requirements for security and compliance, and the maintenance and further development after go-live. Software companies translate those factors into hours per role and a contract model. Without those five factors, every price is an estimate of an estimate.
Below we walk through the five factors, show how software companies calculate development costs, compare custom software with per-user licenses over five years, and close with the points to check on a quote. That gives you a well-founded estimate before you talk to a vendor.
The five factors that drive custom software development cost
Every budget for custom software starts with the same five questions. The more concrete your answers, the smaller the margin in the estimate.
- Size: screens, processes, and users. An internal dashboard with three screens for one department takes a fraction of the work of a customer portal with logins, roles, orders, and documents for thousands of users. Count the processes the software has to support and the screens they need. That is the first measure of the project.
- Integrations with existing systems. Connecting to an ERP, CRM, or accounting package through a well-documented API is manageable work. Connecting to an outdated system without documentation often costs more than the screens themselves. The number of systems and the state they're in weigh heavily.
- Complexity of the business rules. A scheduling tool that accounts for collective labor agreements, technician certifications, and travel times contains hundreds of decision rules that all have to be built and tested. Simple data entry and storage is cheap. Logic with many exceptions is expensive.
- Quality requirements: security, compliance, and availability. Software for healthcare, government, or the energy sector has to meet stricter requirements for access, logging, and data protection. A requirement such as 99.9% availability also means extra work on infrastructure and testing.
- Maintenance and further development. Software is never finished. Security updates, new user requests, and changing legislation call for a team that knows the application and maintains it. Anyone who forgets this underestimates the budget from the start.
If you're still weighing whether custom software is the right route, our page on custom software development helps with that decision. It also covers when off-the-shelf software is the better fit.
How software companies calculate development costs
Almost every software company works from the same basis: hours times rate. The difference lies in who works those hours, how they're estimated, and which contract model you agree on.
A custom software project needs several roles. An analyst or product owner translates your process into functionality, a designer creates the screens, developers build the frontend and backend, a tester checks the work, and a project lead guards the schedule and the scope. Each role has its own rate and its own share of the hours. A quote that lists developer hours only is usually missing part of the work.
Most agencies build in short cycles of two to three weeks. Each cycle delivers working software and an updated estimate for the rest. That keeps the budget steerable, because you see early whether the assumptions hold.
Three contract models and their price tag
| Contract model | How it works | When it fits |
|---|---|---|
| Fixed price | A fixed price for a scope defined up front | Small, fully specified assignments |
| Time and materials | You pay the actual hours, with an estimate up front | Projects where the scope sharpens during the build |
| Dedicated team | You hire a team for a fixed period per month | Ongoing development and maintenance |
A fixed price sounds safe. Agencies price the risk in, however, and bill every change as extra work. Time and materials gives you flexibility and asks you to steer actively. A dedicated team fits organizations that treat software as an ongoing process rather than a one-off project.
Joris is operations director at an installation company with 60 field technicians. He requested three quotes for a scheduling application and received three totals that were far apart. When he asked, it turned out the cheapest agency had left the ERP integration out of scope and had no tester on the team. The most expensive agency had included six months of maintenance. Only after Joris had all three work out the same five factors could he compare the quotes.
What custom software costs over five years
The build is the visible part of the cost. Over five years, hosting, maintenance, security updates, licenses for underlying components, and further development come on top. In our experience the build is often less than half of the total over that period.
Software without maintenance ages and becomes a risk. The Dutch National Cyber Security Centre describes the risks of legacy systems: missing updates, vulnerabilities, and knowledge that leaves the organization. That is why maintenance is a fixed line in every serious budget, and why total cost of ownership is the number to compare.
An independent view helps sharpen the five factors before you request quotes. In an advisory session on your software and systems we look along with you, and we'll tell you when custom software isn't a good route for you.
Custom software compared with per-user licenses
Off-the-shelf software is usually paid per user per month. That feels low until you multiply it. The sum is: number of users × 12 months × number of years × the package's monthly rate. With 80 users over five years, that is 4,800 user-months. Put the build and maintenance of custom software over the same five years next to it and you have a fair comparison. For off-the-shelf software, also count setup, integrations, and the manual steps that work around the package.
Sanne, operations manager at a wholesaler with 40 employees, paid per user for an order portal. When she wanted to give 25 field sales staff access, the license doubled. She put five years of license cost next to a quote for a portal of their own, including maintenance. The custom software came out lower over that period, mainly because the ERP integration removed the double entry that two employees spent hours on every day.
How to keep custom software development cost under control
You have influence on each of the five factors. These four approaches deliver the most in practice.
- Start with an MVP. Build the smallest version first, one that supports one core process for one group of users. That way you only pay for functionality that has proven its value. Our article what is an MVP shows how to define that scope.
- Freeze the scope per cycle. Schedule new requests for the next cycle, so the team finishes the current one without disruption. Every mid-cycle change costs hours of discussion and rework.
- Use standard components where you can. Login, payments, sending email, and reporting have already been solved. Let the agency build what sets your organization apart and reuse what is common.
- Choose a nearshore model. A team that works partly in the Netherlands and partly in a country with lower labor costs, in the same time zone and with the same way of working, lowers the average rate without changing how you manage the work. That is how we work with engineers in Nijmegen and Sarajevo. Read more about our nearshore model and team extension.
How to assess a quote for custom software
A good quote shows how the total comes about. Check these six points before you compare.
- Assumptions. The quote names which screens, processes, integrations, and user numbers have been included.
- Roles and hours. There is an estimate per role, including testing and project management.
- What falls outside the scope. Written down explicitly, so you know where extra work can come from.
- Maintenance and hosting. A separate amount or rate after delivery, with the name of the team that does the maintenance.
- Ownership of the code. You own the source code. Otherwise you're tied to the vendor.
- Further development. The quote describes how changes are estimated and billed.
At Isatis we give an estimate with clear assumptions after an exploratory conversation, based on more than 30 years of software engineering and 100+ projects. Our 30+ engineers work according to ISO 9001 and ISO 27001, and the team that builds is the same team that maintains the software afterward. That last point shapes the cost over five years more than the hourly rate does.
Frequently asked questions about custom software development cost
What does custom software cost on average?
An average says little, because an internal dashboard and a customer portal with three integrations are miles apart. The price follows from the five factors: size, integrations, complexity of the rules, quality requirements, and maintenance. After an exploratory conversation that puts those factors on the table, you get a concrete indication with the assumptions attached.
Is custom software more expensive than off-the-shelf software?
The initial outlay is higher for custom software, because you pay for the build in one go. Over several years that often turns around: with off-the-shelf software you pay per user and the bill grows with your organization, while the build cost of custom software is a one-off. Calculate both over the same period, including maintenance and setup.
What does maintenance of custom software cost?
Maintenance consists of hosting, security updates, monitoring, and small improvements. Software companies usually charge this as a fixed amount per month or as a percentage of the build cost per year. Always ask who does the maintenance and whether that is the same team that built the software.
Can you pay for custom software in phases?
Yes. By building in short cycles you pay per cycle for working software. A dedicated team per month also spreads the cost. Building an MVP first is the most common way to spread the investment and limit the risk.
From question to well-founded budget
You can answer the question of what custom software costs better yourself than an agency that names a number without asking. Remember these points:
- The price follows from five factors: size, integrations, complexity, quality requirements, and maintenance.
- Software companies calculate hours per role, and the contract model determines who carries the risk.
- Calculate over five years, including maintenance, and set that next to per-user licenses over the same period.
- An MVP, a frozen scope per cycle, and standard components keep the budget under control.
The next step is working out those five factors for your situation. That takes about an hour and produces an estimate with assumptions you can check yourself. Schedule an exploratory conversation with our team and you'll receive a concrete estimate with clear assumptions, even if our advice is to start small first.
