How Much Does Custom Software Cost? From Small Tool to Full System (2026)

Custom software costs anywhere from about €1,500 for a small tool that automates one task to €45,000 and well beyond for a system with customer logins, payments and several integrations. Custom software cost comes down to hours times rate, and the hours depend mostly on how many workflows, user roles and integrations the system has to handle.

I'm a freelance developer based in Denmark and I build this kind of software, so I have a stake in the answer. That's why there's also a section on when you shouldn't build anything at all.

The short answer

The table shows my rough estimate of hours for four typical sizes, priced at €75-120 an hour. That rate band comes from the rates freelancers in Western Europe have shared with Lancebase, which put full-stack developers in that range. All figures exclude VAT.

Here's a quick rule. If you can describe the job in one sentence and only your own staff will use it, you're probably in the top two rows. If customers need to log in, or the system has to talk to your accounting software, CRM and inventory, you're in the bottom two.

For the wider picture, from websites to SaaS products, I've put everything in my complete guide to software development cost.

Same hours, different rates: why location matters

The hours in the table are the stable part. The rate is what moves, and it moves a lot across Europe.

Danish freelance rates sit near the top. Lønradar puts senior freelance IT consultants in Denmark at DKK 800-1,200 an hour, which is roughly €105-160 since the Danish krone is pegged to the euro. With a Danish senior, the same internal tool from the table lands closer to €6,300-24,000.

Agencies in Eastern Europe and Asia typically charge less per hour. That can work well for clearly specified projects. The catch is that the hours aren't always the same: a vague brief, several handoffs and little overlap in working hours tend to add rework. I compare the trade-offs in more detail in what a developer really costs: employee, freelancer, agency or offshore.

There's also a data angle. If the tool stores personal data about people in the EU, GDPR applies to it. Keeping both the developer and the servers inside the EU makes that part simpler to reason about, though it doesn't replace proper legal advice.

Why agencies rarely price the small end

Search for custom or bespoke software pricing and most results come from software houses. They start high. Keyhole Software, for example, lists $40,000-120,000 for the simplest projects in its 2026 cost guide. Those are dollar figures from a US software house for projects that run 2-4 months, and even the bottom of that range is about twice the top of my internal-tool row.

That isn't greed. A software house carries fixed costs on every project: sales, proposals, a project manager, kickoff meetings, QA and handover. Those costs barely change whether the job is 40 hours or 400. So most agencies have a minimum project size, and anything below it is either turned down or padded out.

The small end usually looks like this:

• a script that pulls data from one system every night and pushes it into another
• an internal page where staff log what currently lives in a shared spreadsheet
• a weekly report someone spends Friday afternoon assembling by hand
• a simple admin panel on top of a database you already have

Jobs like these suit a freelancer or a small studio. There's no project manager in between, and the person writing the code is the one you talk to. On the other hand, you don't get a team that can scale up next week, and holidays or illness hit the project directly.

Four examples, from small tool to full platform

These are typical jobs, not client case studies. The hours are rough estimates and assume the work has been scoped before development starts.

1. A weekly report from two systems (about 20-40 hours)

A company exports numbers from Shopify and its accounting software every week, merges them in Excel and emails the result to management. A small program can pull the data through each system's API (the interface other software uses to read and write data), calculate the key figures and send the report every Monday morning.

There's no interface to design and no users to manage. Most of the time goes into understanding the data and handling the cases where an API returns something odd or is down. Expect 1-3 weeks of calendar time, at the low end of the price range.

2. The spreadsheet that needs to become an internal tool (about 60-150 hours)

Orders, tasks or equipment are tracked in a shared spreadsheet, and it's starting to break: two people edit at once, formulas get overwritten, and nobody knows which version is current. If that sounds familiar, I've written about the signs your business has outgrown Excel.

An internal tool for this usually means logins, two or three user roles, a few screens for creating and editing records, search and filters, an Excel export and a log of who changed what. Because only your own staff use it, the interface can stay plain and be built with ready-made admin building blocks, such as Filament for Laravel. That saves a lot of hours compared to designing every screen from scratch.

Plan for 3-8 weeks. If data has to be moved over from a messy spreadsheet, add roughly 10-20 hours for cleanup and import.

3. An order portal with customer logins and an accounting integration (about 200-500 hours)

Now customers log in, see their orders and place new ones, and every order flows into Xero, QuickBooks or a similar system as an invoice. That moves the project up a class for three reasons. The interface has to be good enough for customers to use without training. Permissions must be airtight so customers only ever see their own data. And the accounting integration has to cope with errors, edits and credit notes.

Systems of this size are usually called customer portals or web apps, and I go deeper into the price levels in my guide to web app development cost. Calendar time is typically 2-5 months. At this size I always recommend a short, paid discovery phase before anyone commits to a fixed price.

