What does custom software cost? Pricing models, cost drivers and examples for mid-sized companies

Custom software has no list price. That is not an evasion by software agencies — it is because no project is like any other. What you pay depends on how complex your requirements are, what integrations you need, whether you are building a web app or a mobile application, and where the development team is based. AI tools in software development are beginning to shift costs and timelines for some project types — though gradually and not uniformly across all areas. This guide gives you the tools to define a realistic budget before your first conversation.

What determines the price of custom software

Five factors drive the bulk of costs — and all of them can at least be roughly assessed in advance.

• Scope and complexity: The more user roles, workflows and edge cases there are, the more development time is needed. A simple form tool and a full ERP system differ by a factor of 10 to 20.
• Interfaces (integrations): Every connection to an existing system — ERP, CRM, payment provider, external APIs — costs time for analysis, development and testing. Poorly documented legacy systems often double this effort.
• Technology stack: Cloud-native web apps (e.g. Next.js, React, Node.js) are faster to develop than classic on-premises solutions; mobile apps (iOS and Android native or React Native) typically add a further 30 to 50 per cent of effort.
• Team location: DACH developers cost 80–150 €/hour, nearshore (Poland, Romania) 35–70 €/h, offshore (India, Vietnam) 15–35 €/h — with corresponding differences in language ability, time-zone proximity and quality assurance.
• Operations and maintenance: Security updates, hosting, monitoring and ongoing development add up to 15–25 per cent of the initial development cost per year — a figure often omitted from initial budget frames.
• AI-assisted development: Tools such as GitHub Copilot and AI code generators are reducing development time for standard components and repetitive tasks — by an estimated 15 to 30 per cent in clearly defined project areas. The effect is real but uneven: complex custom integrations and legacy connections benefit far less than greenfield front-end work.

Pricing models: fixed price, time and material, or phased approach?

How you structure the contract has almost as much influence on the budget as the scope itself. The three common models distribute risk very differently — choosing the right one is part of sound custom software development.

• Fixed price: Scope, budget and timeline are contractually fixed. Advantage: maximum planning certainty. Disadvantage: every requirements change costs extra, and agencies build in a risk buffer. Best for clearly defined projects up to around 40,000 €.
• Time and material (T&M): Invoiced based on actual effort. Advantage: maximum flexibility, fast response to new insights. Disadvantage: the final budget is open. Best for iterative, agile projects where requirements are still evolving.
• Phased model (Discovery → MVP → expansion): Each phase has its own fixed price or T&M frame. The Discovery phase (2–4 weeks, 5,000–15,000 €) sharpens the scope for all subsequent phases. Recommended for medium to large projects — it reduces risk on both sides.

Our approach to custom software projects

Realistic price ranges and example calculations

The following budget ranges apply to DACH agency rates (80–120 €/hour) and include conception, development and quality assurance — excluding ongoing operating costs.

• Small (15,000–50,000 €): Internal process tools, simple portals, prototypes. Example: holiday-request and approval workflow with ERP connection, 3 user roles — roughly 300 to 400 development hours over 3–4 months.
• Medium (50,000–200,000 €): Customer portals, industry-specific software, B2B platforms with multiple modules. Example: customer portal with CRM integration, document management and user self-service, 700 to 1,500 hours, 6–12 months.
• Large (200,000–600,000 €+): Business-critical systems, multi-language platforms, mobile app plus web plus back end in combination. Example: asset-management software with IoT connection, reporting dashboard and native mobile app, 2,500+ hours, 12–18 months.

AI tooling is beginning to affect these numbers — particularly at the lower end of each category. For projects with clearly scoped requirements and a high share of standard components, agencies using AI-assisted development can sometimes deliver comparable results in less time. The effect does not change the fundamental cost structure, but it is worth asking prospective partners how they use AI in their workflow and whether that is reflected in their pricing.

Custom software is not a cost centre — it is an investment that pays for itself once it automates the right processes or closes a market gap. The question is not "What does this cost?" but "What is the current situation costing me each month?"

Hidden costs — what throws budgets off track

Software projects exceed their budgets more often than most other investment decisions. The most common causes are not technical surprises but organisational gaps.

• Incomplete requirements: Anyone who brings "everything should be flexible" as a requirement pays for every decision made during the development phase. Invest 2–4 weeks in a Discovery phase before the main project.
• Missing internal capacity: A software project needs a decision-maker on the client side. Without a clear contact person, coordination time doubles — and with it, the agency hours.
• No test phase budgeted: QA costs around 20–30 per cent of the development budget. Cutting it saves money short-term and costs three times as much to fix in production.
• Maintenance underestimated: Most proposals end at go-live. Hosting, security updates, minor adjustments and support cost 1,000–4,000 €/month depending on system size.
• Change management overlooked: New software changes processes. Training, internal communication and adoption work cost time and money — and are rarely included in the project budget.

Checklist: what to clarify before your first proposal meeting

The better prepared you are for the initial meeting, the more accurate the proposal — and the lower the risk of unpleasant surprises later. These five points are the foundation of any productive custom software project.

• Problem definition: What specific process or problem should the software solve — not what features it should have.
• Integration inventory: Which existing systems (ERP, CRM, external APIs) must be connected? Are documentation and access credentials available?
• User groups: Who will use the software daily — internal staff, external customers, or both? How many concurrent users are expected?
• Budget and timeline: Name a ballpark — even a rough range helps propose the right model and team composition.
• Decision structure: Who has budget approval, who makes functional decisions, who is the main contact on your side?

If you are still in the orientation phase and unsure whether custom software is the right choice or whether an off-the-shelf solution will serve you better, a strategic IT consulting session is a useful first step before committing to development.

Discuss your custom software project with NoviCogi