Home / Custom software

Buy, configure or build

Custom software or a package: how to decide, before anyone quotes

The choice is rarely between a package and a custom build. It is between three options, and the middle one is where most budgets die. This page sets out the four questions that settle it and what each route actually costs once you count the years after go-live.

By Tom Joseph · Last updated: 27 August 2026

Free consultation Pricing

In short

Buy the parts of your business that look like everyone else's, and build only the part that is the reason customers choose you. Accounting, payroll and CRM are solved problems: a package will be less expensive and better than anything built for you. The exception is the process that is genuinely yours, the one no vendor models properly, where a package forces you to work in a way that costs you your advantage. Build that, buy the rest, and connect them.

Three routes, one choice

How to choose before anyone quotes

Package, configuration or custom: the least expensive route depends on your process, not your budget.

The routes
Three roads, one trap
Package, configuration and custom. The trap sits between them: rebuilding a package until you inherit custom maintenance without the ownership.
The questions
Four questions that decide
How unusual is the process, who does the work in year two, what is the exit, and where does your edge sit.
Year two
Cost it past the quote
Licences continue and custom needs maintenance. The comparison is only honest once year two counts.
Configuration
The middle road, honestly
Configuration is faster than custom and more flexible than a package, until the day you want to leave the platform.

The three options

Package, configuration, custom: and the trap between them

Most comparisons offer two choices. There are three, and the middle one is the expensive surprise.

A standard package. Least expensive to start, least expensive to run, and someone else maintains it. You adapt to the software. For anything commoditised, this is simply the right answer.
A configured package. The same product bent toward you with settings, scripts and add-ons. This is the trap: it is sold as low-risk, but heavy configuration is custom software you cannot upgrade, built in a language you cannot hire for, owned by a partner you cannot leave.
Custom software. Most expensive to start, and it fits exactly. It is worth it when the fit is the point, and a poor investment when it is not.

The decision

Four questions that settle it

Run these before anyone quotes. Three "no" answers means buy a package and stop reading.

Is this process a reason customers choose us? If yes, custom is defensible. If it is administration, it is not.
Do the packages force a change we would refuse? Not a change we dislike. One we would actually refuse. That is a different and much shorter list.
Do we know the rules well enough to write them down? Custom software makes your exceptions explicit. If they only live in one person's head, that discovery is the first phase of the project, and it is worth doing regardless.
Can we own it for five years? Custom software is a commitment to keep it running. If nobody will own it, buy a package where that is someone else's job.

Cost over time

What each route costs once you count year two

Package licensing looks low-cost in year one and compounds; custom looks expensive in year one and then mostly stops. The crossover depends on seat count, and with enough users a package can quietly cost more than the build it replaced.

The number nobody quotes is the cost of the workaround. A package that fits 85% leaves 15% living in spreadsheets, re-keying and a person who knows the trick. That cost is real, recurring, and invisible in the business case because it never appears on an invoice.

Our own prices are published, which makes at least one side of this comparison easy to run: audit €2,500, proof of concept €20,000, production from €50,000.

Buyer guides

Compare further

Custom software development Choosing a software company API integration Process automation AI with Exact, AFAS and e-Boekhouden A Zedrox alternative

FAQ

Frequently asked questions

Is custom software always more expensive?

To start, yes, almost always. Over five years it depends on seat count and how much workaround the package leaves behind. Compare total cost including the manual work a package forces, not licence against build.

Can we start with a package and build later?

Often the best route. Buy the package, run the business, and let the friction show you which part is genuinely yours. Then build only that and connect it. It is also the least expensive way to be wrong.

What about low-code?

Good for internal tools with a handful of users and simple rules. It becomes expensive at exactly the point custom would have been the answer: many users, real integrations, or logic that needs testing. Judge it as configuration, with the same upgrade and exit questions.

How do we avoid being locked in?

Own the source, own the data, and insist the stack is one you could hire for. If a build can only be maintained by the firm that wrote it, that is not a technical property of the software, it is a commercial choice someone made.

Still deciding between a package and a build?

The €2,500 audit runs the four questions against your actual processes and gives you a written answer, including the case for buying a package and not hiring us.

Book a conversation