← All articlesArchitecture and quality

Custom software: what to build and what to take off the shelf

Custom software does not mean writing everything from scratch. The best projects I know combine your own code where the company stands out with proven off-the-shelf components everywhere else. Here is how I draw that line.

When an off-the-shelf tool is not enough

Off-the-shelf software is great as long as your processes look like those of most companies. Trouble starts when:

  • the team adapts the way it works to the tool instead of the tool to the way it works,
  • data has to be moved by hand between several systems because none of them does everything,
  • the system has to serve thousands of locations, devices or users, and the licence costs of a ready-made product grow faster than the company,
  • what sets you apart in the market requires features nobody else offers.

In these situations a system built for your needs pays for itself faster than it seems at the quoting stage.

What I do not write from scratch

Some parts of every system look similar regardless of the industry. There I propose proven solutions that we run as separate services.

The best example is login and user management. Writing it from scratch rarely makes sense when mature tools such as Keycloak or Better Auth exist. A ready-made solution has been tested in thousands of deployments, supports signing in with Google or Microsoft and two-factor authentication, and costs a fraction of your own code to maintain. The exception is projects with specific requirements that no tool meets.

I take the same approach to payments, sending emails and text messages, search and message queues.

How I draw the line

For each part of the system I ask three questions:

  1. Does it set us apart? If so, we build it. This is where the value of custom software lies.
  2. Is there a mature solution that meets the requirements? If so, we evaluate it before writing our own.
  3. What will it cost to maintain over several years? Not just the start-up cost counts, but also updates, security and licences.

The result: the budget goes into what gives the company an edge, not into recreating things that already exist.

What you get

A system that fits your processes, with code and documentation that belong to you. The off-the-shelf components in it are replaceable: if a better tool appears in a few years, it can be swapped in without rebuilding the whole.

Let’s talk about your project

Tell us briefly what you want to build or fix.