Build vs. Buy vs. Retire: Making Better Software Decisions
“Should we build it or buy it?” is one of the most common technology questions in any growing company. It’s a good question, but it’s incomplete. It assumes the software should exist at all.
A better framework has three options: build, buy, or retire.
Start with the problem, not the solution
Before comparing options, write down in one or two sentences what business problem the software solves and what it’s worth to solve it. If you can’t, stop there. That’s usually a sign the third option is the right one.
When to buy
Buy an existing product when:
- The problem is common to many businesses, such as accounting, CRM, HR, scheduling, or ticketing
- A mature product handles at least most of your needs well
- Your process can reasonably adapt to how the product works
- The vendor is stable and the product is actively maintained
Buying means someone else carries the maintenance, security, and platform changes. That’s usually worth a lot. The trade-offs are subscription cost, less control, and dependence on the vendor’s roadmap.
When to build
Build custom software when:
- The capability is genuinely part of how you compete or deliver value
- No product fits without contorting your business
- You need deep integration across systems in ways products can’t support
- You’re prepared to own it after launch
That last point is the one most often skipped. Custom software has to be monitored, patched, documented, and changed for as long as you use it. (See The Hidden Costs of Custom Software After Launch.) Building without a plan for ownership is how orphaned software gets created.
When to retire
Retire, meaning stop doing the thing or stop using the tool, when:
- Usage is low or declining
- Another system already covers the need well enough
- The process it supports no longer matters as much as it once did
- The cost of maintaining it, in money, risk, and attention, exceeds its value
Retirement is the most underused option because nobody gets credit for removing things. But every system you retire is one less thing to secure, patch, pay for, and explain on a security questionnaire.
A quick decision guide
| Question | If yes |
|---|---|
| Is this a common business function? | Lean toward buy |
| Is it core to how we compete? | Consider build |
| Will we commit to owning it long-term? | Required to build |
| Is anyone really using it? If not | Retire |
| Does something we already have cover it? | Consolidate or retire |
The principle behind it
The best software portfolios aren’t the most advanced. They’re the smallest that do the job well, with every remaining system clearly owned and properly maintained.
If you’re facing these decisions across several systems, a Software Portfolio Audit gives you a ranked plan. If you’re considering building something, we’ll be direct about whether you should. Sometimes the right answer is “don’t build this.” Let’s talk.
Tell us what you're running.
Two quick steps. I'll read it personally and reply with an honest read on your situation and whether our team can help, usually within one business day.
- I lead every engagement personally
- No sales sequences, and your details are only used to reply
Prefer email? [email protected]