4. A platform with several user types and payments (600+ hours)

Picture a platform where customers, suppliers and your own staff each have their own access, payments run through Stripe, notifications go out, and several external systems have to stay in sync. At this point the coding is only part of the bill. Scoping, testing, security and operations take just as much effort.

Projects like this can easily pass €100,000 and should be built in phases, with the first phase live and in use before the rest is built. Platforms have their own cost drivers, so they get their own guide on marketplace and platform development cost.

What pushes the price up or down

The technology itself rarely decides the price. What decides it is how many things the system has to keep track of, and how many exceptions there are.

Integrations are often underestimated. Reading data from a system is rarely hard. Keeping two systems in sync when an invoice is edited, a customer is deleted or an API changes takes real time. Each integration is effectively a small project of its own.

Edge cases are the other big cost. The main path through a workflow is often quick to build, but the last 20% of special cases ("unless the customer is a public body, then ...") can take as long as everything else.

What it costs after launch

The build is not the last invoice. Software has to run somewhere, and it has to be kept up to date.

Hosting a small internal tool on a European cloud provider typically costs tens of euros a month. Larger systems with several servers, backups and monitoring cost more. Then there's maintenance: framework and package updates, security patches and changes when an external service updates its API.

As a rough guide, budget 10-20% of the build cost per year for hosting, updates and small fixes. A €15,000 tool would then cost around €1,500-3,000 a year to keep running. I break down those line items in my guide to web app maintenance cost.

Also plan for new features. Once people use a system they like, requests for more come quickly. That's a good sign, but it belongs in the budget.

When you shouldn't build custom software

I make a living building software, but there are several situations where I'd advise against it:

• Off-the-shelf software covers most of the need. If a SaaS subscription at a few tens of euros per user per month solves 80% of the problem, adapting your process to the tool is almost always cheaper than building your own.
• The process isn't settled yet. If your workflow changes every month, keep it in a spreadsheet or a no-code tool until it stabilizes. Otherwise you'll pay to rebuild it several times.
• The job is tiny. An Excel macro or an automation in Zapier or Make may be enough, and you don't need a developer billing €100 an hour for that.
• You need a whole team right away. If five developers need to start next week, or you need 24/7 on-call support, a freelancer like me is the wrong fit. Look for an agency or software house instead.

On the other hand, custom software is often the cheapest option over time when a workflow is stable, eats many hours every week and doesn't fit any standard product.

How to get a number you can budget against

An accurate quote needs an accurate description. Here's how to get there:

1. Describe the problem, not the solution. What takes time today, who does it and how often?
2. Choose the one workflow that has to work in the first version.
3. Gather the material: the spreadsheet, screenshots of the systems involved and a list of who will use the tool.
4. Ask for a rough estimate first. If the job is bigger than a small tool, start with a fixed-price discovery phase before you get a fixed quote for the build.
5. Compare quotes on hours and scope, not just the total. A cheap quote with vague scope rarely stays cheap.

I start larger projects with a fixed-price discovery phase, and you own the code from day one. If you're looking at a customer portal, an internal tool or a system that should replace spreadsheets, you can see how I work on my page about custom web app and platform development.

Frequently asked questions

Do I own the code once I've paid for it?+

You should, but it has to be in the contract. Some vendors keep the rights and only grant you a license, which means you can't simply hand the code to another developer later. With me, you own the code from day one. Whoever you hire, ask directly about ownership and access to the code before you sign anything.

Will AI coding tools make custom software cheaper?+

Somewhat, but less than the headlines suggest. AI tools speed up writing routine code, so a small tool can cost less than it did a few years ago. The expensive parts are unchanged: understanding the workflow, making integrations work, testing edge cases and keeping the system running. Be wary of quotes that are dramatically cheaper because of AI, and ask who tests and maintains the code.

What happens if my freelance developer stops working on it?+

That's the real risk of hiring one person, but you can keep it small. Make sure you have access to the code, that it's built on a widely used framework such as Laravel, and that there's short documentation of setup and hosting. Another developer can then take over without starting from scratch. Agree on this at the start, not when the problem arises.

Can a small tool grow into a bigger system later?+

Yes, if it's built for it. An internal tool made with a mainstream framework and a proper database can be extended with more roles, integrations and eventually customer access. If the first version is built in a no-code tool or as a spreadsheet full of macros, growing requirements usually mean a rebuild. Starting there isn't necessarily wrong, but put the rebuild in the budget.

Do I pay VAT if I hire a developer in another EU country?+

Usually not on the developer's invoice. When a VAT-registered business buys services from a supplier in another EU country, the general rule is the reverse charge: the supplier invoices without VAT, and you account for VAT at your own country's rate in your VAT return. Both of you need valid VAT numbers, and there are exceptions, so confirm the setup with your accountant before the first invoice.