How much does custom business software cost? What actually moves the number

Search for custom software development cost and you will find ranges so wide they are useless: a few thousand dollars at one end, half a million at the other. Both ends are real. The range is wide because "custom software" covers everything from one internal form to a platform with thousands of users.

A better question is what moves the number for your project. Five things do most of the work. Once you know them, you can read any quote, ours included, and see where the money goes.

We don't publish a price list, and we have no hard minimum. After a first call we send a written scope with a price for the first release, usually within a week. This post explains how that price gets built.

The five things that set custom software development cost

Each one ends with a question to ask yourself before you ask anyone for a quote.

1. Users, roles and permissions

Software for one person is simpler than software for twenty. Every new kind of user adds screens, rules and tests.

A dispatcher, a field worker and an accountant each need different views of the same records. Each also needs limits on what they can change. The work is not the login page. It is deciding who may see, edit, approve and export each kind of record, then proving those rules hold.

Ask yourself: how many kinds of people will use this, and what must each one never be able to do?

2. Integrations with tools you already pay for

Most businesses already run on five or six tools. New software that has to read from or write to them costs more than software that stands alone.

A one-way export to a spreadsheet is small. But a two-way sync with accounting software is not. The hard parts are what happens when the other tool is down, when a record changes in both places, and when the same request arrives twice. A good integration handles all three without anyone noticing.

Ask yourself: which tools must this talk to, and which one is the source of truth for each record?

3. Data migration

If years of records live in spreadsheets, PDFs or an old system, moving them is its own project. Old data is rarely clean. So expect duplicates, missing fields, dates in three formats and a column whose meaning only one person remembers.

Migration cost depends less on the number of rows than on how messy they are. It also depends on whether the old and new systems must run side by side for a while.

Ask yourself: what has to come across on day one, and what can stay archived?

4. Compliance and record-keeping rules

Payroll, health, payments and anything touching personal data carry rules. Those rules add work: audit trails, records that can never be changed once final, retention periods, access logs.

None of this is optional when it applies. It is also easy to underestimate, because nobody sees it in a demo.

Ask yourself: which laws or contracts govern this data, and who will check?

5. Who looks after it afterwards

Software keeps costing money after launch. Hosting, security updates, new browser and phone versions, and small changes as the business moves all need someone.

Some teams take this on themselves. However, most small businesses prefer a monthly arrangement with the people who built it. Either way, it belongs in the budget from the start.

Ask yourself: who will fix it at 7am on a Monday?

A worked example (hypothetical)

Here is how those five factors shape custom software development cost for an invented business. The numbers of people and tools are made up to show the reasoning. They are not a real client.

A landscaping company with 25 staff schedules crews in a shared spreadsheet. Office staff copy finished jobs into their accounting software by hand every Friday.

• Users and roles. Three kinds: the owner, two office staff, and crew leads on phones. Crew leads see only today's jobs and can mark them done. That is a modest permission model.
• Integrations. One: finished jobs become invoices in the accounting tool. It is two-way only for payment status. This is the single biggest line in the scope.
• Data migration. Two years of jobs in one spreadsheet. The customer list is fairly clean; job history is not. The scope moves customers and open jobs, and archives the rest as a read-only export.
• Compliance. Light. No payroll in the first release, and no card numbers stored.
• Upkeep. A monthly care plan covering hosting, updates and small changes.

The first release would include crew scheduling, the phone view for crew leads and the invoice sync. Route optimization and customer texts would wait for a second release. That split is the most useful thing a scope does. It says what is in, what is out, and why.

What a discovery phase buys you

On a larger project, the first paid step is often discovery: a short, fixed piece of work before the build is priced. It produces a map of how the work really happens, the data model, the integrations, and a list of decisions the business has to make.

Discovery is worth paying for when the problem is fuzzy or several departments disagree. But it is not needed for a small, well-understood tool. For that, a good conversation and a written scope are enough.

How to compare quotes

Quotes for the same project can differ by a factor of three or more. Before you compare totals, compare these:

1. What is in the first release. One quote may include reporting and another may leave it for later.
2. Who owns the code and accounts. You should own the repository, the hosting account and the domain from day one.
3. How changes are priced. Find out what happens when you ask for something new halfway through.
4. What happens after launch. Check whether maintenance is included, quoted separately or left out.
5. What the team will not build. A scope that lists what it leaves out is more honest than one that promises everything.

If you are still deciding whether to build at all, start with what you already pay for. Often the right answer is an off-the-shelf tool, connected properly, and a good developer will say so. The web applications and internal tools pages show how we run a build week to week.

Get a scoped range for your project

Send a few lines about the problem: who uses the software, which tools it touches and where the data lives today. We reply within one business day. After a call, you get a written scope with a price for the first release, and nothing is billed before you approve it. Start here.

Cover photo by Jakub Żerdzicki on Unsplash.