What custom software actually costs (and why it varies so much)

If you've asked two software companies for a price on the same project, you've probably gotten two very different answers. One says $15,000. The other says $150,000. And you're left wondering if one of them is lying.

Usually, neither is lying. They're just answering different questions. Here's why custom software prices vary so much, and how to make sense of the numbers.

What drives the price

Software pricing comes down to four things: how complex the work is, who does the work, how much planning happens up front, and how much support you need after launch.

Complexity. A simple tool that does one thing well is going to cost a fraction of a full system with multiple modules, user roles, integrations, and reporting. The jump from "one screen that solves one problem" to "a platform that runs a department" is enormous. Most of the price difference between quotes comes from a different understanding of what you're asking for.

Who does the work. A senior engineer with 20 years of experience costs more per hour than a junior developer. But the senior person usually finishes faster, writes fewer bugs, and asks better questions. Cheap hourly rates don't always mean a cheaper project.

Discovery and planning. Good software companies spend time understanding your problem before they start building. That time costs money, but it saves more than it costs by preventing rework. Companies that skip this step often deliver something that doesn't quite fit, and you pay for the rework later.

Ongoing support. Software isn't a one-time purchase like a piece of furniture. It needs updates, security patches, bug fixes, and changes as your business evolves. Some quotes include this. Others don't. Make sure you're comparing the same thing.

Ballpark ranges

These are rough ranges based on what we see across our projects and the wider industry. Your project will land somewhere depending on what you need.

Simple single-purpose tool: $10,000 to $30,000. A focused application that solves one specific problem. A custom reporting dashboard. A scheduling tool. An internal calculator that replaces a spreadsheet.

Mid-range business system: $30,000 to $100,000. Something with multiple screens, user roles, data storage, and maybe a couple of integrations with other tools you use. This is where most of our projects land.

Large platform or ERP replacement: $100,000 to $250,000+. A full system that replaces multiple tools and runs a significant part of your operations. Data migration, training, and ongoing support are all part of the scope.

Why two quotes look so different

When you get two wildly different quotes, it usually means one of these things:

Different scope. One company heard "build me a scheduling tool" and scoped a simple calendar. The other heard "build me a scheduling tool" and scoped a full resource management platform with notifications, reporting, and mobile access. Same words, different projects.

Different team structure. One company uses senior US-based engineers. The other subcontracts to an offshore team. The hourly rates are different, and so is the total cost, though not always in the direction you'd expect.

Different assumptions about what's included. Does the quote include testing? Training? Documentation? Ongoing support? Data migration? If one quote includes all of that and another doesn't, they're not comparable.

How to budget for it

If you're thinking about custom software but don't have a specific project in mind yet, here's a practical way to think about budgeting:

Start with the problem, not the budget. Figure out what's costing you money today. Manual work, errors, delays, missed opportunities. Put a rough dollar value on it. That's your ceiling for what the software should cost, because it needs to pay for itself.

Plan for phases. You don't have to build everything at once. A good software partner will help you break the project into phases, so you can start with the highest-value piece and add more over time. Phase one might be $20,000. Phase two might come six months later for another $15,000. This spreads the cost and lets you prove value as you go.

Budget for maintenance. A good rule of thumb is 15-20% of the build cost per year for ongoing support, updates, and small improvements. If you build a $50,000 system, expect to spend $7,500 to $10,000 a year keeping it healthy.

Red flags in a quote

No discovery phase. If someone quotes you a fixed price after one phone call, that price is a guess. Good quotes come after understanding your problem.

No mention of what happens after launch. Software needs care. If the quote is all about building and nothing about supporting, ask what happens on day 31.

Unusually low price with no explanation. If a quote is much lower than the others, ask why. It might mean a simpler scope (which is fine) or it might mean junior developers, offshore work, or missing pieces. Know what you're getting.