The question business owners and directors ask us most often is this: should we build it or buy it? It is, on the surface, a straightforward question. In practice it involves a set of trade-offs that look different depending on the nature of the business, the operational context, the growth trajectory, and the honest assessment of what the business actually needs versus what it thinks it wants.
This article is an attempt to give you a useful framework for making that decision — not a sales case for either option, but a set of questions that will help you arrive at the right answer for your specific situation.
The case for off-the-shelf software
Off-the-shelf software — whether that is a CRM, an accounting platform, a project management tool, or a sector-specific package — is the right choice in more situations than the bespoke software industry sometimes acknowledges.
Speed of deployment. A packaged product can be up and running in days or weeks. A bespoke system takes months. If the business need is urgent, the packaged option buys time while a more considered decision is made.
Lower upfront cost. The development cost of a packaged product is shared across thousands of customers. A bespoke system's development cost is borne entirely by you. The unit economics of packaged software are hard to beat on day one.
Continuous improvement. A well-funded SaaS product is updated regularly, with improvements funded by the customer base. You benefit from features developed for other customers' requirements without paying for them directly.
Integration ecosystem. Popular packaged products have established integration ecosystems. Connecting a mainstream CRM to a mainstream accounting platform is a solved problem. Connecting a bespoke system to either may require custom integration work.
If the process you are trying to support is genuinely standard — standard sales pipeline, standard project management, standard invoicing — then a packaged product that handles it well is almost certainly the more rational choice.
The case for bespoke software
Bespoke software becomes the rational choice when the process it is supporting is not standard — or when the combination of processes the business needs to support cannot be served by any single product or reasonable combination of products.
Operational specificity. If your business operates in a way that is genuinely different from most businesses in your sector — if the process is the competitive advantage — then forcing it into a generic system means either losing the advantage or maintaining it through workarounds. Neither is satisfactory at scale.
Total cost of ownership over five years. This is the calculation that most "buy vs build" analyses get wrong. The comparison is not upfront development cost versus first-year licence fee. It is the full cost over a planning horizon of three to five years, including licence escalation, per-seat pricing, integration costs, switching costs, and the cost of the workarounds required to bridge the gaps between what the product does and what the business needs.
For many businesses that have made this calculation honestly, the five-year total cost of a bespoke system is comparable to, or lower than, the total cost of maintaining a packaged system that partially fits.
No ongoing licence fees. A bespoke system, once built, does not carry a recurring per-user or per-transaction fee. As the business scales, the cost per user of the bespoke system falls. The cost per user of a packaged system typically does not.
Ownership and control. You are not dependent on a vendor's commercial decisions. If the vendor is acquired, changes its pricing model, discontinues a feature, or simply decides to pivot its product in a different direction, a bespoke system is unaffected. The business owns the software asset outright.
The questions that determine the answer
How differentiated is the process?
If you can describe your core operational process and a reasonably sophisticated packaged product covers 80% or more of it without significant modification, the packaged route is probably right. If the core process has characteristics that no packaged product handles well, bespoke becomes worth evaluating seriously.
What is the honest five-year total cost?
Build a realistic model: licence fees, escalation clauses, integration costs, implementation costs, training costs, workaround labour cost (be honest about this one), and the cost of the gaps that the product simply won't fill. Compare it to a realistic bespoke development and support cost. The answer is often surprising.
What is the growth trajectory?
Per-user and per-transaction pricing models become increasingly expensive as a business scales. If you are planning significant growth, the economics of bespoke improve with time. If the business is stable and unlikely to scale significantly, the packaged model may remain more cost-effective.
What is the strategic role of the system?
Is this a commodity back-office function (payroll, accounting, standard HR) where differentiation is not the point? Or is it the operational system that enables the business to serve its customers in the way that differentiates it from competitors? The answer to that question should carry significant weight in the decision.
The hybrid approach
The decision is rarely binary. Many of the most effective systems combine a bespoke core — built around the specific operational processes that define the business — with standard integrations to commodity tools where those tools genuinely fit. A bespoke operational platform that connects to Xero for accounting and Stripe for payments is not a weakness in the design; it is a sensible use of existing infrastructure.
The goal is not to build everything from scratch. It is to build exactly what needs to be bespoke, and use the best available off-the-shelf components for everything else.