Kortelo.
EN
All insights
Strategy 6 min read Jun 2026

Build vs buy, on an SME budget

Custom software isn't always the answer — and off-the-shelf isn't always cheaper. A simple test for which one you actually need.

The build-vs-buy question usually gets settled by whoever argues loudest, not by the economics. But there's a straightforward way to reason about it — and, honestly, the answer is 'buy' more often than a software studio is supposed to admit.

Buy when the problem is common

If thousands of companies have the exact problem you do — email, accounting, payroll, a CRM used the standard way — someone has already built a mature product for it, and their per-customer cost is a fraction of yours. Competing with that by building is almost always a losing trade.

The honest advice here is boring and correct: buy the commodity, configure it well, and move on. A studio that tells you to custom-build your email is optimizing for its invoice, not your outcome.

Build when the problem is yours

The case flips when the problem is specific to how your business actually runs — the way your five distributors price, the exact shape of your order flow, the reconciliation logic only your finance lead understands. No off-the-shelf tool models that, so you end up bending your business to fit the software.

That bending is the hidden cost of 'buy' in the wrong place: workarounds, exports, and a manual layer of people gluing generic tools together. When that glue costs more than the software would, custom stops being a luxury and becomes the cheaper option.

The test we actually run

Before we quote anything, we ask two questions. First: is this problem common or specific to you? Second: what does the current workaround cost in hours and errors every month? Common plus cheap workaround means buy. Specific plus expensive workaround means build — and usually a smaller build than expected.

Most real situations are a mix: buy the commodities, build the one piece that's genuinely yours, and integrate them. That's not a compromise — it's the point. You spend custom-engineering money only where it can't be bought.

The takeaway

Buy the common problem; build the one that's specifically yours. If your monthly workaround costs more than the software would, custom is the cheaper choice — not the extravagant one.

Reading about your exact problem? Let's fix it.

Enterprise capabilities. SME pricing.