"How much does custom software cost?" is the most searched question in our category, and the most poorly answered. Most articles dodge the question with ranges so wide they are useless ("between 30,000 and 2 million euros"), or they refuse to give numbers at all and funnel the reader to a contact form. Neither is helpful if you are trying to budget an actual project.

This guide gives you real numbers: hourly rates by region in 2026, what actually drives total cost, and three end-to-end pricing scenarios for projects we have delivered or seen delivered. The goal is not to promise a fixed figure, because custom software genuinely does not work that way, but to give you enough detail to plan a realistic budget and to tell the difference between a reasonable quote and one that is either padded or unsustainable.

Hourly Rates in 2026: What the Market Actually Looks Like

Custom software development is priced either per hour (Time and Material) or per project (fixed price). For reasons we have covered elsewhere, we recommend T&M for almost every real project, so the hourly rate is the number to focus on.

Here is what we see in the market today for a senior developer with 5+ years of framework-specific experience, working on a serious enterprise project:

• Western Europe (UK, Germany, Netherlands, Nordic countries): 110 to 180 EUR per hour
• United States (major metros): 120 to 220 USD per hour
• EU nearshore (Poland, Czech Republic, Romania, Portugal): 50 to 90 EUR per hour
• Eastern nearshore (Ukraine, Moldova, Serbia): 35 to 70 EUR per hour
• Offshore (India, Philippines, Vietnam): 20 to 50 USD per hour

At codelabs.rocks, our rates fall in the EU nearshore band. We work primarily with clients in Germany, Benelux, the UK, and the Nordics precisely because the value equation of EU nearshore (same time zone, GDPR-native, EU contract law, quality close to Western Europe, cost roughly 50 percent lower) tends to beat both the offshore alternative and the local Western European option on total project outcome.

A note on the offshore band: the hourly rate is real, but the effective cost is often higher than it looks. Time-zone friction, communication overhead, and a higher rate of rework typically add 30 to 60 percent to the headline number. This is not an ideological claim; it is what we hear consistently from clients who have switched from offshore to nearshore after a failed first attempt.

What Actually Drives Total Project Cost

Hourly rate matters, but it is only one of five factors. A lower rate on an inflated hour count is not cheaper than a higher rate with a disciplined scope.

1. Team composition

A custom software team is not just developers. A healthy team for a 6-month project typically includes two or three developers, a project manager or Scrum Master, a designer (part-time), a QA engineer (part-time), and occasional DevOps support. Vendors who quote only developer hours are hiding the other roles, which means either you are paying extra for them separately, or nobody is actually doing that work and it will show up as quality problems later.

2. Project duration

The range we see for a serious custom software project is 3 to 18 months for an initial build. Anything shorter is usually a small integration or a proof of concept; anything longer typically means the scope was mis-sized or the team is under-resourced. Most genuine enterprise projects land in the 6 to 9 month window for a first production release, followed by ongoing development.

3. Discovery and architecture

Expect to spend 4 to 8 weeks on discovery, architecture design, and project setup before the first feature ships. At a senior rate, that is roughly 20,000 to 60,000 EUR of work that some vendors will happily skip to start billing sprints faster. Skipping it costs more later, every time.

4. Infrastructure and third-party costs

Cloud hosting (AWS, GCP, or Azure), monitoring, CI/CD, error tracking, and any paid third-party services (authentication providers, payment gateways, email services) are separate from development costs. For a mid-sized enterprise application, budget 1,000 to 5,000 EUR per month for infrastructure once in production. This scales with users, so check the growth curve before you commit.

5. Post-launch support

Plan on 15 to 25 percent of the build cost per year for ongoing maintenance, security patching, and small improvements. A 500,000 EUR build will typically cost 75,000 to 125,000 EUR per year to maintain properly. If a proposal assumes 5,000 EUR per year, the maintenance is not real.

Three Realistic Scenarios with End-to-End Numbers

Scenario A: Fleet management platform for a regional bus operator

