01 / When to buy

Buy when the process is common

Accounting, email, file sharing, basic CRM and standard commerce are well-served categories. A mainstream product usually provides mature features, ongoing updates and a lower initial commitment than rebuilding the category yourself.

Signs an existing product may fit

  • The workflow is similar across many businesses
  • The product covers the important requirements without severe workarounds
  • Subscription and migration costs are acceptable
  • The vendor’s security and support model suits the business

02 / When to integrate

Integrate when the tools are useful but disconnected

Sometimes the software choices are sound but staff spend too much time moving information between them. A focused integration can remove this friction without replacing platforms that already perform their main jobs well.

03 / When to build

Build when the process creates meaningful advantage

Custom software becomes more compelling when an important workflow is genuinely distinctive, standard products create expensive constraints, or a digital experience is itself part of the product offered to customers.

The comparison should include discovery, development, hosting, maintenance, support, security and future change. The initial build price is only one part of ownership.

Signs to explore a custom build

  • The requirement is central to how the business operates or competes
  • Available products cannot support it without persistent costly workarounds
  • The business can provide sustained ownership and subject-matter input
  • A smaller first release can test the expected value

04 / Combining the approaches

Do not force a binary decision too early

A practical answer can combine all three approaches: buy a capable core platform, integrate it with existing systems and build only the specialised component that creates distinct value.

Discovery should compare these options before a custom build is treated as the default.