Most small businesses should start with off-the-shelf software. It is cheaper, it works on day one, and somebody else looks after the updates. If a ready-made product does what you need, use it and get on with running your business.
The harder question is what to do when it stops being enough. This post is a plain-English way to tell the difference between a tool that is slightly annoying and a tool that is quietly costing you money.
Signs your current tools are holding you back
None of these is a problem on its own. Several of them together usually are.
The same information gets typed into two or three different systems.
A spreadsheet holds the whole process together, and only one person really understands it.
You pay for a long list of features and still lack the one you need.
You have changed how your business works to suit the software, rather than the other way round.
Your tools cannot talk to each other, so someone copies and pastes between them every week.
When custom software makes sense
Custom software earns its cost when the work it supports is central to how you make money, and when it happens often enough for small savings to add up. Good candidates tend to look like this:
A process that is specific to your business and that no ready-made product handles properly.
Work that is repeated every day or every week by several people.
Data that should live in one place but is scattered across several.
A product or service you want to offer to your own customers.
Poor candidates are things that every business does in much the same way, such as sending email or running video calls. Buy those.
Start small
Custom software does not have to mean a huge project. The sensible approach is to pick the one workflow that causes the most pain and build a small first version around it. You use it for a few weeks, you tell the developer what is wrong, and it improves. If it earns its place, you extend it. If it does not, you have spent far less than you would have on a large build.
Statemint, the UK bookkeeping application we build at Home Brunch, grew out of exactly this kind of problem: small business bookkeeping spread across too many separate tools, none of them quite fitting the way a UK business has to work.
Questions to ask any developer before you hire them
Whoever you choose, get clear answers to these before any work starts:
Who owns the code and the data when the project is finished?
Where will it be hosted, and who pays for that?
What happens if you stop working together, or the developer becomes unavailable?
How are backups and security updates handled?
Can the first version be small and delivered quickly?
A developer who quotes a fixed price without asking detailed questions is guessing. Good answers to the questions above are usually specific and a little boring, and that is a good sign.
A simple test before you start
Before you speak to anyone, write down the task you want to improve, how often it happens, how long it takes and what goes wrong. If you can fill in those four lines, you already have the start of a proper brief. If you cannot, spend a week noting down what actually happens. That alone often shows whether you need new software at all, or just a better way of using the tools you already have.
Talk it through
If you are weighing up custom software, a mobile app or a new website for your business, I am happy to talk it through. The first consultation is free and there is no obligation. You can book a free consultation here.