Guides
Build or buy internal tools for small teams
When off-the-shelf software is the right answer, when a custom tool pays for itself, and how to tell the difference before you spend money.
Start with the work, not the tool
Most small teams do not have a software problem. They have work that nobody can see. Jobs live in inboxes, spreadsheets and people's heads. Before you compare tools, write down the job: who does it, what triggers it, and what happens when it is missed. That list tells you more than any feature grid.
Buy when the process is standard
If your process looks like everyone else's, buy. Helpdesks, accounting and CRM tools are mature and cheap at small team sizes. You also get updates and support you do not pay for directly. The trade-off: you work the way the tool wants you to work. For standard processes, that is fine.
Build when the gaps cost you money
Build when you are stitching spreadsheets and SaaS tools together by hand, when per-seat pricing grows faster than your team, or when the way you work is your edge. The clearest signal is lost revenue. If work is done but not billed, or missed because nobody can see it, a custom tool usually pays for itself.
Work out the real cost of each option
Compare three numbers over two years: the subscription cost of the tools you would buy, the staff hours spent on manual workarounds, and the money lost to missed or unbilled work. A custom internal tool from £3,000 often beats a stack of per-seat subscriptions within the first year. Sometimes it does not. Do the sums before you decide.
A real example: £50K recovered
Aldeburgh Coastal Cottages ran maintenance through a group WhatsApp chat, with job details on paper. Work was missed, and done work often went unbilled. No off-the-shelf tool fitted how the team worked. I built a maintenance ticketing tool and a linen tracker shaped around their process. Result: £50K recovered, a day of admin saved every week, and 750 cleans tracked each month.
What to check before you build
Own the code, in your own GitHub account. Agree a fixed scope and a fixed price before work starts. Set up login and access rules from day one. Check that the tool can connect to the systems you already use. And keep V1 small: build the part that stops the money leaking first. Everything else can come in V2.
Want help with this? Book a free 30-minute call.