Custom or off-the-shelf software: how do you choose?

What both terms mean

Off-the-shelf software is a package made for many businesses at once: an accounting program, a CRM, a webshop platform or an ERP package. You take out a licence or subscription, configure it with the settings the package offers, and the vendor takes care of updates.

Custom software is built for one business, around the way that business works. It does what you need and nothing more, and you decide what changes. In between lies a large grey area: a package with a custom module, or custom software that leans on standard components. In practice the question is rarely entirely one or the other.

When off-the-shelf software is the better choice

A package is strong where your process resembles that of many other businesses. Accounting, payroll, e-mail and calendars are largely the same everywhere, and legal rules change regularly. You do not want to reinvent the wheel there, and a vendor that keeps up with it for thousands of customers does it better than a system of your own.

• The process is generic and differs little from that of other businesses in your sector.
• You want to start quickly and can live with the way of working the package prescribes.
• A lot of legislation applies, which the vendor keeps up to date for you.
• It is not an area in which you set yourself apart from competitors.

When custom software pays off

Custom software becomes interesting where your business works differently from what the package assumes, and where that difference matters. That is often exactly the part of the work you are good at: the way you quote, plan, produce or deliver.

• You adapt your way of working to the package, while that way of working is your strength.
• Excel lists, Word forms and loose notes run next to the package to fill the gaps.
• Data is retyped by hand between systems that do not talk to each other.
• You pay for a package of which you use only a small part, and still miss what you really need.
• Every change you want depends on a vendor's roadmap and priorities.

The cost is not only in the purchase

A package often looks cheaper because the price is known up front. But the total cost also lies in what happens around it: the time people lose on workarounds, retyping between systems, licences that grow with the number of users, and the configuration and customisation an implementation partner charges for.

Custom software asks for a larger investment up front, and maintenance after that. In return the software fits exactly, you pay no per-user licences, and you can change what you need when you need it. A fair comparison puts both side by side over several years, including the hours your people spend working with it every day.

Questions to ask yourself

These questions help sharpen the choice before you request quotes:

• Which part of your process is the same as at other businesses, and which part is really yours?
• Where is work done by hand, retyped or tracked in a separate sheet today?
• Which systems does the new software have to work with?
• Who has to use it: office, shop floor, customers, partners?
• What happens when your business grows: does the package still fit, and what does it cost then?
• How important is it that you decide when and how the software changes?

Often the answer is: both

The best solution usually combines the two. Accounting stays in a standard package, and the part that sets your business apart, such as planning, quote calculation or the customer portal, is custom-built and connected to what is already there. That way you only pay for custom work where it really adds something, and the rest stays standard.

How I approach it

I do not start with the question of what should be built, but with how your business works today. Where does it get stuck, where is work done twice, and what does that cost? Only then do I look at whether a package solves it, whether custom software makes sense, or a combination of both.

If an existing package is the best choice, you will hear that. If custom software makes sense, I build it around your own process and connect it to the systems you already use. You see the plan before any code is written, and you work with me from start to finish.

Frequently asked questions

Is custom software always more expensive than a package?

Up front, usually yes. Over several years it depends on what the package costs in licences, configuration and workarounds, and how much time your people lose on work the package does not support. A fair comparison counts all of those costs, not just the purchase.

Can custom software work with the software I already have?

Yes, and that is often the point. Custom software usually does not replace everything, but fills in where the package falls short, and exchanges data with your accounting, ERP or webshop through integrations.

How do I know which choice suits my business?

By mapping your process first, before looking at solutions. In a free 30-minute introductory call I look with you at where things get stuck today, and you hear honestly whether a package, custom software or a combination makes the most sense.