Software Development Cost (2026): A European Price Guide

Software development cost comes down to hours times rate: with a senior freelance developer in Northern Europe, most projects land between about €4,000 for a small integration and €150,000 or more for a SaaS product or marketplace with payments, user roles and integrations, excluding VAT. Where your developer is based sets the hourly rate, while the size of the project and how clearly it's defined up front decide almost everything else.

I'm a freelance developer based in Denmark, so read this with that in mind. The numbers are rough market estimates, not a quote, and I've tried to be just as clear about when you shouldn't build custom software at all.

The short answer: cost ranges by project type

These are ballpark figures for work done by a senior developer, assuming €100-150 per hour excluding VAT, rounded. The hours are what really move. Each project type has its own detailed cost guide.

The ranges are wide on purpose. An MVP (minimum viable product: the smallest version you can put in front of real users) with login and one core workflow is a very different project from one with payments, notifications and three types of users. Use the table to check whether your idea and your budget are in the same order of magnitude, not as a price to plan around.

Two project types come up so often that they have their own guides: customer portal development cost and what a booking system costs to build. Both usually fall inside the web app range, but each has its own traps.

Many of the cost guides you'll find online quote USD figures from US agencies or offshore vendors. Neither maps neatly onto a European project, so treat those numbers as a different market rather than a benchmark.

What actually drives software development cost

Every quote you get is built the same way: estimated hours multiplied by a rate. Even a fixed price is calculated like that. The difference is who carries the risk if the hours run over.

The hourly rate depends on where you hire

The same project can cost twice as much depending on where your developer lives, and that's mostly about labor costs, not skill. According to Eurostat's figures for 2025, average hourly labor costs across the whole economy ranged from €12.0 in Bulgaria to €56.8 in Luxembourg, with Denmark second-highest at €51.7 and the EU average at €34.9. Developer rates tend to follow the same pattern.

In Denmark, LønRadar's 2026 guide to freelance IT rates puts juniors at 400-600 DKK per hour, mid-level developers at 600-900 DKK, seniors at 800-1,200 DKK and specialists at 1,000-1,600 DKK, all excluding VAT. At roughly 7.5 DKK to the euro, a Danish senior lands around €105-160 an hour. Agencies usually sit at the top of their local range or above it, because the rate also covers project management, sales and office space.

So why pay Northern European rates? Usually for direct contact with the person writing the code, overlap with your working day, and a supplier working under the same EU rules as you. If none of that matters for your project, a cheaper region may be the right call. I go deeper into this in my guides to freelance developer rates in Denmark and what cheap and expensive developers really cost.

Hours matter more than the rate

Two developers with the same rate can send quotes where one is double the other, simply because they picture different solutions. A senior at €145 an hour who needs 200 hours costs €29,000. A less experienced developer at €80 an hour who needs 450 hours for the same job costs €36,000, and may leave code the next person has to clean up. How estimates are put together, and how to read one, is covered in my guide to software development estimates.

What pushes the hours up

• More user types. Every role, such as customer, staff member and admin, needs its own screens, permissions and tests.
• Payments and subscriptions. Cancellations, failed payments, invoices and VAT take far longer to build than the checkout button.
• Integrations. Every connection to another system, whether Stripe, HubSpot, Xero or a national eID like BankID or MitID, comes with its own documentation, test accounts and failure cases.
• Bespoke design. Designing from scratch costs more than starting from a proven component library, in both design and development hours.
• Data migration. Moving data out of an old system almost always uncovers gaps and duplicates that someone has to decide on.
• Security and GDPR requirements. Audit logs, access control and documentation are necessary work, and they belong in the budget.
• More platforms. Web, iOS and Android at once are three deliverables, even when a lot of code is shared.
• Deadline pressure. A hard date usually means more people on the project or less time for testing.

The biggest cost driver isn't on the list: unclear requirements. Every decision made halfway through development means something gets rebuilt, and those hours were rarely in the first estimate.

What brings them down

