Build or buy? Choosing between off-the-shelf and custom business software

Every growing company reaches the same moment. The spreadsheets no longer hold, the tools don’t talk to each other, and someone asks the question: should we buy an ERP, a CRM, an HR system off the shelf, or build our own?

There is no universal answer. But there is a reliable way to decide.

Start with the process, not the product

Before comparing products, write down the processes the software must support, step by step, as they really happen today. Who requests, who approves, what data moves where, which rules apply.

Then sort them into two groups:

• Processes that are the same in every company. Leave requests, invoicing, basic bookkeeping. They follow rules everyone shares.
• Processes that make you different. The way you price, the way you serve customers, the way your group of companies works together. They are why customers choose you.

This single exercise usually answers most of the question.

When off-the-shelf wins

Buying is the right call when:

• The process is standard. If your way of approving leave is the same as everyone else’s, a mature product has already solved it, with years of edge cases behind it.
• You need it running this month. A product can be live in days. Custom software takes weeks at least, even when done well.
• The vendor fits your context. Your languages, your country’s rules, the number of companies you run.

Be honest about the last point. A product that almost fits often costs more than it seems: per-user licences that grow with you, modules you pay for and don’t use, and above all the workarounds your team invents to bridge the gaps.

When custom wins

Building pays for itself when:

• The process is your advantage. If your pricing logic, your service model or your operations are what set you apart, forcing them into a generic tool erases the difference.
• You run several companies or countries. Many products are designed for one company, one language and one set of rules. Groups with several entities, multilingual teams and local regulations quickly hit their limits.
• The workarounds have become the system. When spreadsheets, exports and manual copies fill the gaps between three or four tools, the real cost is already high. It is just spread across everyone’s week.
• Licences scale faster than value. Per-user pricing that made sense for twenty people may not for five hundred.

The hybrid path

In practice, most growing companies end up with a mix, and that is usually the best answer. Buy what is standard, build what is yours, and connect everything so data is entered once.

A typical shape:

• An off-the-shelf tool for standard bookkeeping.
• A custom platform for the operations, sales process or customer portal that make you different.
• Clean integrations between them, so the numbers match everywhere.

The key is to design the connections deliberately, not as an afterthought. Each external product should sit behind a clear interface, so it can be replaced without rebuilding everything around it.

A simple decision grid

For each process, ask four questions:

1. Is it the same in every company, or is it part of what makes us different?
2. Does an existing product fit our languages, countries and structure without workarounds?
3. What do the workarounds cost us today, in hours and in errors?
4. If we stop using this product in three years, can our data leave with us?

Mostly “same, fits, cheap, yes”: buy. Mostly “different, doesn’t fit, expensive, no”: build. Anything in between is a candidate for the hybrid path.

Before you decide

Whatever you choose, insist on three things: working software early (a trial for a product, a prototype for custom software), clear ownership of your data, and documentation that lets another team take over.

If you want a second opinion on your own build-or-buy decision, book a call. We will tell you honestly when buying is the better option.