Build or buy: how to decide on internal tools at a small company
A decision guide for founders choosing between off-the-shelf software and custom internal tools, covering cost, fit, maintenance and risk.
By Atharva Bhardwaj. Published .
Key takeaways
- Buy when the need is common and a good product already exists.
- Build when the workflow is specific to how you compete, or when off-the-shelf tools force painful workarounds.
- Always count maintenance: a custom tool needs an owner after launch.
When is buying the better option?
For common needs such as accounting, email, CRM or project management, established products are usually cheaper and more reliable than anything a small team can build. They also improve over time without extra effort from you.
When does building make sense?
- The workflow is unique to your business and gives you an edge.
- Your team spends real time on workarounds between tools.
- You need to combine data from several systems in a way no product supports.
Is there a middle ground?
Often, yes. Low-code platforms and integrations can connect existing tools or add a simple custom layer on top, which costs less than building from scratch and less than living with workarounds.
How do you compare the true cost?
For buying, include subscription costs as you grow, setup time and the cost of workarounds. For building, include development, hosting, security, fixes and the time of whoever maintains it.
Frequently asked questions
Can we start with a spreadsheet?
Yes. Many internal tools start as spreadsheets. When the spreadsheet becomes slow, fragile or depends on one person, it is time to consider something more robust.
What is the risk of building?
Mainly maintenance. If the person who built it leaves, a tool without documentation can become a problem.
How do we avoid vendor lock-in?
Choose tools that let you export your data and that integrate with others through open APIs.