Skip to content

Make or buy

Standard or custom software: how to decide

By Dominik Natter · Last updated on 1 October 2026 · 2 min read

In short

Choose standard software if it covers 80% of your process and the remainder is not a competitive advantage. Build your own if several systems have to work together, if your process sets you apart from competitors, or if customising the standard product would cost more than a solution of your own. In practice the best answer is often a combination: standard software for accounting and ERP, custom-built for what makes your business distinctive.

The case for standard software

Standard software is available immediately, proven in practice and developed further by the vendor. Statutory changes such as new VAT rates or payment formats are included in the subscription. For accounting, payroll, simple order processing and standard shops, there is no reason to build something of your own.

Where standard software reaches its limits

  • Several systems need to exchange data and none of them takes responsibility.
  • The process departs from the norm and is managed in Excel lists alongside the system.
  • Customising the standard product is possible, but expensive and at risk with every update.
  • Licence costs per user grow faster than the benefit.

Six questions for your decision

  • Does this process set us apart from competitors, or is it the same for everyone?
  • How many Excel lists do we keep alongside the software today?
  • Over five years, what does customising the standard product cost compared with a solution of our own?
  • Which systems have to be connected, and are there ready-made connectors for them?
  • Who will look after the solution in five years' time?
  • What happens if the vendor discontinues the product or raises its prices?

The middle way: standard at the core, custom at the edges

Most SMEs do best with a standard ERP as the system of record and a lean application of their own for the part the ERP cannot handle. That application reads and writes through interfaces, while the ERP stays unmodified and can still be updated.

That way you pay only for what really sets you apart, and you avoid depending on expensive customisation of the standard product.

Decision guide

Accounting, payroll, VATStandardstatutory changes maintained by the vendor
Simple shop with list pricesStandardShopify or WooCommerce
Connection between two systemsCheck for a connector, otherwise customdepends on volume and logic
Core process with special featuresCustomconnected to the ERP
Portal for customers or partnersUsually customunless the ERP module is enough

Frequently asked questions

When do you advise against custom software?

Whenever a standard product covers 80% of the case and the remainder is not a competitive advantage. For accounting, simple appointment booking or a small shop, there are good off-the-shelf solutions. We will tell you so in the intro call. Custom software pays off where several systems have to work together or your process departs from the norm.

Who holds the rights to the code and the data?

The data is yours. The source code is kept in a repository you have access to, and the usage rights to it pass to you once the work is paid in full. We rely on widely used technologies such as Next.js, C# and PostgreSQL, so that another team can take the software forward if needed.

How dependent do we become on Natter Solutions?

As little as possible, and we make sure of that from day one. Every project is documented and handed over so that it can be operated and developed without us: the repository, architecture description, operations manual and access credentials are in your hands.

Matching services:Custom softwareIntegrations

Let us talk about your case.

20 minutes are enough to find out whether a custom solution is worth it for you.