Custom software or off-the-shelf? An honest decision framework

We build custom software for a living, so take this article as being against interest: most of the time, you should buy, not build. If an off-the-shelf product fits 90% of your workflow, buy it, adopt its opinions, and spend your money elsewhere. We say this in discovery calls weekly, and it costs us projects. It's still the right answer.

The interesting question is the other case — the one where teams keep buying tools that almost fit, stacking subscriptions and spreadsheets to bridge the gaps. Here's the framework we actually use.

Every business has processes that are generic — payroll, ticketing, email — and a few that are the business. The freight forwarder's quoting logic. The firm's client-intake flow. The distributor's pricing rules.

Buy generic. But when the 40% a product doesn't cover is your competitive edge, forcing it into someone else's workflow means sanding off exactly what makes you win. That 40% is where custom software pays — usually as a small, focused system that does one thing your way, integrated with the off-the-shelf tools doing everything else.

Nobody budgets for the spreadsheet era, so it looks free. Count it honestly: the hours re-typing data between systems, the errors from stale copies, the key person whose head holds the process, the deals lost to a three-day quote cycle. Put a monthly number on it. Custom builds stop looking expensive when compared against the real baseline instead of against zero.

The honest argument against custom software isn't the build cost — it's abandonment. A system nobody maintains is worse than a product with a support contract. So make maintenance part of the purchase decision, not an afterthought: who patches it, what the response SLA is, what it costs per month. If a vendor can't answer that in writing, that's your answer about the vendor.

This is why we treat launch as the midpoint of an engagement, and why most of our clients are on maintenance plans years after the build. If you're weighing a build-vs-buy decision right now, describe the workflow to us — including when the honest answer is 'buy the product, and here's which one'.