Custom software or off-the-shelf? A decision framework for SMBs
Five scored criteria, a five-year total cost table including the hidden items, and a third option: an off-the-shelf core with a custom layer on top.
Companies with 10 to 200 employees sooner or later run into the limits of spreadsheets or a cheap subscription. Then comes a decision that will shape how people work for years: buy a ready-made system, or have one built. This article gives you a framework for comparing the two options honestly – including the costs that never make it into the quotes.
The question is not “which is cheaper” but “what sets you apart”
A poor decision costs more than the figure on the quote. It costs years in which people adapt to the system instead of the system serving them.
So don’t start with prices. Ask one question first: is this process your competitive edge, or does every competitor do it the same way?
- Accounting, payroll, email, time and attendance – standard processes you run the same way as every other company. Here off-the-shelf wins.
- The way you schedule jobs, price quotes or look after customers – if that is what wins you business, it is a candidate for custom software.
Write down your five most important processes and mark each one “standard” or “differentiator”. Often only one or two end up as a differentiator.
What “off-the-shelf” and “custom” mean in 2026
Off-the-shelf today usually means SaaS – software as a service with a monthly fee per user. It also covers classic licences and low-code platforms where you “click together” your workflows. The vendor decides what the system can do, when it changes and at what price.
Custom software is an application built around your processes. You own the code and the data; it runs on your servers or in the cloud. You decide on changes and you pay for developers’ work, not for licences.
The middle ground is an off-the-shelf core plus integrations and custom extensions – more on that below.
Easytrade, for example, develops both ready-made products for clinics and restaurants and custom software – a ready-made product makes sense where the process is similar across an industry, custom software where a company does things differently.
Five criteria that decide
Score each criterion from 1 to 5. The higher the number, the stronger the case for custom software.
1. How distinctive the process is
Is the way you do it the reason customers buy from you? If so, bending to fit a boxed solution costs you your advantage. If everyone in the industry runs the process the same way, score 1.
2. How much of your needs the off-the-shelf product covers
Rule of thumb: if a ready-made solution covers roughly 80% of your needs and you can adjust the process for the rest, take it. If it lacks things the process cannot work without, even the cheapest subscription won’t help.
How to find out: not from the vendor’s demo, but from a trial run. Two weeks, real data, two or three people from operations. A demo shows what the system can do. A trial shows what it lacks.
3. Integrations and data
How many systems need to talk to each other? Does the off-the-shelf product have an API and a data export? In what format do you get your data when you leave? For personal data you have the GDPR on your side – Article 20 gives the data subject the right to receive their data “in a structured, commonly used and machine-readable format”. It does not apply to your business data about orders and jobs; there, the contract decides.
4. Pace of change
Does your process change every quarter – growth, new markets, regulation? With off-the-shelf you wait for the vendor’s roadmap. With custom software you commission the change, but someone still has to build it – and pay for it. Ask: who will make the change, and in how many days?
5. Vendor dependence and risk
With SaaS: price list changes, product discontinuation, acquisition. With custom software: dependence on a single developer, quality of documentation, access to the source code.
| Criterion | 1 point | 5 points |
|---|---|---|
| Distinctiveness of the process | same as everyone else’s | this is how we win business |
| Coverage of needs | 80% or more | the core of the process is missing |
| Integrations and data | 1 system, export available | 3+ systems, no connectors |
| Pace of change | once every few years | every quarter |
| Vendor risk | large vendor, clear exit terms | one person, no documentation |
The result is a guide, not a verdict. A total of up to 12 points argues for off-the-shelf, above 18 for custom software. In between is the space for a third option.
Total cost over five years – what the quotes leave out
A SaaS quote shows a price per user per month. A development quote shows a price for delivery. Neither shows what you will pay over five years.
| Cost item | Off-the-shelf | Custom software |
|---|---|---|
| Licences / subscription | grows with users and modules | none, or only for components |
| Implementation and setup | days to weeks | months |
| Integrations | ready-made connectors, otherwise expensive | part of the brief |
| Fitting people to the system | training, workarounds, Excel “on the side” | the system fits the people |
| Changes and development | you wait for the vendor | you pay for the work, you set the priorities |
| Operations, security, updates | included | your responsibility and budget |
| Support | depends on the plan | maintenance contract |
| Exit costs | data migration, rewriting integrations | code and data stay with you |
Two items are underestimated most often. The first is “Excel on the side” – work done outside the system because the system cannot do it. Nobody sees it in the accounts, yet it costs hours every week. The second is subscription growth. In a forecast from November 2025, Gartner expects spending on public cloud services in Europe to grow 24% in 2026. Zylo’s 2026 index reports that organisations leave an average of 36% of their SaaS licences unused – the data comes mostly from large organisations, but the principle holds at twenty users too: you pay for user accounts, not for work done.
Exit costs are also addressed by the EU Data Act (Regulation (EU) 2023/2854). It has applied since 12 September 2025 and requires cloud service providers to remove obstacles to switching to another provider. Until 12 January 2027 they may charge only reduced switching charges; after that, none at all. Read your contract with this legislation to hand.
When we would not recommend custom software
- It is a standard process and there is a good off-the-shelf product for it – accounting, payroll, invoicing, email.
- Fewer than about ten people will use the system and the workflow is simple.
- You have no process owner – someone who will write the brief, test and sign off.
- You need it “next month”. Custom development is measured in months.
- The budget covers delivery only, not the operations, security and maintenance that follow.
If you ticked two or more, buy off-the-shelf and put your energy into the process.
When custom software pays off
- The process is your differentiator and a boxed solution would force you to change a way of working that works.
- You need to connect three or more systems and ready-made connectors don’t exist.
- You are planning AI agents and automation on top of your own data. A system you own has an API and keeps the data under your control – the foundation for agents.
- Regulation or a customer requires the data to run on your own infrastructure.
- The user count is growing to the point where a subscription for every account stops making sense.
The third option: off-the-shelf core, custom layer on top
Picture a field service company with 60 employees. Accounting and payroll run on a ready-made Slovak system. The CRM is off-the-shelf too – keeping track of contacts and quotes is no different from the rest of the industry. Only the scheduling of service jobs and the technicians’ mobile app are custom-built, because fast, accurate service is why customers choose the company. Everything is connected through APIs: a job is created in the CRM, scheduled in the app, and the invoice goes out from the accounting system.
Why is this often the cheapest option overall? You pay for development only on the part that sets you apart. The standard parts you buy at subscription prices. And when you one day replace the CRM, you replace one connector, not the whole system. There is more on connecting systems in our section on process automation.
Questions for the vendor (either kind)
- Who owns the code and who owns the data?
- In what format and on what terms do we get a data export?
- What does a change cost – a small tweak, a new module, a new integration?
- How is the system updated and who is responsible for updates?
- Where is the data physically hosted and who has access to it?
- What happens when the contract ends – notice periods, transition period, fees?
- Do you have references with a similar process, not just a similar industry?
- What does support look like – who handles it, in what hours and at what cost?
Get the answers in writing.
Key takeaway: The choice between off-the-shelf and custom software does not hinge on the licence price but on whether the process is your competitive edge. Buy standard processes ready-made; have the differentiating ones built. Compare total cost over five years, including the work done “beside the system”, subscription growth and exit costs. A combination often wins: an off-the-shelf core with a custom layer where it delivers an advantage.
If you are facing this decision, walk through the five criteria with us on your own processes. A free process audit shows what is standard and what is your differentiator – only then does it make sense to talk about a solution. Book a free consultation.
Sources
- Gartner Forecasts IT Spending in Europe to Grow 11% in 2026 (press release, November 2025) – https://www.gartner.com/en/newsroom/press-releases/gartner-forecasts-information-information-spending-in-europe-to-grow-11-percent-in-2026
- Zylo 2026 SaaS Management Index (January 2026) – https://zylo.com/news/2026-saas-management-index
- Data Act explained (European Commission) – https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained
- Regulation (EU) 2023/2854 – Data Act, Articles 23 and 29 – https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng
- Regulation (EU) 2016/679 (GDPR), Article 20 – right to data portability – https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679