When Standard Software Isn't Enough: 3 Signs It's Time to Think About Custom Development
- Roberto Benanti
- Apr 3
- 3 min read
Every time someone in a company says "we use Excel for this because no software does exactly what we need", there's a signal worth paying attention to.
It's not necessarily a problem. Excel is a powerful and flexible tool. But when it becomes the glue between five different systems, or when "Mario's file" is the only place where a critical process lives, the problem is no longer Excel: it's that the company has outgrown the capacity of its standard tools.
We work with Italian SMEs every day. In this article we share the 3 signals that, in our experience, reliably indicate it's time to consider a custom solution.
Signal 1: the workaround has become the process
A workaround starts as a temporary fix. An Excel sheet is used while waiting to find the right software, or data is manually copied from one system to another because no integration exists. Then a year passes, and that workaround is still there. In fact, someone has built three more workarounds on top of it.
The critical signal isn't having a workaround: it's when the workaround has become the official process, and nobody remembers how it was done before. At that point, every new employee is trained on how to use the workaround. Operational risk grows every day.
At a logistics company we work with, shipping cost calculations ran on a 14-tab Excel file maintained by a single person. When that person went on holiday, the process stalled for two days.
If your company has critical processes that exist only in someone's head or in a file that "must not be touched", that's a clear signal.
Signal 2: you're paying for more software than you actually use
Many Italian SMEs we meet have between 6 and 12 active SaaS subscriptions. CRM, PM tool, note-taking tool, invoicing software, internal communication platform, digital signature solution, HR system. Each was chosen to solve a specific problem, and it solved it.
The problem is that none of these tools talk to each other. Data lives in separate silos. Every time information needs to move from one system to another, someone copies it manually. Errors, delays, multiple versions of the same data.
When the total cost of these subscriptions exceeds the value they deliver, or when the time spent making systems communicate exceeds the time each one saves, it's time to think differently. Sometimes the answer is a smart integration between existing tools. Other times it's building something specific that replaces three subscriptions with one tool designed for exactly how that company works.
Signal 3: the software dictates the process instead of adapting to it
This is the most subtle signal, and often the most significant. It happens when the team starts changing how they work to fit the constraints of the tool, instead of the other way around.
Concrete examples we hear often: "we can't do X because the software doesn't support it", "we have to go through Y even though it makes no sense because it's the only way the system understands", "the report management wants can't be extracted directly, someone builds it manually every Monday".
Software should be an enabler, not a constraint. When a company's most critical processes are limited by the tools that support them, competitive advantage erodes over time. Companies that build tools aligned to their specific way of operating have an advantage that is difficult to replicate.
Custom software doesn't necessarily mean "built from scratch"
When we talk about custom software with our clients, the first reaction is often: "but isn't that incredibly expensive?" The answer depends on what you mean by "custom".
In many cases, the solution isn't writing an application from scratch. It's building an automation and integration layer on top of existing tools, or developing a specific module that covers exactly the identified gap. The starting point is always the same question: which process costs the most in its current form?
We've seen companies solve years-old problems in a few weeks, not because the problem was simple, but because they finally took the time to analyse it properly and build the right solution instead of adding yet another workaround.
Do you recognise any of these three signals in your company?
Our approach always starts with analysing the real process: where time is lost, where information gets lost, and what the current situation actually costs. Only from there do we evaluate together which type of solution makes sense, and whether custom software is truly the right answer.
Or read all articles in the Custom Software Development category.