There is a spreadsheet somewhere in your business that was only ever supposed to be temporary. It sits between two systems that do not talk to each other, and every morning someone opens it, copies data from one place, pastes it into another, adjusts a few figures, and moves on. It has been there for a year, probably longer. You have looked at replacing it a few times, tried a couple of tools, and none of them quite handled the specific thing you needed them to do, so the spreadsheet stays.
Most micro business owners have some version of this. A process that works well enough but takes time every week, relying on a manual step that nobody has found a better answer for. The question of whether custom software makes sense usually starts here, not with some grand digital transformation plan but with a specific, repeated annoyance that off-the-shelf tools have not been able to fix.
The tools that almost work
The average UK small business runs on six or more different software tools every day, according to research by Blucando. Each one handles its own job, but they were not designed to work together, so the gaps between them get filled by people. A separate study by Teque found that small business owners lose around 96 minutes a day just switching between applications, which adds up to roughly three working weeks a year spent on something that produces nothing.
A GOV.UK survey on technology adoption among UK SMEs found that 54% of micro businesses say they are well served by off-the-shelf products. That is a majority, but it also means just under half are not, and for businesses with fewer than ten people, the gap between what the tools do and what the business actually needs tends to show up as manual work that somebody has to do every day or every week. The workaround becomes part of the routine, and because it only takes an hour here or twenty minutes there, it does not feel like a problem worth solving until you add it up across a year.
How to tell if it is worth fixing
Not every manual workaround justifies building something. Plenty of them are fine as they are, and the time they take is not significant enough to warrant the cost or effort of replacing them. But there are a few questions that help clarify whether a particular process is worth the cost of replacing.
The most obvious one is how much time it actually takes per week. Research by Digit Shouts found that UK SMEs waste an average of 120 hours a year on manual admin tasks, and for a micro business where every person’s time counts, even two or three hours a week on a single repetitive process adds up to something material over twelve months. If you can put a rough number on the weekly hours, you can compare it against the cost of fixing it, and the answer is often closer than people expect.
It also matters whether the process has settled. If you are still working out how your business handles something, building software around it is premature because the requirements will shift as you refine the approach and you will end up changing the tool before it has had a chance to prove itself. If the process has been running the same way for six months or more, though, it is probably stable enough to build on.
The other consideration is whether you have already tried the off-the-shelf options and found they do not fit. If you have looked at three or four products and none of them handle the specific thing your business needs, that is a reasonable signal that the problem is specific enough to your workflow that a general-purpose tool is not going to solve it. If you have not looked yet, start there before considering anything custom.
What custom actually means at this scale
When most people hear “custom software” they think of large enterprise projects that cost six figures and take a year to build. For a micro business, it is nothing like that. Custom software at this scale usually means a focused tool that does one specific thing well. That could be system integration, such as connecting two systems that currently require manual data transfer between them, or automating a document that someone assembles by hand every week from three different sources. For a business that spends time copying data between a CRM and an invoicing tool because neither one offers an integration with the other, it might be a small piece of software that handles that transfer automatically.
The cost for something like this is much lower than most people assume. A small, well-scoped tool can start from a few thousand pounds, and the build time is typically measured in weeks rather than months. The key is that the scope stays tight. A tool that does one thing well for a micro business is a different proposition entirely from a platform that tries to manage everything, and keeping the scope focused is what keeps the cost and the timeline realistic.
When off-the-shelf is the right answer
If an existing product covers most of what you need and the remaining gap is small, it is almost always better to use it and accept the remaining limitations rather than building something from scratch. Off-the-shelf tools have the advantage of being maintained and updated by someone else, and for a micro business that does not have an IT team, that matters more than it might for a larger company.
A good development partner will tell you this upfront. The way a good bespoke software development company typically works is to start with a discovery phase before any building happens, and the point of that phase is to answer the question of whether custom software is the right call for your specific situation. If an off-the-shelf product would do the job, a decent firm will say so, because a project that should not have been built does not lead to a good outcome for anyone. That discovery conversation also gives you a fixed-price figure for the build if it does go ahead, so you know the full cost before you commit.
What to look for if you do go ahead
If you reach the point where building something makes sense, a few practical things are worth checking before you choose who to work with. You want a fixed-price quote so you know the cost upfront rather than watching it climb as the project runs, and a discovery phase before any building starts so that you are not paying for development until both sides agree on what is being built. Ongoing maintenance costs should be transparent from the start so you know what the tool costs to run after launch, not just what it costs to build. The best indicator of a trustworthy partner is probably their willingness to tell you that you do not need custom software and should just use an existing product instead, because that kind of honesty early on tends to mean you get honest advice throughout the project too.
Where to start
Write down what the current manual process looks like, how many hours a week it takes, and what you would want a tool to do instead. That is enough for a first conversation with a developer, and a good one will tell you straight whether building something makes sense or whether an off-the-shelf product would handle it. For micro businesses with a specific operational problem that the available tools have not been able to solve, the cost of a small, focused custom tool is often lower than it looks from the outside, and that first conversation is where you find out what it would actually cost.
