How much does custom software cost? What really drives the price

Custom software costs vary widely because the work varies widely. Instead of a meaningless average, here are the things that actually drive the price, and how to get a fixed price you can trust.

The honest answer to "how much does custom software cost?" is that it depends on a handful of things you can identify in advance: what it has to do, who uses it, what it connects to, the data it starts with, and whether it includes AI. Any single number quoted without knowing those is a guess. That is why we don't publish a price list: we give a fixed price once we understand what you need.

What we can do is show you what moves the price, so you can scope sensibly and compare quotes fairly.

What drives the cost of software development

1. What it has to do. An internal tool that replaces one spreadsheet is a different size of job from a product your customers pay to use. The number of screens and the rules behind them matter more than the category.

2. Who uses it. Software used only by your team is simpler than software your customers use, which in turn is simpler than something open to the public. Each step up adds security, support and polish.

3. Kinds of user and permissions. One kind of user is simple. Staff, managers and customers who each see different things add work to every screen.

4. Features. Login, an admin panel, payments, file uploads, notifications, reports, search and a mobile app each add work. Payments and mobile apps add the most.

5. Connections to other tools. Every system it must talk to (accounting, CRM, email, your existing database) adds work, and older systems without good connections add surprises.

6. Existing data. Starting fresh is easy. Moving and cleaning data from several sources is often underestimated.

7. AI features. AI that reads documents, answers questions or takes actions needs testing on your real examples, and has running costs per use.

8. How it is looked after. Hosting, monitoring, backups and fixes after launch are a real part of the cost, whoever does them.

Why quotes for the same idea vary so much

• Different assumptions about scope. One quote includes things another leaves out. Ask each what is not included.
• Different quality bars. Tests, security, backups and monitoring cost time. A quote without them is cheaper now and expensive later.
• Fixed price vs time and materials. A fixed price puts the risk of overrun on the builder. Hourly billing puts it on you.
• Guessing vs scoping. A price given before anyone understands your process is a guess, and it tends to grow.

How to keep the cost down without cutting corners

1. Build one thing first. Decide the single outcome the first version must deliver, and write down what it will not do.
2. Reuse what you already pay for. Connect existing tools instead of rebuilding them.
3. Clean up your data early. It shortens the build.
4. Make decisions quickly. Slow decisions cost more than slow code.
5. Plan for running costs. Budget for hosting, fixes and small improvements after launch.

What about ongoing costs?

After launch, software needs hosting, security updates, backups, monitoring and occasional fixes. AI features also need re-testing when models change, and they cost something per use. Some businesses handle this themselves; others choose a monthly care plan. Either way, include it in the decision.

How we price

We don't price anything until we understand it. It starts with a free consultation about how your work happens today. For a clear, focused project we then send a fixed price for the agreed scope. For complex or unclear projects we suggest a short paid Scoping Sprint first: a clickable prototype, a build plan and a fixed price, with the Sprint's fee credited to the build. Changes are priced before we do them, and you own the code.

To get a feel for the size of your project first, try our Build Scope Planner. It suggests a first version and the risks to plan for, with no price on purpose. When you're ready, book a free consultation.

A scoping checklist to take to any builder

Answer these before you ask for a quote, and every builder will be pricing the same thing:

1. The goal: the one outcome the first version must deliver, in one sentence.
2. The users: who uses it, and what each kind of user can see and do.
3. The screens: a rough list, even as sketches on paper.
4. The rules: calculations, approvals and limits the software must enforce.
5. The connections: every tool it must read from or write to.
6. The data: what exists today, where it lives, and how clean it is.
7. AI: if AI is involved, what exactly it does, and what happens when it's wrong.
8. Not in this version: what you are deliberately leaving out.
9. After launch: who hosts it, fixes it and improves it.

Comparing quotes fairly

• What is not included? Exclusions are where costs reappear later.
• Is the price fixed for the agreed scope? It tells you who carries the risk of overrun.
• How is the work tested? Untested software is cheaper now and dearer later.
• Who owns the code? You should, once it is paid for.
• What happens after launch? Hosting, fixes and updates are part of the real cost.
• How are changes priced? Changes are normal; surprise invoices shouldn't be.

Frequently asked questions

Why won't you give a rough price on your website? Because the same request can be a small job or a large one, depending on details we don't know yet. A number before a conversation would be a guess.

Is a fixed price really fixed? For the agreed scope, yes. Anything outside it is priced before we do it, so there are no surprises.

Is it cheaper to use off-the-shelf software? Often, if it fits how you work. Custom software is worth it when you are bending your process around tools, or paying for several tools that still don't do the job.