When a business process outgrows spreadsheets, the first question is usually whether to buy an existing product or build something of your own. Both can be the right answer. The mistake is deciding on instinct rather than on a clear view of cost, fit and risk.
When buying makes sense
- The process is standard across industries: payroll, accounting, email, HR records.
- A mature product covers at least 80 per cent of your needs without heavy customisation.
- You need to be up and running in weeks.
- The software does not differentiate you from competitors.
When building makes sense
- The process is a source of competitive advantage, such as how you price, schedule, match or serve customers.
- Off-the-shelf tools would force you to change a process that works well.
- You need deep integration with existing systems or unusual data.
- Licence costs grow steeply with users or volume, and the long-term total exceeds a custom build.
Compare the total cost, not the price tag
For each option, estimate costs over five years:
- Buy: licences, implementation, configuration, integrations, training, and the cost of workarounds where the product does not fit.
- Build: design and development, hosting, support and maintenance, and ongoing improvement.
Licence fees that look small per user can become the largest line item as you grow. Equally, a custom build that nobody maintains becomes a liability.
Consider the hybrid
Often the best answer is both: buy the commodity parts and build the differentiating layer on top. For example, use an established CRM for contact management, and build a custom portal that connects it to your scheduling and billing systems.
Buy what makes you similar to others. Build what makes you different.
Questions to ask before deciding
- Which parts of this process do customers notice and value?
- How often will the process change in the next three years?
- What happens to our data if we switch vendors?
- Who will own and maintain the system internally?
- What are the security, compliance and data residency requirements?
Answering these honestly, with input from operations, finance and IT, turns build versus buy from a debate into a decision.
