How much does a custom app cost for a small business?

A focused internal tool that replaces one broken process commonly runs $5,000 to $25,000. A customer-facing product with accounts, payments and multiple user types commonly runs $15,000 to $60,000 or more. Then budget roughly 15 to 25% of the build cost per year for hosting, maintenance, security updates and small changes, because that part never stops.

Should I build a custom app or use off-the-shelf software?

Use off-the-shelf unless it genuinely cannot represent how your business works. Most requests for custom software are actually requests for the tools you already pay for to be configured properly and connected to each other. That is cheaper, faster, and someone else maintains it. Custom becomes right when the workaround costs more than the fix.

What are the signs I have outgrown my current tools?

Someone spends hours re-typing data between systems, a spreadsheet has become load-bearing, you pay for features you cannot use because your process does not fit the tool's assumptions, or you are turning down work because the admin does not scale. Any one of those is worth pricing. Two or more usually justifies building something.

Can I build a business app with AI tools or no-code?

For an internal tool with a handful of users, often yes, and it is a sensible way to prove the idea cheaply. Be careful before it touches customer data, payments or anything you would be liable for: the common failure is not that it does not work, it is that access control and data handling were never designed. Prove it with the cheap version, then have it hardened before it matters.

What is the cheapest first step?

Write down the process as it actually runs today, including the workarounds. Most of the time that document alone shows the problem is two systems not talking, which is an integration costing a fraction of an app. It also becomes the specification if you do end up building, so the hour is never wasted.

When Does a Small Business Need a Custom App?

You need custom software when off-the-shelf tools cannot represent how your business actually works, when you are paying people to be the integration between two systems, when a spreadsheet has become load-bearing, or when the workaround is now more expensive than the fix. If none of those are true, configure what you already own instead.

When does a small business actually need a custom app?

When the software you can buy cannot represent how your business really works, and the cost of working around that has quietly overtaken the cost of fixing it.

We build custom software, so we are one of the answers you might land on. That is also why the honest version is worth having: a good portion of the enquiries we get should not become a build, and saying so early is cheaper for everyone than discovering it in month three.

The four signs you have genuinely outgrown off-the-shelf

1. Someone’s job is to be the integration

If a person spends hours a week copying data from one system into another, you are paying a salary to do what software does for a fraction of the cost. This is the clearest signal on the list, and it is usually the easiest to fix, often with an integration rather than an app.

2. A spreadsheet has become load-bearing

Not a spreadsheet. The spreadsheet. Several people edit it, nobody is sure who owns it, it has rules that only one person understands, and the business would stumble if it were lost.

That spreadsheet is already your custom app. It is just a version with no permissions, no history, no validation and no backup.

3. You are paying for features you cannot use

You bought a tool, and using it properly would mean changing how you work in a way that does not suit your customers. So half of it sits unused while you keep a parallel process alongside it.

That is a mismatch between the tool’s assumptions and your business, and no amount of configuration removes it.

4. You are turning down work because the admin does not scale

The clearest commercial signal. If more customers means proportionally more manual handling, growth is capped by your own back office. That has a number attached: the jobs you did not take.

The five cases where custom is a mistake

You have not tried configuring what you already own. Most businesses use a fraction of the tools they pay for. Check that before you build.

The process is not written down. If three people do it three different ways, building software picks one of the three at random and makes it permanent.

You want it because a competitor has one. Their constraints are not yours, and you cannot see what theirs cost or whether it worked.

The real problem is one integration. Two systems not talking is a common and much cheaper problem than it feels like from the inside.

Nobody will own it afterward. Custom software is a permanent commitment. Without someone responsible for it, it decays into the thing everybody complains about.

What it actually costs

	Typical build	Ongoing
Integration between two existing tools	$500 to $5,000	Minimal
Focused internal tool, one broken process	$5,000 to $25,000	15 to 25% of build, per year
Customer-facing product, accounts and payments	$15,000 to $60,000+	15 to 25% of build, per year

The ongoing line is the one people leave out of the decision. Hosting, dependency updates, security patches, and the small changes that arrive the moment real people start using it. Budget for it from the start, because it does not stop.

The cheaper step to take first

Write down the process as it actually runs today. Not how it is supposed to run. Include the workarounds, the re-typing, the spreadsheet, the message someone always has to send.

Most of the time that page shows the problem is two systems not talking, or one tool configured badly. Both are far cheaper to fix than building something.

And if it does turn out you need to build, that page is your specification, so the hour is never wasted either way.

If you do build, build the smallest version

Not the whole vision. The smallest thing that removes the worst part of the current process, put in front of real users, then decided on.

The most common way small businesses waste money on software is building the complete imagined system in one go, then discovering that the part everyone actually needed was one screen, and three of the features nobody uses were where the budget went.

Ship the one screen. The rest of the plan will look different once it is in use, and that is the point.

What to do next

If the answer looks like “fix the process, not the software”, what to automate first in a small business ranks the candidates by hours back per dollar and covers the integration cases.

If you are weighing building against buying, build vs buy custom software goes deeper on that decision. And if a build looks likely, how to work with a dev studio covers what to have ready and what to put in writing before anyone starts.

If the signs above point to building, DappaSol’s automation lane covers exactly this range: integrations from $2,000, full internal tools and custom systems from $8,000, with the $500 Game Plan as the cheap first step that prices your specific case.

When Does a Small Business Actually Need a Custom App?