The Real Question
"Should we build or buy?" is one of the most common questions we hear from SMEs. But it's often the wrong starting point. The better question is: "What problem are we solving, and which approach gives us the best outcome for the investment?"
Neither option is universally better. Off-the-shelf software is fantastic for solved problems. Custom software is the right call when your competitive advantage depends on doing something differently.
When to Buy
Off-the-shelf software makes sense when the problem you're solving is well-understood and commoditised. Accounting, email, project management, CRM — these are solved problems with mature products that have been refined over years and millions of users.
Buy when:
- The problem is generic across your industry
- A mature product exists that covers 80%+ of your requirements
- The remaining 20% isn't where your competitive advantage lives
- You need to move fast and can't wait for a custom build
- The total cost of ownership (licensing, training, integration) is lower than building
Examples: Accounting (Xero, QuickBooks), CRM (HubSpot, Salesforce), project management (Linear, Jira), communication (Slack, Teams).
When to Build
Custom software makes sense when your requirements are genuinely unique, when the software itself is your product, or when off-the-shelf tools create more friction than they solve.
Build when:
- Your process is a competitive differentiator and off-the-shelf tools can't replicate it
- You need to integrate multiple systems in ways that no existing product supports
- The software is your product (SaaS, marketplace, platform)
- You're spending more time working around a tool's limitations than using it
- Data ownership, security, or compliance requirements rule out third-party solutions
- You need an experience that's uniquely yours (customer-facing applications)
Examples: A logistics company whose routing algorithm is their edge. A fintech building a new lending product. An operations team drowning in spreadsheets because no tool fits their workflow.
The Hidden Costs of Each Approach
Hidden Costs of Buying
- Licensing fees compound. Per-seat pricing adds up quickly as your team grows. A £50/user/month tool costs £30,000/year for 50 users.
- Integration overhead. Making tools talk to each other often requires custom development anyway.
- Vendor lock-in. Migrating away from a platform once your data and processes are embedded is painful and expensive.
- Feature bloat. You pay for features you don't use, and the interface complexity slows your team down.
- Customisation limits. When you hit the edge of what the tool can do, you're stuck.
Hidden Costs of Building
- Ongoing maintenance. Custom software needs updates, security patches, and bug fixes. Budget 15-20% of the initial build cost annually for maintenance.
- Longer time to value. A custom build takes weeks or months. Off-the-shelf can be live in days.
- Knowledge dependency. If the team that built it disappears, maintaining it becomes harder. Good documentation and clean code mitigate this, but it's still a risk.
- Scope creep. Custom builds are vulnerable to ever-expanding requirements. Strong scope management is essential.
A Decision Framework
Ask yourself these five questions:
- Is this problem unique to our business? If yes, lean towards build. If no, lean towards buy.
- Is this a core differentiator or a supporting function? Build your differentiators. Buy your support tools.
- What's the total cost of ownership over 3 years? Include licensing, integration, customisation, and maintenance. Often the numbers are closer than you'd think.
- How fast do we need this? If speed is critical and an off-the-shelf option exists, buy first. You can always build later once you understand the problem better.
- Do we have the internal capacity to manage a custom build? Building software requires a product owner — someone internally who can make decisions, prioritise features, and provide feedback.
The Hybrid Approach
In practice, most businesses end up with a mix. Buy the tools that solve generic problems. Build the software that makes you different. Connect them with APIs and integrations.
This is often the most cost-effective approach: you get the reliability of mature products for the boring stuff, and the flexibility of custom software where it matters most.
Common Mistakes
- Building what you should buy — custom-building a CRM or project management tool when excellent options exist.
- Buying what you should build — forcing a generic tool to do something it wasn't designed for, creating workarounds that are fragile and expensive to maintain.
- Not accounting for total cost of ownership — comparing the upfront cost of a custom build to the monthly cost of a SaaS tool without projecting forward.
- Building too much too soon — commissioning a full product when an MVP would validate the idea at a fraction of the cost.
Right Advance Digital helps SMEs make smart build-vs-buy decisions. We'll give you an honest assessment — even if the answer is "don't build." Get in touch.