Skip to content
Engineering5 min read

When we tell clients not to build

We turn down build work often enough that it is a standing possible outcome of discovery rather than a courtesy. Here is the test we apply.

CyberXSolutions Engineering

Published

The default answer is buy

Commercial software is cheaper than custom software for anything that is not a source of competitive advantage. That is not a controversial statement, and yet build decisions are routinely made on the strength of a 70% feature match and an unexamined dislike of the vendor.

Three conditions that justify building

We build when the process is genuinely differentiating, when no product fits without workarounds that cost more than the licence, or when integration and data ownership requirements make a product structurally unsuitable.

Two out of three is usually not enough. One out of three almost never is.

  • The process is a real source of competitive advantage
  • No product fits without workarounds that cost more than the licence
  • Data ownership or integration requirements rule products out structurally

The honest cost comparison

Most build-versus-buy analyses compare licence cost to build cost and stop there. Include five years of maintenance, the opportunity cost of the engineers, and the risk-adjusted cost of the project running long — and a lot of build decisions reverse.

We produce that comparison during discovery whether or not it favours us.

Working on this yourself?

We run ninety-minute working sessions with no charge and no pitch. Bring the process that keeps breaking and whatever numbers you have.

Book a session

Start the conversation

Bring us the process that keeps breaking.

Ninety minutes with our engineers and strategists. You leave with a systems map, an automation shortlist and an honest read on what AI should and should not touch in your business.

What to expect

  • No pitch deck, no obligation
  • Senior engineers in the room
  • A written plan within five days