Buy, Build, or Leave It Alone: Choosing Business Software
Every few years a business hits the same fork. Something is not working, a vendor has a demo, and someone internally says "we could just build that." The decision that follows sets the cost base for years.
There are three options, not two, and the third one gets skipped most often.
Option one: buy it
Buying is right when the problem is common, well understood, and not where you compete. Payroll, accounting, email, scheduling, help desk. Thousands of businesses have the same need, so someone has already solved it better than you will.
The honest costs of buying are not on the pricing page. They are configuration, data migration, training, the integration that turns out to be an add-on, and the annual increase. Ask for the all-in number over three years, including your own team's time.
Buy when the process is standard, the vendor is stable, and you can live with their way of doing things.
Option two: build it
Building is right when the thing you are automating is genuinely how you compete, or when no product fits without distorting the business around it.
The trap is that building always looks cheaper at the start, because the estimate covers version one and the cost is versions two through ten. Software you build is software you own forever: maintenance, security updates, the person who wrote it eventually leaving, and the certainty that it will need to change when the business does.
Build when it is a real differentiator, you have or can hire the capability to maintain it, and you have costed five years rather than five months.
Option three: leave it alone
This is the option that gets skipped, and it is often the correct one.
Sometimes the process is annoying but cheap, and fixing it would cost more than the annoyance. Sometimes the problem is a people or process issue that software will encode rather than solve. Sometimes the business is about to change enough that whatever you pick now will be wrong within a year.
Leave it alone when the pain is real but small, the cause is not technical, or the situation is about to shift.
Four questions that usually settle it
Is this how we compete, or is it table stakes? Table stakes should almost always be bought.
What happens if we do nothing for six months? If the answer is "not much", that is useful information.
Who owns this after launch? If nobody can name a person, you are not ready to build.
What is the exit? How do you get your data out, and what does leaving cost?
The mistake we see most
It is not picking wrong. It is picking without agreeing what success looks like.
If nobody wrote down what should be different in six months, every option looks defensible and none of them can be evaluated afterwards. Decide the measure first. The build-or-buy conversation gets much shorter once you have.
How we work through it
We are deliberately platform-agnostic, which means the recommendation depends on your situation rather than on who we have a relationship with. Our approach explains how we weigh the tradeoffs, and the ETS Path shows where this decision sits within a wider engagement.
Not sure where AI or technology could help your business?
Tell us what is taking too much time, what is not working, or what you would like to improve.
