In most companies, the decision between custom software and off-the-shelf software is made too early and based on emotion. A sales manager has a standard solution in mind because a competitor uses it. An IT manager wants custom software because the last SAP project took three years. Both are poor starting points. If you want to make a well-reasoned decision, you need criteria that can be verified—not gut feelings.
Off-the-shelf software is suitable when a process follows industry standards and does not provide a competitive advantage—such as accounting or time tracking. Custom software is worthwhile when the process itself is the advantage. The key factors are twelve verifiable criteria, above all the degree of standardization, differentiation, and the costs over five years rather than over the first year.
Custom Software vs. Off-the-Shelf Software: The Numbers Behind It
In Germany, the cost range for custom software in 2026 is between 5,000 and 500,000 euros (kulimo.com, 04/2026). The range is so wide because an internal automation tool has little in common with an enterprise-wide platform. Off-the-shelf software, on the other hand, seems predictable, but it rarely is. With 50 users and a monthly license fee of 60 euros, the total cost over five years comes to 180,000 euros (Groenewold IT, 2025)—pure license costs, excluding setup and customization.
Anyone who adapts a standard solution to their own processes pays extra. According to Gartner figures, ERP customization costs 30 to 40 percent of annual license fees (Gartner via Groenewold IT, 2025)—year after year, not just a one-time expense. And the total costs are almost always underestimated. On average, companies overlook 50 to 70 percent of their actual total cost of ownership (Gartner via researchly.at, 2024) because integration, training, and maintenance are omitted from the initial calculation.
It's interesting how rarely companies opt for a simple either/or choice.
of spending on enterprise software goes into combinations of buying, building, and connecting. A pure either/or is the exception.
Gartner via TECHSY, May 2026
It therefore usually makes more sense to ask the more specific question of which model is suitable for which process. We describe what this mix looks like in practice in the article on the costs of custom software development and in the overview of the Buy-Build-Blend Strategy.
The 12 Criteria for a Sound Decision
Instead of relying on gut feelings, we recommend a list of twelve questions. Each one can be answered with facts; none of them is based solely on a hunch.
- Degree of process standardization. Does the process work the same way as at almost every other company in the industry, or is it structurally different?
- Competitive differentiation. Does the process provide a measurable advantage over the competition?
- Interfaces. How many legacy systems need to be integrated, and are there open APIs available for this purpose?
- Data sovereignty. Where is the data stored, and who has contractual access to it in the event of a dispute?
- 5-Year Costs. How does the cost trend change over five years, not just in the first year?
- Need for adjustment. How often does the process change each year, and who implements the change?
- Compliance. What regulatory obligations apply, and does a standard solution even cover them?
- Scaling. Is the number of users or the data volume expected to grow significantly, and what will that cost?
- Exit scenario. What happens when you switch providers, both technically and contractually?
- Team expertise. Is there in-house expertise to operate a customized solution over the long term?
- Time to Market. How soon does the solution need to be up and running?
- Operating model. Who operates the solution during normal operations—in-house or externally?
Criterion seven, compliance, has carried additional weight since the end of 2025. The NIS2 Directive has been in effect in Germany since December 6, 2025, and, according to the BSI, affects approximately 30,000 companies (BSI via inno-software, 04/2026). Those affected must also consider the verifiability of security measures in every software decision. Off-the-shelf software often includes this by default, while custom software must actively incorporate it.
| Criterion | Off-the-shelf software | Custom Software |
|---|---|---|
| Initial Investment | low, license valid from day one | high, development before benefit |
| Ongoing Costs | License per user per month | Maintenance and Further Development |
| Adaptation to Your Own Processes | limited; customization costs annually | Complete, with effort as needed |
| Time to Market | Weeks to months | two to twelve months, depending on the scope |
| Code Rights | from the provider; you will receive a license | contractually with the client |
| Competitive Differentiation | None; the competition uses the same one | possible when the process itself is the benefit |
| Dependence on the provider | high, with no exit clause in the contract | High, with no documentation or rights to the code |
| Updates and Security | provided by the provider | Plan and budget on your own |
When Off-the-Shelf Software Is the Better Choice
For accounting, time tracking, or standard CRM functions, custom development is almost never worth it. These processes are the same across industries, the market offers mature solutions, and no one wins a customer with a custom-built payroll system. Criterion one scores high here, while criterion two scores low—a high degree of standardization with little differentiation. This is exactly what off-the-shelf software is designed for.
When Custom Software Pays Off
The situation is different when the process itself is the competitive advantage. This includes a logistics provider with its own route optimization system, a manufacturer with specific batch size control, or a retailer whose returns process differs from industry standards. In these cases, off-the-shelf software forces the company to adapt its own process to the tool, rather than the other way around. This costs time and flexibility—and, in the end, often results in the loss of the very advantage the company was hoping to build upon.
The case of the Swiss retail group Migros illustrates just how expensive this can get. The SAP update, which took several years, cost significantly more than planned because switching to another system was effectively no longer an option (NZZ, 12/2024). To find out how to avoid this, see the article on Exit Strategies for Software Contracts.
For companies that want to develop a sustainable solution tailored to their specific processes, we provide information on our page about Custom Software Development, how we go about it.
Review the twelve criteria for your projectA 30-minute conversation is enough to figure out the right direction. If off-the-shelf software is a good fit, we'll let you know.
Frequently Asked Questions
How much does custom software cost compared to off-the-shelf software?
Custom software requires a higher initial investment, but there are no ongoing license fees. Off-the-shelf software is cheaper to start with, but the costs of licenses and customization often add up to higher total costs over several years. Which model is more cost-effective depends on the number of users, the contract term, and the need for customization—not on a one-size-fits-all rule.
How long does it take to develop custom software?
Simple tools are ready for use in two to four months; medium-sized projects take four to eight months; and complex systems take six to twelve months or more (Smartbetrieb, 03/2026). The duration depends heavily on how clearly the requirements are defined at the outset.
Who owns the rights to the code for custom software?
In the case of custom software, the rights to use and exploit the code are contractually assigned to the client, provided this is specified in the development contract. Unlike with off-the-shelf software, where the provider retains the rights and merely grants a license to use the software, this results in genuine ownership of the product.
The Next Step
torck develops custom software for industry and retail, with its own development teams in Maxhütte-Haidhof, Vienna, and Rabat. If a standard solution is the better choice for your process, we’ll be just as upfront about that. In any case, the German company torck GmbH remains the contractual partner. In the Initial Consultation we go through the twelve criteria together for your project.
This article refers to laws and regulations to put technical decisions in context. It is not legal advice. Whether and how a rule applies to your company is a question for your legal department or a law firm.
German 
English 
French