Every growing business reaches a point where it needs a capability the market does not satisfy cleanly. Maybe the available tools are too generic, too complex, or too expensive. Maybe the workflow is genuinely unusual. Maybe a vendor relationship ended badly and the instinct is to own the solution this time.
The question that follows — build it or buy it? — is one of the most consequential technology decisions a business can make. It is also one of the most frequently made on instinct rather than analysis.
Why the Framing Is Usually Wrong
The "build vs buy" framing implies a binary choice. In practice, there are at least four options:
Buy and configure. Purchase an existing product and adapt your processes to fit it. This is the fastest path and the most common — but it requires honest acceptance that the tool's model may not be a perfect fit for your business.
Buy and integrate. Purchase an existing product and build custom integrations to connect it to your existing stack. Faster than building from scratch, with the reliability of a maintained product. The integration is the custom investment, not the core tool.
Build on top of a platform. Use a development platform (Airtable, Notion, Retool, Power Apps) to build custom tools without starting from zero. Lower build cost, faster iteration, but with platform dependency and capability limits.
Build from scratch. Commission or develop a custom application. Maximum control and fit — but maximum time, cost, and maintenance obligation.
The right question is not "build or buy" but "which of these four options produces the right outcome given our constraints?"
The Five Decision Criteria
1. Does this capability differentiate you?
If the capability you need is something every business in your sector needs — invoicing, HR management, project tracking, customer communication — you should almost certainly buy it. The tool vendors have invested more in building it than you ever will. Building a generic capability from scratch is expensive and distracts engineering resource from the things that actually differentiate your business.
If the capability is genuinely specific to how you operate — a workflow that reflects your unique service model, a data structure that no existing tool supports, a process that is proprietary — then building makes more sense. You are building a competitive asset, not a commodity tool.
2. What does the integration landscape look like?
An off-the-shelf tool that does not integrate with your existing stack is not cheaper than building. Every manual step required to bridge the gap is a hidden cost. Before evaluating any tool on features, assess its integration story: what APIs does it expose, what does it connect to natively, and what would it take to embed it in your data model?
3. What is your maintenance appetite?
Custom-built software requires maintenance. Security patches, dependency updates, bug fixes, new browser compatibility — these are ongoing obligations that do not end at go-live. Most SMEs underestimate this cost significantly.
A rough rule: plan for annual maintenance investment equivalent to 20-30% of the original build cost. If that is not a sustainable commitment, a maintained commercial product is almost always the better choice.
4. How stable is the requirement?
If the business process the tool supports is likely to change significantly in the next two years — because you are in a growth phase, because the market is shifting, because you are still figuring out the model — build for flexibility. A commercial tool with good configuration capabilities will adapt faster than a custom application that requires a developer to change.
If the requirement is stable and well-understood, building is less risky.
5. What is the timeline?
Commercial tools go live in weeks. Custom builds take months. In a fast-moving business, a working tool in six weeks is often more valuable than a perfect tool in six months. Speed to capability matters.
The Case for Buying Almost Everything
For most growing SMEs, the default should be buy. The commercial software market is mature, well-funded, and increasingly well-integrated. The tools available today are orders of magnitude better than they were five years ago. The cases for building from scratch are real but narrower than most businesses think.
The specific cases where building makes sense:
- The capability is core to your competitive differentiation and no commercial tool approaches it
- The commercial alternatives would require significant process distortion to use
- The integration requirements of commercial tools would cost more than building
- You have in-house technical capability and the ongoing maintenance is factored into resource planning
Everything else should default to buy, integrate where necessary, and adapt processes to fit.
Making the Decision
Run each option through the five criteria and score it honestly. The point is not to produce a precise number but to make the assumptions explicit. A decision made on explicit assumptions is correctable. A decision made on gut feel is not.
Then test the conclusion with one question: if this decision turns out to be wrong, what is the cost of reversing it?
If the cost of reversal is low, move fast. If the cost is high — you are committing significant budget, long-term maintenance, or critical process dependency — take more time with the analysis.
If you are at a decision point on a specific capability and want a structured conversation about which path makes sense for your business, book a consultation. This is one of the assessments we do in our advisory engagements.
