Custom web application or off-the-shelf software?

The question is often framed as a matter of principle, but it is really a calculation with several line items. This text names the items that count in both directions — and the cases in which the answer is clear-cut.

Who it is forManagement, project leads
LevelDecision
Reading timeabout 7 minutes
Last updated16 October 2026

What you will learn

Which five questions really carry the decision
Which costs of off-the-shelf software are often overlooked
Which costs of custom software are often overlooked
When the answer is settled without further review

Five questions that carry the decision

Above all, the decision depends on the relationship between your process and what a ready-made product provides; budget, and the options for operation and maintenance, set the framework.

Is your process typical for your industry, or your own? The further it departs from the norm, the more expensive it becomes to bend it into a product. How many systems are involved? Every connection is work in both variants. With off-the-shelf software, the effort depends on which interfaces and connectors the product brings with it; with custom development, they have to be built in full. How long should the solution last? A stopgap for two years is calculated differently from a tool for ten. How important is the process to your business? A peripheral process can tolerate compromises, a core process cannot. Who will maintain the solution later? Custom software needs someone responsible — internally or at a service provider.

What off-the-shelf software really costs

The price of a product is the visible part. On top of that come, regularly:

Setup and configuration within the limits the product provides.
Training, because the product's terms are not yours.
Adapting your processes to the product — the item that is least often quantified.
Running fees that rise with the number of users or the volume of data.
The question of what happens if you want to leave the product: can you get at your data?

None of these points speaks against off-the-shelf software. For a typical process, a proven product is almost always the better choice — it has been used by many, and it shows.

What custom software really costs

Here, too, the development effort is only the beginning. On top of that come:

Operation: servers, updates, backups, monitoring.
Maintenance: PHP versions and libraries keep evolving, even if your requirements stay the same.
Further development: every change to the process becomes a task that someone has to carry out.
Dependence on knowledge: whoever knows the application must be reachable — and their knowledge must be documented.

In certain cases the advantage weighs heavily: the software follows your process, not the other way round. There is no feature you pay for and do not need, and no limit behind which "the system does not provide for that" stands.

The third way: standard plus extension

In practice the most common case is a mixture. A proven system carries the standard part, and a custom extension takes over precisely the part that is yours. This is how shop extensions, additional screens in a portal or interfaces that connect two products come about.

This variant has a price that you need to know: the extension has to follow the updates of the main system. That is plannable, but recurring work.

An example from practice

The same task, two decisions

Two businesses want to record orders. The first works with typical quotation and invoicing steps; for it, a proven industry solution is the right choice, even if it comes with ten fields that it never fills.

The second has a process that depends on a review by two different departments, and has to hand the results over to an existing planning system. Here, any standard solution fails not at recording, but at the approval path and at the handover — and those are exactly the two things that are not negotiable.

When the answer is settled

Two cases need no lengthy review. If there is a widespread, well-maintained product for your process and your process does not differ fundamentally — take the product. If your process is your competitive advantage and is not provided for in any product, there is much to be said for a custom solution — but first check whether a standard system with a custom extension can cover the differing part.

Everything in between is decided by the five questions above. If you are unsure, a short stocktake is worth more than a longer discussion: what steps does your process have, which systems are involved, which rules apply?

Common misconceptions

For a typical process, usually yes. For a process of your own, the ongoing adaptation costs of a product can even out or reverse the difference over the years. What matters is the comparison over the planned period of use, not the purchase price.

The installation, yes. The introduction — data, permissions, training, adapting the processes — is the longer part in both variants.

Not for the basic decision. For that, the systems involved, the steps of your process and the rules that must apply are enough.

About the author

Fabian Lücker is managing partner of PHP-Schmiede KG in Rheine and has worked in software development since 2007. He is responsible for development and concept design and writes here about decisions that come up in real projects.

Questions about the article? Write to us

Putting the decision into context together

Describe your process and the systems involved. We will tell you where we recommend a standard product and where we do not.

Discuss your project