With 50 to 250 employees, an organisation sits in an awkward middle ground. You’ve outgrown the standalone packages you started with: every department now has its own tool, and someone bridges the gaps between them with Excel and manual re-typing. For heavyweight enterprise systems, you’re too small - the implementation alone demands more time and money than you’re willing to spend.
It’s precisely in that middle ground that custom software pays off. Not because bespoke development wouldn’t work elsewhere, but because the ratio between investment and effect is strikingly favourable at this size. Here’s why.
Large enough to repeat, small enough to decide fast
The quiet advantage of a mid-sized company is scale without sluggishness. A clunky process that causes little more than irritation at eight employees repeats itself hundreds of times a week at a hundred and twenty. Every minute a custom application shaves off that process therefore counts heavily, straight away.
At the same time, decisions get made quickly. The managing director or operations manager who signs off the investment knows the shop floor and sits at the table themselves. No steering committee is needed to work out which process hurts most. That keeps a custom project sharp: it targets the work that matters, not the wish list of everyone who got a say.
Work out what the manual work is costing you now
The case for custom software doesn’t start with what it delivers, but with what the current way of working costs. You can do that sum yourself, without a quote. Say four people in your back office each spend five hours a week moving orders from one system to another. That’s twenty hours a week, well over nine hundred hours a year. Multiply those hours by what a working hour costs your organisation and you have the annual price of that one process alone. The errors that come with re-typing, and the time to fix them, aren’t even in that figure yet.
Set that figure against the investment in software that takes over the work, and you have a fair basis for a decision. An application like that also lasts for years, so the saving counts again every year. Often one visible process is enough on its own to tip the balance, and there are usually more.
Where off-the-shelf software starts to pinch at this size
Off-the-shelf packages are built for the average company. A mid-sized company has usually grown into its own way of working, and that’s exactly the part a package doesn’t recognise. The signs are familiar:
- working methods that only fit the package via workarounds
- data scattered across systems that don’t talk to each other, held together by manual work
- licence costs for modules and users that barely touch them
- reports someone assembles by hand every month from three different sources
Each sign is manageable on its own. Together they form a cost that grows with the organisation and never shows up as a separate line on any budget. We wrote earlier about what goes wrong when this situation persists, in what happens when your systems don’t communicate with each other.
Custom software doesn’t have to replace everything
Custom software rarely means rebuilding your entire system landscape. Your accounting package does its job fine; you don’t replace that, you connect it. Most of the value sits in targeted custom work alongside what’s already there, such as an internal tool that automates a manual process or an integration that ties two systems together. That way the investment stays limited to the process that demonstrably costs money.
So start not with the biggest system, but with the process your team complains about most often. That’s almost always also the process that makes the strongest case. Does the figure turn out to be one you don’t want to leave on the table? The page on custom applications explains how we approach that kind of project for organisations that have outgrown their packages.