Custom internal tools vs off-the-shelf software
Build or buy is the wrong question on its own. The better one is how specific your workflow is, and how much the gap between your process and your software is costing you every week. Here is a way to decide without a stack religion.
When off-the-shelf wins
For common, well-solved jobs, buy. Accounting, email, payroll, document storage and the like are the same in almost every business, and a mature product will always be cheaper and safer than rebuilding it. If a tool fits your process out of the box, use it.
When custom wins
Build when the workflow is specific to you and the manual work around the tool is the real cost. Pricing rules, approval chains, how you onboard a client, what counts as a complete order: these are yours, and forcing them into a generic product usually means someone doing the difference by hand.
The tell is a spreadsheet or an inbox sitting next to the SaaS tool, holding the part the tool could not do.
The hidden cost of “almost fits”
Software that almost fits is the most expensive kind, because the cost is hidden in people's time. A tool that handles eighty percent of a job leaves the other twenty percent as manual work, forever, and that work does not show up on an invoice the way a licence does.
The middle path most teams miss
You rarely have to replace everything. The most cost-effective build is often a thin custom layer that connects the tools you already pay for, moves data between them on rules you set, and gives your team the one screen the off-the-shelf tools could not. You keep what works and remove the copy-paste in between.
A quick decision test
Before you build anything, answer three questions:
- is this job common to most businesses, or specific to us?
- how many hours a week does the manual workaround take?
- would the tool still make sense if we doubled in size?
Related work
Have a workflow like this?
Show us the most tedious thing your team does on a computer and we’ll tell you what we can automate.
Show us the manual work