• A small first version. Build the one workflow that proves the idea works, and leave the rest until you have real users.
• Existing services for solved problems. Payments, email delivery, login and search can usually be handled by services you plug in rather than code written from scratch.
• Standard components instead of bespoke design, at least for version one.
• One decision-maker on your side who can answer the same day.
• A clear brief. The fewer guesses your developer has to make, the less buffer goes into the quote.

A worked example: an internal tool for field service jobs

The table above shows ranges. Here's a made-up example of how one concrete project might break down, so you can see where the hours go. It isn't a real client project, but the split is typical.

Picture a service company that wants to replace spreadsheets and phone calls with an internal tool. The office creates and schedules jobs, technicians see them on their phones and mark them as done, and customers get an email update. Completed jobs are sent to the accounting system (Xero, for example) so they can be invoiced.

Notice that only just over a quarter of the hours go into what feels like the actual product: jobs and scheduling. The rest is login, design, integration and testing, all of which has to be in place before staff can rely on it every day.

The example also shows where you can save. Push the accounting integration and customer emails to version two, export invoice data as a file for now, and you cut 55 hours, or about €6,900. Making trade-offs like that visible is what a discovery phase is for.

Pricing models: hourly, fixed price, discovery and retainers

How you pay matters as much for your budget as the amount itself. There are four common models, and many projects combine them.

Hourly or day rate

You pay for the time spent. It's flexible and suits work where the requirements change as you go, but the risk of hours running over sits with you. Ask for a monthly cap and a short weekly status update.

Fixed price

You know the price in advance, but only for what's written down. Your developer adds a buffer for uncertainty, and changes along the way are priced separately. Fixed price works best when the scope is clear. I compare the two in detail in fixed price vs hourly rate.

Paid discovery phase

A short, paid phase before development where requirements get written down, the solution is sketched and you get an estimate you can act on. It's how I start larger projects myself: a discovery phase at a fixed price, followed by a fixed price for the build. It costs a fraction of the total budget, and you keep the material whoever ends up building it. See what a discovery phase costs for typical prices and contents.

Retainer

After launch, most software needs both maintenance and new features. A retainer, a fixed number of hours per month, is a common way to handle that. I explain how to set one up in the guide to developer retainer agreements.

Freelancer, agency, in-house or offshore

Who builds your software affects the rate, how much of your own time the project takes, and what happens after launch.

• Freelancer: lower overheads than an agency, and you work directly with the person writing the code. The trade-off is that you depend on one person, so insist that the code lives in your own repository and that documentation is written as you go.
• Agency: a full team with design, project management and development under one roof. It costs more per hour, but it can be the right choice when several disciplines need to work in parallel.
• In-house developer: salary is only part of it. As one data point, PROSA, the Danish IT union, reports an average of 63,812 DKK (about €8,550) per month in the category that includes software developers, including bonus and employer pension. That's over €100,000 a year before equipment, licenses, recruitment and management time. It pays off when there's development work all year, for years.
• Offshore team: hourly rates can be much lower in parts of Asia or Latin America. The total bill doesn't always shrink to match, because coordination, language, time zones and quality control take more of your own time. It works best when you have technical knowledge in-house, or someone who can manage the team for you.

Time zones are easy to overlook. A developer in Central European Time shares most of the working day with the UK and the rest of Europe, and a few hours with the US East Coast. For the full side-by-side numbers, see my developer cost comparison.

The costs that start after launch

Launch isn't the last line on the bill. Software that's in use costs money every year, and it's the item most budgets forget.

• Hosting and services: servers, database, backups, email delivery and error monitoring. For a typical web app that runs from tens to a few hundred euros a month, while a platform with many users can cost more.
• Updates: frameworks and packages need regular updates for security. Laravel, for example, ships a new major version every year, and each version gets security fixes for two years, according to Laravel's own support policy. Skip the updates and the eventual jump gets bigger and more expensive. Here's what a Laravel upgrade costs.
• New development: once real users arrive, you find out what's missing. The first version is rarely the last.
• Fees and licenses: payment providers charge per transaction, and many services get more expensive as your user count grows.

My rule of thumb is to set aside 15-20% of the build cost per year for hosting, maintenance and small improvements, and more if the product needs to move fast. You can work out a concrete figure with the web app maintenance cost guide, and check the line items that rarely appear in a quote in hidden costs of software development.