Based on the GTV BUS platform we built. Real-time GPS tracking of 60 vehicles, driver compliance module, dispatcher dashboard, route planning, integration with existing ticketing. Angular frontend, Symfony backend, AWS infrastructure.

• Discovery and architecture: 6 weeks, ~45,000 EUR
• Build phase: 7 months, team of 3 developers + PM + part-time QA, ~320,000 EUR
• Infrastructure setup and first 3 months of hosting: ~8,000 EUR
• Total initial build: ~373,000 EUR
• Annual ongoing: ~70,000 EUR for small team on retainer plus ~25,000 EUR infrastructure

Scenario B: Telemedicine platform with GDPR-compliant video consultations

Based on similar scope to the WeTalk platform. Patient portal, practitioner portal, scheduling, video consultation, medical records, subscription billing. Strong compliance requirements.

• Discovery, compliance review, and architecture: 8 weeks, ~60,000 EUR
• Build phase: 9 months, team of 4 developers + PM + QA + part-time designer, ~520,000 EUR
• Compliance audits and penetration testing: ~20,000 EUR
• Infrastructure setup and first 3 months: ~12,000 EUR
• Total initial build: ~612,000 EUR
• Annual ongoing: ~110,000 EUR maintenance plus ~40,000 EUR infrastructure and compliance

Scenario C: Enterprise learning experience platform for Fortune 500 users

Based on the Social Talent engagement (used by Microsoft, Cisco, IBM, Siemens). Multi-tenant architecture, SSO, content management, assessment engine, analytics, deep customisation per client. Angular frontend, Symfony backend.

• Discovery and architecture: 10 weeks, ~75,000 EUR
• Build phase: 14 months, team of 5 developers + PM + QA + designer, ~920,000 EUR
• Enterprise security and SSO integration work: ~40,000 EUR
• Infrastructure at enterprise scale, first 3 months: ~18,000 EUR
• Total initial build: ~1,053,000 EUR
• Annual ongoing: ~180,000 EUR dedicated team plus ~70,000 EUR infrastructure

How to Read a Quote

When you receive a proposal, the sticker price matters less than the composition. Here is what to check:

Hours broken down by role and phase. A quote that gives you one total number and a single hourly rate is hiding complexity. You want to see hours for development, PM, QA, design, and DevOps, split across discovery, build, and stabilisation.

Assumptions listed explicitly. A good quote states what it assumes about scope, integrations, user load, and compliance. When assumptions are written down, you can challenge them; when they are implicit, they become the basis of later disputes.

Change management defined. Scope will evolve. A healthy quote explains how changes are estimated, approved, and invoiced. This is not a legal detail; it is a workflow that you will use dozens of times during the project.

Exit and handover terms. What happens if you need to move to another vendor? The answer should exist before you sign, not be negotiated from a position of weakness later.

What Is Genuinely Negotiable

A common misconception is that hourly rates are fixed by the market and nothing else is. In reality, hourly rates are the least flexible part of most contracts because they reflect the vendor's actual cost base. What is negotiable is the shape of the engagement:

• Team size and ramp-up curve (start with a small team, scale if the project proves out)
• Payment cadence (monthly is standard, but milestone-based options exist for some vendors)
• IP ownership terms (default should be 100 percent client ownership at payment; push back if not)
• Exclusivity on key team members (important for long engagements)
• SLA structure and response commitments for the support phase

The Short Answer

A serious custom software project from an EU nearshore vendor in 2026 typically costs somewhere between 200,000 EUR and 1.5 million EUR for the initial build, with annual ongoing costs at 15 to 25 percent of the build figure. Projects smaller than that are usually integrations or extensions of existing systems, not greenfield custom builds. Projects larger than that usually mean either multi-product platforms or scope that should be broken into phases.

If you are getting quotes significantly below this range, check carefully what is missing. If you are getting quotes significantly above it, check whether the premium is buying you something tangible (deeper sector expertise, enterprise references, post-launch commitment) or just larger overhead.

‍