Skip to content
CompanyWRX

Software

Should you build or buy business software?

Most build-versus-buy discussions are held at the wrong altitude. They compare features, when the decision is really about who owns the result for the next ten years.

The short answer

Work through four options in order: buy it if a product fits without damaging workarounds; configure it if it nearly fits; integrate it if the gap is between systems rather than inside one; build it only if the process is a genuine competitive difference or the cost of bending the business to available software exceeds the cost of building. The deciding question is whether someone in your business will own the result long-term — if nobody will, buying is better even when it fits worse.

The four options, in order.

Buy. Somebody has already built this and it fits your process without damaging workarounds. This is the right answer far more often than people who enjoy building want it to be.

Configure. It nearly fits, and the gap closes with settings, fields and workflow configuration inside the product. Cheaper than it looks, and frequently already paid for.

Integrate. Each system is fine at its own job and the problem is the space between them. This is the most commonly misdiagnosed case — it presents as "our software is bad" when the software is fine and disconnected.

Build. None of the above is honestly true. Now you are building, and you should know exactly why the first three failed.

The question that actually settles it.

Not "can we build this" — you almost certainly can. The question is: who owns it in five years? Custom software needs hosting, dependency updates, security patching, and someone who understands why it works the way it does. That is a permanent operating commitment, not a project cost.

If you cannot name the person or the arrangement that covers that, buy something. A product that fits at 80% and is somebody else’s responsibility to maintain will beat a perfect system that nobody owns.

Two signals that building is genuinely right.

The process is a competitive difference. If how you do this thing is part of why customers choose you, software that forces you to do it the standard way is removing your advantage to save a license fee.

Per-seat economics have inverted. On a large team, per-seat licensing for a system used by everyone can pass the cost of building. That is a real calculation rather than a feeling, and it should be done with the maintenance cost included on the build side.

If you do build, build in stages.

The failure mode of custom software is a year-long build revealed at the end, at which point the requirements have moved and the people who specified it have changed their minds legitimately. One real workflow, in production, used by real people, teaches more than any amount of specification — and it gives you the option to stop.

You don’t need another vendor.You need a company that understands the whole company.

Whether you are starting with an idea or scaling an established operation, CompanyWRX can help build the brand, technology, systems and operations behind the business.

Typically owner-led companies from first idea to around 500 people.