Business management software: when off-the-shelf is enough, when you need custom

People searching for "business management software" are almost always comparing products: features, price, reviews. It's the right question, but it comes one step too late. Before choosing between two or three products, there's a question almost no page on this topic asks honestly: standard or custom.

That's not an accident. I opened the Italian pages that hold this search: whoever writes them is almost always selling one of the two answers, an off-the-shelf software vendor or a software house that builds custom systems, and the comparison naturally tilts their way. My own case isn't neutral either: I build custom software, not off-the-shelf management products. That's exactly why, before any product comparison, what follows is the data with its source and a way to work out which case you're actually in, not a reason to pick one side.

How many businesses already use one

Starting from the numbers helps frame the question: you're not deciding whether to be an outlier, most Italian businesses past a certain size have already faced this choice.

According to ISTAT's Imprese e ICT, anno 2025 report, published on 15 December 2025 (data checked on 31 July 2026), 56.0% of firms with at least 10 employees use at least one management software among ERP, CRM or Business Intelligence, roughly 7 percentage points more than in 2023. Looking only at ERP, the software covering administration, warehousing and production, the share drops to 48.8% among small and medium enterprises, against 85.9% among large companies: the gap isn't surprising, it grows with organisational complexity, not with willingness to digitise.

One point worth keeping in mind so as not to draw the wrong conclusion: the ISTAT survey only covers firms with at least 10 employees. Microbusinesses, which make up the largest share of Italy's productive base, are left out of the count entirely. If you run a smaller business, these numbers tell you how companies past a certain organisational threshold behave, not the whole landscape of Italian businesses.

What actually changes once you install it

A common idea in off-the-shelf product comparisons is that installing management software is a nearly painless step: you create an account, import your data, and the next day you work as before, just with less paper. The data says otherwise.

Research by the Digital Innovation Observatory for SMEs at Politecnico di Milano, carried out with AssoSoftware on a sample of over 500 Italian SMEs and presented in November 2023, found that 54% of companies had to revise at least one business process after introducing a piece of software, and 26%, one company in four, found it necessary to rewrite every business process to make it actually work.

This applies to off-the-shelf software too, not only to custom builds. A ready-made product carries an implicit way of working: fields that must be filled in a set order, approval steps already decided by whoever designed it, a way of organising stock or customers that might not be yours. It's not a flaw in the product, it's the nature of a tool built to suit many different businesses: something in how you work has to bend to fit it.

When off-the-shelf is enough

For the large majority of businesses, a commercial management product is the right choice, and it's worth saying that as plainly as the opposite case. It costs less, it's running in weeks rather than months, and maintenance, updates and security stay with the vendor, not with you.

If the processes you want to digitise look like those of any business in your sector, invoicing, bookkeeping, order management, appointment scheduling, customer records, it's very likely a product built for your sector already covers them, and covers them better than a first version built from scratch could. Custom isn't a more refined option in general: it's the answer to a specific case standard software doesn't cover, not a step every business eventually has to take.

When custom makes sense

The signal that matters isn't an opinion, "my business is special", it's a verifiable fact: you're already keeping that piece of work running by hand, with spreadsheets, or with two or three different programs that don't talk to each other and that someone copies between manually. If you're already doing that, the time you lose every week making by hand what no product does is the real cost, not an impression.

A few concrete examples to recognise it: a production or delivery process that follows your own rules, different from anyone else's in the sector; a link between systems that no commercial product can bridge, maybe because one of them was written years ago specifically for you; a workflow that's the reason customers choose you over a competitor, and that therefore makes no sense to standardise by buying the same product they're buying.

Outside these cases, custom isn't the answer to a comparison between two standard products: it's the answer to a process that comparison doesn't even account for.

The risk product comparisons don't name

Both standard and custom software carry a cost almost no promotional page spells out: what happens the day you want to change.

With off-the-shelf software, the risk is vendor dependency: if the price goes up, if terms change, or simply if the vendor closes, what happens to your data, your customer records, your order history? Can it be exported, and in what format? These are questions to ask before signing, not to discover the day you actually need an export and no one knows how to do it.

With custom software, the risk is symmetrical and has another name: dependency on whoever wrote it. If the agency or developer who built it closes, changes jobs, or simply stops answering, who steps in when something breaks? That's why a written specification and documentation that stays yours, not only in the head of whoever coded it, aren't a technical detail: they're the difference between software that stays yours and one that stays someone else's even after you've paid for it.

How to decide, in practice

The most reliable criterion isn't a checklist of features, because that list is always won by whoever wrote it to make their own product win. It's a single question, and you probably already know the answer, even if you've never put it in writing: how many hours a week do you, or someone on your team, spend making by hand what a piece of software should already be doing on its own?

If the answer is few, or none, a well-chosen off-the-shelf product solves it, and it's the sensible place to start: it costs less and you can try it before committing. If the answer is a number that tells you how much time, every week, is stuck in work no one should still be doing by hand, that's the signal it's worth looking at what it would cost to build the missing piece, not necessarily an entire system from scratch.

My custom software work starts from there: first, analysing the process with whoever runs it every day, then a written specification before any coding, so you know what you're buying and I know what I'm building, then development in stages, with something working to try early rather than only at the end. There's no list price, because it depends on the process it needs to cover, and anyone who gives you a figure before seeing it is guessing.

If that isn't your case, that's fine too: most people reading this article probably aren't, and the honest answer is that a good off-the-shelf product, chosen carefully around the features you actually need, remains the right choice.

If you do recognise the signal, that work you repeat by hand every week because no product covers it, get in touch and describe the process: it becomes clear quickly whether it's genuinely a case for custom software, or whether a product that covers it already exists and you simply haven't looked closely enough yet.