Build or buy the system?

“Should we build it ourselves or buy something off the shelf?” is one of the biggest decisions a business makes about its systems – and one of the easiest to make on gut feeling. This page doesn’t give you an opinion but a decision model: a rule to lean on, a calculation to run, and a map of the traps that catch people going both ways.

The core rule: differentiation decides

Strip away everything else and this remains: build where you differentiate, buy where you’re like everyone else.

So the question you ask about every system isn’t “can we build it?” – almost anything can be built. The question is “does this make us unique?” If the answer is no, buy. A finance system doesn’t make you sharper than your competitors, no matter how nicely you build it. The process that gets customers to choose you, on the other hand, is worth owning.

The rule is powerful because it shifts focus from technology to business. This isn’t something the development department should decide alone, but a question of where your edge actually sits.

The five-year calculation

When the rule doesn’t give an obvious answer, you need to calculate – but the right way. The mistake people make is comparing a visible purchase price against an invisible development cost. The right comparison is total cost over five years.

A bought system has a low entry cost but ongoing licenses and a customization bill that grows every time a new version breaks what you’ve customized. A homegrown build has a high entry cost but no license and full control. Which ends up cheaper depends on how well an off-the-shelf system actually fits – and that fit is exactly what the calculation forces into the light.

The most common wrong decisions – in both directions

There are two classic ways to get this wrong, and they’re mirror images of each other.

• Building what you could have bought. A team decides to build its own generic system – often because it feels more fun or more flexible. Two years later, they have a half-finished copy of an off-the-shelf system, plus a maintenance commitment that never ends. Consequence: money and time burned on something with no competitive advantage.
• Buying what is the business. A company squeezes its distinguishing process into an off-the-shelf system to save money. The system doesn’t bend, so they bend – and lose exactly what made them unique. Consequence: a cheap solution that hollows out the business itself.

A concrete example: a logistics company whose strength was its own route optimization bought an off-the-shelf system that “almost” handled it. That “almost” ended up costing them what set them apart from competitors. Had they instead bought the finance module ready-made and built the route optimization themselves, they’d have gotten both low cost and kept their edge.

Who should own the decision?

One reason this goes wrong is that the decision lands at the wrong table. Left entirely to engineering, the homegrown build tempts, because it’s more stimulating to build than to configure something ready-made. Left entirely to finance, the purchase price tempts, because the license looks cheap against a development budget. Neither angle sees the whole picture alone.

The right decision requires business, technology, and finance to sit at the same table and ask the only question that matters: does this make us different, or does it make us like everyone else? It’s a business question before it’s a technical one. Keep that question central, lean on the five-year calculation, and keep the two classic wrong decisions in mind, and most choices land right.

The right decision, then, requires someone willing to ask the uncomfortable question of where your real value lies. Want a neutral sounding board for your specific systems? At Weapp we’re happy to think through the whole picture with you and can go through the choices with you before you commit.