How to get a quote you can trust

You won't get a reliable figure by asking five developers for "a price for an app". You get it by giving them something solid to price. Here's how:

1. Describe the problem before the solution. Who will use the software, what do they need to do, and how do they do it today? That gives your developer room to suggest something simpler than you had in mind.
2. Split features into "needed now" and "can wait". It's the most effective tool you have for controlling the price.
3. Set a budget range. A number you can live with lets the solution be shaped around it, rather than the other way round. My software project budget template can help.
4. Start with a discovery phase for anything above a couple of hundred hours, so the estimate rests on something concrete.
5. Compare quotes on the same basis: same scope, same requirements for testing and documentation, and the same arrangement for maintenance. Here's how to compare software development quotes.
6. Ask what isn't included. Hosting, testing, documentation, support after launch and code ownership are the usual gaps.

If you already have a prototype built with an AI tool like Lovable, Bolt or Cursor, the starting point is different. The question becomes what it takes to make it safe for real users, and I cover that in the cost to fix a vibe-coded app. And if your company is based in Denmark, check the funding options for software development in Denmark before you settle the budget.

When you shouldn't build custom software

Sometimes the most honest answer to "what will it cost?" is that you shouldn't build anything. I'd advise against custom development in these situations:

• An off-the-shelf tool covers most of what you need. If an existing booking tool, e-commerce platform or CRM handles around 80% of your needs, adapting your process is almost always cheaper than building your own.
• You need a standard marketing website on a budget of a few thousand euros. A template on Webflow, Squarespace or WordPress gets you further for that money than code written from scratch.
• You don't know yet whether anyone will pay. Test demand with a landing page, a manual process or a no-code tool before you pay for development.
• You need a full team for years. Hiring or an agency is a better fit than a single freelancer.

Custom software pays off when it supports something specific to how your business works, when standard tools force daily workarounds, or when license fees over a few years would cost more than owning the software outright.

Next steps

You're in a good position if you can answer three questions: which row in the table your project resembles, what has to be in version one, and what budget you can live with. Read the cost guide for your project type, then write a short description of who will use the software and which systems it needs to connect to.

How I price my own work, with a paid fixed-price discovery phase before larger builds and a fixed price for the build after it, is on my pricing page. You'll talk to me directly, not a sales rep, and you'll hear back within one business day.

Frequently asked questions

How long does it take to build custom software?+

It depends on the hours and on how many people work on it. A developer realistically manages 25-30 focused development hours a week once meetings, testing and coordination are taken out, so a 300-hour project typically takes 10-12 weeks with one person. Add time for discovery, feedback and testing. More developers can speed things up, but not proportionally, because coordination takes time too.

Will AI make software development cheaper in 2026?+

Yes, for parts of the work. AI tools speed up boilerplate code, tests and first drafts. But requirements, architecture, security, integrations and code review still take time, and that's where a large share of the hours go. Expect a modest saving, not a 50% discount. A prototype built with an AI tool is a great starting point for a conversation, but it's rarely ready for real users as it is.

Who owns the code when I hire a freelancer?+

Your contract decides. Under the EU Software Directive, the employer holds the economic rights to code an employee writes as part of their job unless the contract says otherwise, but that rule doesn't automatically cover freelancers or agencies. Make sure the contract assigns the rights to you and that the code lives in your own repository. My clients own their code from day one. This isn't legal advice, so have a lawyer review the contract if a lot is at stake.

Do I have to pay the full amount upfront?+

No, and you rarely should. With a fixed price, it's common to pay in installments: a share at kickoff and the rest spread across milestones or on delivery. Hourly work is usually invoiced as you go, often monthly. Be wary of a supplier who wants the full amount before any work starts, and always agree on what happens to payments if the project stops halfway.

Should I agree on prices in EUR or another currency?+

Agree on one currency in the contract before work starts. If your developer invoices in a currency other than yours, you carry the exchange rate risk, which adds up on a project that runs for months. The Danish krone is pegged to the euro within a narrow band, so with a Danish developer the difference is small either way. Just ask whether they can invoice in EUR.