Custom software cost: price ranges and examples

What drives the price

Cost depends less on screens and more on business logic, data quality, permissions, integrations, and how much needs to happen after launch.

• Number of workflows.
• Integration complexity.
• Data migration needs.
• Roles and permissions.
• Reporting and support expectations.

Indicative price ranges by type of system

A focused internal tool can stay close to EUR 5,000 to EUR 15,000 when it supports one workflow and uses limited integrations. A CRM, customer portal, booking platform, or operational dashboard usually starts around EUR 15,000 to EUR 40,000. Connected platforms with several roles, data migration, payments, planning, or complex integrations often fall between EUR 40,000 and EUR 100,000 or more.

How to keep the first investment under control

Price is easier to control when the first release has one owner, one measurable outcome, and a fixed acceptance test. Reuse reliable services for authentication, payments, email, and hosting where ownership is not a differentiator. Build the workflow and data model that make the company distinctive.

• Define must-have workflows before discussing screens.
• Separate migration and integration risks from the core build.
• Agree what support and maintenance include after launch.
• Compare three-year ownership cost with the SaaS stack being replaced.

Price the operational change, not a collection of screens

Custom software cost is driven by business rules, exceptions, integrations and operational risk. A portal that reads one source is fundamentally different from a platform coordinating stock, payments and scheduling. Start by documenting the work that should disappear, the decisions the product supports and the response when information is missing. Only then can a project estimate be useful. A detailed feature list without process context often creates false certainty while hiding the work that will decide delivery time and quality.

• Map users, transaction volumes, busy periods and exception paths.
• Identify systems that remain authoritative for core records.
• Flag features affecting revenue, privacy, safety or continuity.
• Separate launch requirements from improvements and future options.

Include the full cost of ownership

Development is only one line in the investment. Discovery tests assumptions before they become code. Integrations need mapping, authentication and failure handling. Migration exposes duplicates and incomplete records. Security, acceptance and training determine whether the product can be used responsibly. After launch, hosting, monitoring, support and change continue. Show these categories separately so a low build quote is not later overtaken by data clean-up, missing controls or an unsupported production service.

• Discovery, service design and technical validation.
• User experience, engineering and automated testing.
• Integrations, migration and data reconciliation.
• Security, privacy, documentation and user acceptance.
• Cloud, monitoring, support and planned improvement.
• Time required from internal owners and subject experts.

Estimate with scenarios rather than one precise-looking number

Early estimates should expose uncertainty. Create a core scenario for one workflow, an expected scenario with essential integrations and an extended scenario with additional roles, reporting or AI. Record assumptions and exclusions for each. Leadership can then choose an investment level that matches expected value and risk. A short discovery should narrow the range and may make a fixed-price delivery phase sensible, without pretending that unresolved data or third-party APIs are predictable.

• Core: one user group, one workflow and limited migration.
• Expected: several roles, key integrations and operational reporting.
• Extended: advanced permissions, mobile journeys, AI or higher availability.
• Hold contingency against named risks, not unlimited scope.

Compare custom software and SaaS over three years

Do not compare a build budget with a single monthly subscription. Include licences by role, add-ons, implementation, integration tools, support and the internal labour spent on workarounds. Consider control as well: can the company export its data, change the process and switch suppliers? SaaS remains the right answer for many standard functions. Ownership becomes attractive when a distinctive workflow, rapidly increasing licence bill or permanent duplicate work creates a recurring business cost.

• Calculate current licences, modules and middleware at realistic growth.
• Measure rekeying, checking, reconciliation and recovery work.
• Value shorter lead time, fewer errors and improved conversion conservatively.
• Include exit cost and the residual value of owned assets.

Contract around evidence and decision points

A healthy project connects payment to verifiable outcomes. Discovery delivers a process model, risk register and validated scope. The first build phase delivers a working core journey with tests. Integration, migration and controlled rollout follow. Specify acceptance, ownership of code and accounts, documentation and support. This keeps budget and risk visible, while giving the company a genuine choice to continue, redirect or stop after each useful phase.

• Request estimates by phase, discipline and recurring cost.
• State which inputs and decisions the client must provide.
• Use change control for new scope, never to excuse defects.
• Commission an independent review for sensitive or critical systems.