Skip to content
ITLC
Choosing software

Packaged software or a custom build: which question are you actually asking?

Most software decisions stall because two different questions get argued as one. Separating them usually settles it.

Two questions usually get merged into one conversation. The first is about fit: does software that already exists do what this operation needs? The second is about ownership: does this business need something shaped around how it works specifically? They feel like the same question because both end in a purchase, but they have different answers and different consequences.

What actually separates the two

A packaged product exists before you decide to use it. You can be shown it working. Its behaviour was settled by whoever built it, and adopting it means accepting most of those decisions and adapting a few of your own processes around them. The compensation is that the thinking is already done.

Custom software does not exist until it is built. There is nothing to be shown except other work and a description of intent. Every behaviour is a decision someone has to make, which is precisely the point when the way you operate is the thing that makes the business work — and precisely the cost when it is not.

The practical differences that tend to matter during a decision
Packaged productCustom build
Exists before you buyYes — you can be shown itNo — it is described, then built
Who decided how it behavesThe people who built itYou, during the engagement
What you adaptSome of your processesThe software
Where the effort goesAdoption and setupDefinition, then delivery
What you are buyingA product to activateWork to be performed

The questions worth asking first

Before comparing anything, it is worth being honest about four things. They are unglamorous, and they decide the answer more often than any feature list does.

  • Is the way we do this genuinely unusual, or is it just ours? Familiarity is not the same as distinctiveness. A process can feel specific simply because it is the only one you have seen.
  • If we adopted someone else's way of doing this, what would actually break? If the answer is a reporting habit, that is different from a regulatory obligation or the thing customers pay you for.
  • Do we know what we want clearly enough to have it built? Custom work converts unclear thinking into expensive rework. A packaged product forces the clarity on you at no cost.
  • Who maintains this in three years? Both paths need an answer. Only one of them makes it your problem by default.

It is often not one or the other

The two are frequently treated as a fork when they are closer to layers. A business can run packaged software for the parts of its operation that resemble everyone else's, and commission work only for the part that genuinely does not. The failure mode at both extremes is the same: deciding once, for the whole business, on reasons that only applied to one part of it.

That is also why the question is worth separating from the vendor conversation. Which shape you need is a question about your operation. Who builds it is a question you can only answer well once the first one is settled.

How this maps to ITLC

ITLC publishes these as two separate things rather than one blended offering, because they are answers to different questions. The products are software you activate and use. The services are engineering work performed to a brief. Neither page tries to talk you into the other, and the site does not publish pricing for either — what a given piece of work costs depends on what it turns out to be.

Where to go from here

If you would rather talk it through than read more, a demo is a conversation about how your operation runs today.

Related reading