Build or buy: when custom software beats a subscription for a small service business

We build custom software for a living, and the honest first answer to “should we build this?” is usually no. Off-the-shelf software is cheaper to start, someone else maintains it, and for most jobs it is good enough. The question is where “good enough” stops.

Buy when the job is the same for everyone

Accounting, payroll, email, video calls, file storage: every business does these the same way, and the software for them is mature and cheap. Building your own would cost more and do less. The same goes for any tool where the vendor’s way of working is a perfectly good way of working.

Build when the process is the business

The case for bespoke software starts where your way of working is the reason customers choose you. A removals company that quotes differently, a clinic group that runs a queue across several branches, a consultancy that qualifies leads with its own questions: when a subscription forces that process into someone else’s shape, you either change how you work or you work around the tool. Both cost more than they look.

Build when the tools must talk to each other

Most small businesses do not have one system; they have five subscriptions and a spreadsheet in the middle. When staff copy the same details from the enquiry tool to the booking tool to the invoice, the cost is not the subscriptions, it is the typing. A small custom layer that joins them, or replaces two of them, often pays for itself on that alone. We wrote about the three manual steps to automate first.

Build when the fees grow faster than the team

Per-seat pricing is fine for three people. It looks different at fifteen, when every new hire adds a line to three bills, and a reseller’s markup sits on top of the platform’s own charges. The first WhatsApp inbox we built replaced a third-party subscription: going direct to Meta’s Cloud API removed the middleman’s markup (Meta still bills per message) and put the conversations and lead data on a server the business controls. More on that in WhatsApp inbox and automation.

Questions that decide it

1. Would a competitor use exactly the same tool, the same way? If yes, buy.
2. How many places does the same piece of information get typed? More than one is a cost you are already paying.
3. What will the subscription cost with the team you expect to have, not the one you have?
4. Who owns the data, and can you get all of it out?
5. What happens if the vendor changes its pricing or shuts down the feature you rely on?
6. Is there one part of the process that off-the-shelf tools keep getting wrong? That part is the candidate for building, not the whole business.

The usual answer is both

Buy the commodity, build the part that makes you different, and connect them. That is also why every project we take on starts with a written scope: it is where “build” gets narrowed down to the smallest piece worth building. If you want to talk through where that line sits for your business, here is how we build custom software and automation.