Every growing business hits the same fork: should we build a custom solution, buy an off-the-shelf product, or is it too early to do either? Get it wrong and you either overspend on something bespoke you did not need, or outgrow a cheap tool within a year. Here is the simple framework we use to make that call — and why “advise first” is usually the honest answer.
Most digital decisions come down to three paths, and each has a right time:
Buy when your need is genuinely common — email, accounting, standard CRM workflows, a basic website. If thousands of businesses have the same requirement, someone has already built a good tool for it, and building your own would be reinventing the wheel at ten times the cost. The mistake here is ego: assuming your business is more unique than it is.
Build when the way you do something is actually part of your edge, or when your requirements are specific enough that every off-the-shelf tool forces painful compromises. A custom CRM makes sense when your sales process is genuinely different; a custom web application makes sense when it becomes a core part of how you deliver value. The mistake here is the opposite: building something bespoke just because it feels impressive, when a product would have done the job.
The most expensive software is not the one with the highest price tag. It is the one you build and then abandon — or buy and then outgrow — because nobody asked the right questions first.
When a vendor sells only custom builds, everything looks like it needs building. When a vendor resells one product, everything looks like it needs that product. Neither is advice — it is a sales motion wearing advice’s clothes.
Genuine advice starts by understanding the business and is willing to reach an inconvenient conclusion: “you do not need to build this,” or “this cheaper tool is enough for now,” or even “do nothing yet.” That answer earns less in the short term and more trust in the long term — which is exactly the trade we think is worth making.
Before any build-or-buy decision, ask three questions: Is this need common or genuinely specific to us? Will this still fit in two years, or will we outgrow it? And do we actually understand the problem well enough to commit — or are we buying certainty we do not have yet? If the third answer is shaky, that is your signal to advise first.
We advise before we deliver. A first conversation is free — and if the honest answer is “don’t build it yet,” we will tell you.
